![]() ![]() Re-add your extra paths here, or better yet - under C/C++/General -> Additional Include Directories and Linker/General -> Additional Library Directories. This will reset include path to something like $(VC_IncludePath_x86) $(WindowsSdk_71A_IncludePath_x86) (will vary for SDKs). This will remove your additional paths.Ĭlick 'Apply'. Open project properties, go to VC++ Directories, for 'Include Directories' and for 'Library Directories', choose. In my case the project was using v120 toolset from VS2013, which is superseded by v140_xp in newer VS.Īfter setting correct platform and toolset understood by VS2017, I did the following to resolve the problem: If the quotation marks contain an absolute path, the compiler only looks for the file at that location. I have all legacy SDKs in VisualStudio 2017 installer, and none of that fixed VS not finding essential includes such as. include 'myincludefile.h' this tells the compiler to look for the file in the same directory that contains the source file first, and then look in other locations specified by the build environment. None of the answers or comments listed/linked here so far are helpful. This is legitimate problem which I ran into myself recently when migrating old project targeted for Windows XP into VS2017. If you added your own additional paths in project properties, VisualStudio 2017 can't automatically figure out base paths when switching between platforms/toolsets - normally it automatically puts correct paths there, but if you added customizations, VS won't touch them. ![]() This happens when you have customized include/library paths in legacy projects. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |