The above warning occurs as a result of a clash between two features of the Visual Studio development suite and can be eliminated by either disabling support for "Edit and Continue" or eliminating Incremental Compilation. The first allows you to edit code while debugging when stopped at a break point. The second specifies whether linking is done incrementally or not (that is, one included library at a time). Linking incrementally can result in larger file sizes and occassionally "jump thunks," which, I believe, are libraries that require multiple memory hops to reach.
If you link a module that was compiled with /ZI, which implies an internal linker option called /EDITANDCONTINUE, and a module that was compiled with /OPT:REF, /OPT:ICF, or /INCREMENTAL:NO, which imply no /EDITANDCONTINUE, you will get LNK4075.
The property controlling "edit and continue" can be changed in the Project Properties Pages -> Project Configuration -> C/C++ -> Debug Information Format, whereas the property specifies if linking should be done incrementally can be changed in the Project Properties Pages -> Project Configuration -> Linker -> Enable Incremental Linking.
2009/07/31
2009/07/30
Subscribe to:
Posts (Atom)
Labels
- .Net (1)
- AES (1)
- c# (8)
- cmd (3)
- Database Script (1)
- DES (1)
- dll (3)
- Error (1)
- Event Viewer (1)
- File Operation (1)
- FireFox (1)
- Gmail (1)
- HashMap (1)
- HashTable (1)
- HeidiSQL (1)
- HMAC (1)
- ip (1)
- Java (2)
- Java Bean (1)
- Javascript (1)
- LINQ (1)
- Marshall Class (4)
- MD5 (1)
- Microsoft System Configuration Utility (1)
- MVC (1)
- MySQL (3)
- Opera (1)
- PRNG (1)
- Regedit (1)
- Run Command (3)
- SHA (1)
- String Operation (1)
- struct (1)
- Stylish (1)
- Technical Interview Questions (1)
- Unmanaged Memory Operation (3)
- Virtual Machine (1)
- Visual Studio 2005 (2)
- Warning (1)
- Web Application (3)