Geeks, please accept the hero post of 2021 Microsoft x Intel hacking contest>>>
When compiling old projects, I found that there are two ways on the Internet, both of which can be used. In essence, they are the same two ways. Here are listed for your convenience
Method 1( http://www.cnblogs.com/loongfee/archive/2012/10/25/2738322.html )
Just change it to No. This is more convenient
Method 2
Or select command line for this interface
1. Click the command line property page
2. Type/safeseh: no into the “additional options” box, and then click apply
From: http://blog.csdn.net/wujunokay/article/details/47168589
It’s hard to say what’s on the Internet. The one on the website above said he was original, but the first one in front of him was published nearly three years ago
The following one is even more extraordinary. In 2009, he wrote a plan for this problem( http://blog.csdn.net/lijiawlm/article/details/4406837 )
Original text:
You may encounter this problem when compiling the driver, especially when writing the C + + driver
At this point, you need to add a sentence to the source file
NO_ SAFESEH = 1
This will disable the safeseh compilation option
Similar Posts:
- Non-ASCII character ‘\xe8’ in file xxx.py on line 8, but no encoding declared
- LNK2026 module unsafe for SAFESEH image. Error: LNK1281 Unable to generate SAFESEH image.
- java.io.IOException: Server returned HTTP response code: 405 for URL:
- Solve the security check error similar to error c4996: ‘scanf’: this function or variable may be unsafe in vs2019
- bash :startx command not found
- cleartext http traffic to 192.168.1.106 not permitted
- The jar file rt.jar has no source attachment appears in eclipse
- LINK : fatal error LNK1123 (VS2010)
- 「ImportError: libcublas.so.10.0: cannot open shared object file: No such file or directory」
- Solve the problem of error running xxxapplication command line is too long when compiling and running IntelliJ idea