After reinstalling VS2017 on different folder, when I compile an old project I get an error about a missing natvis file (which now is on a different path).
I searched inside the VC++ project files and my user profile but it is not there.
Where natvis information is stored?
Error LNK1104 cannot open file 'C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\Common7\Packages\Debugger\Visualizers\std_json.natvis'
Found it, it is inside .vcxproj file but it does not show in explorers.
Related
I have been trying to install the ImageView plugin for Far Manager, but I couldn't find the dll file. Instead I found the original code, but I am having trouble compiling it into a DLL.
Here is the original: https://sourceforge.net/p/farplugs/code/HEAD/tree/ImageView/
I am trying to open the files as a Visual Studio project, opening plugin.cpp and pressing Build->"Build Current Document". It starts building, and runs into a million fatal errors like this one:
C:\Users\User\source\repos\ImageView\ImageView\libfreeimage\c1 : fatal error C1083: Cannot open source file: 'FreeImage\Source\LibPNG\pngwutil.c': No such file or directory
The files aren't there, but in ...\libfreeimage\ there are a bunch of vcxproj files like FreeImageLib.vcxproj
I am new to C++, and Visual Studio, so I am not sure what I am doing wrong. Any help would be greatly appreciated.
I'm a beginner and I'm trying to build an open source project for the first time in Windows, but I keep running into file not found errors when building. What I've found so far is that a header file called corecrt.h is located at C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\. This file would include another header file named vcruntime.h. The problem is that vcruntime.h is nowhere to be found in that folder.
I later found that vcruntime.h is located in a separate folder located at C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\VC\Tools\MSVC\14.25.28610\include. This is strange because I'm not sure why corecrt.h would include a file that is not in its own filepath...
I did the bone-headed thing of just copying over vcruntime.h file to the C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\, but this just shifts the problem down the road because vcruntime.h in turn also includes other header files located at C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\VC\Tools\MSVC\14.25.28610\include, and so on.
I think the issue lies with Windows itself. I think I'm missing something that's suppose to install additional header files like vcruntime.h to C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\
So far I've tried uninstalling/reinstalling Windows SDK, and just reinstall Windows as a whole, but still no dice to make the missing files appear in that folder. Can someone give me some insight on this? I've asked this question on Reddit but so far nothing has been able to help.
Here's the link to the instructions I'm following on how to build https://wiki.documentfoundation.org/Development/BuildingOnWindows
I'm building using their suggested environment Lode on my Windows 10 machine.
I get C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\ucrt\corecrt.h(10): error: vcruntime.h: No such file or directory
The error occurs right at the build step and I run make 2>&1 | tee build.log
I too had the same issue, but found the cause which was the Include directories were not specified correctly. To fix this I did the following with Visual Studio:
Right click on the project name, and then click on Properties.
Under Configuration Properties, select VC++ Directories.
The Include directories should contain $(VC_IncludePath);$(WindowsSDK_IncludePath); - correct this.
Click OK to save and Bob's your uncle.
I often find that I have problems getting visual studio to find my headers and I think I might have finally found out why: it seems that visual studio does not understand multiple relative directories in project configurations, e.g:
When that directory certainly does exist.
My question is: can somebody confirm this is the case and, if so, is there a reason why they'd do this? Is it a bug or intentional?
Posting as an answer as I can't really fit this into a comment although its a bit frowned upon...
The easiest way to debug this is to run Process Monitor from here, and add a filter to only show access to your file name. I made an example c++ project which tried to load a non existant header #include "Bobby.h" and then added the following filter to Process Monitor:
Path Contains Bobby.h Include
Then I ran the build and got the following output:
CreateFile C:\Users\MyUserName\Documents\Visual Studio 2012\Projects\ConsoleApplication2\ConsoleApplication2\Bobby.h NAME NOT FOUND
CreateFile C:\Program Files (x86)\Microsoft Visual Studio 11.0\VC\include\Bobby.h NAME NOT FOUND
CreateFile C:\Program Files (x86)\Microsoft Visual Studio 11.0\VC\atlmfc\include\Bobby.h NAME NOT FOUND
CreateFile C:\Program Files (x86)\Windows Kits\8.0\Include\um\Bobby.h NAME NOT FOUND
CreateFile C:\Program Files (x86)\Windows Kits\8.0\Include\shared\Bobby.h NAME NOT FOUND
CreateFile C:\Program Files (x86)\Windows Kits\8.0\Include\WinRT\Bobby.h NAME NOT FOUND
From this output you can easily see where the compiler searched for the header file - It may be good enough to help you understand why it didn't find it.
HTH
I'm new to VS2010 and tried to compile a project ever worked in VS2008. The error looks simple:
stdafx.h(43): fatal error C1083: Cannot open include file: 'afxwin.h': No such file or directory
stdstring.h(619): fatal error C1083: Cannot open include file: 'TCHAR.H': No such file or directory
threads.h(52): fatal error C1083: Cannot open include file: 'cassert': No such file or directory
I googled and this type of error happens often in VS2010 Express version, but I'm using VS2010 Professional Edition. And I've checked, all these missing files are at the right place.
C:\Program Files (x86)\Microsoft Visual Studio 10.0\VC\atlmfc\include and
C:\Program Files (x86)\Microsoft Visual Studio 10.0\VC\include
The thing is, other header files in stdafx.h is at the same directory as afxwin.h but didn't get complained.
I also checked the VC++ Directories of the property manager and the "Include Directories" is "$(VCInstallDir)include;$(VCInstallDir)atlmfc\include;$(FrameworkSDKDir)\include;$(WindowsSdkDir)include".
Is there anything else that I forgot to check? Very much appreciated for the help.
The properties explorer is where you want to look. Afxwin.h is in ..\atlmfc\include, tchar.h and cassert are in ..\include which you'd think would be a global-type property, but it turns out it's not so simple. This is the biggest problem I had with upgrading from 2008. This is no longer an application option, it's a user property.
Before you go about changing things, look the properties explorer and read the MSBuild documentation, because, while the new format is more powerful and flexible, but it doesn't upgrade from the old format gracefully.
This could be a very silly question to any long time C++, visual studio or live555 users but I am having problems building the live555 source code with visual studio 2005. I have found a good walk through guide for creating the projects manually because .mak files are no longer supported by newer versions of visual studio but am still having problems. It seems that visual studio cannot open the .hh files that come in the include folders and I have added to the header folders of each seperate project.
Is there something special you have to do to the compilier or a plugin for the IDE to allow VS2005 to open .hh header files?
This is the error I am getting:
fatal error C1083: Cannot open include file
'BasicUsageEnvironment.hh': No such file or directory.
It seems to me that Visual studios cannot find the file, rather than it not being able to open that file type. If you right click on your project and go to
Properties->C/C++->General->Additional Include Directories
Now browse to the location of the .hh file and add it to the path. Visual studios should now be able to find the file in question. You may also have to add library paths to your solution. Please let me know if there are additional errors.