My environment is Visual Studio 2022, x64, and I am doing a Qt project which needs the curl lib.
I installed curl with vcpkg and got this error.
Then I cannot find the pdb file in the path below and only see a libcurl.dll here.:
C:\vcpkg\packages\curl_x64-windows\bin
If I ignore the pdb file and keep compiling my project in Visual Studio 2022, I'll got these error:
Which means VS can not find these pdb files from the include path.
Is that means vcpkg didn't install or compile the curl source code?
How to resolve this? Thanks a lot!
Related
I have a cmake that create a project for VS 2019. When I try to compile the code, I am getting that this library is not found:
Error LNK1104 cannot open file 'C:\Program Files (x86)\Windows Kits\10\Lib\10.0.18362.0\um\x64\Psapi.Lib'
Checking my system, I do not have 'C:\Program Files (x86)\Windows Kits' directory.
I made sure that during my VS installation, the C++ code development was selected and also I run a repair on installation to ensure that any missing file is installed, but I m still have the same issue.
What other software or library should I install to get this issue fixed?
I have Visual Studio 2022 and installed Win10 SDK 10.0.19041.0 via Visual Studio installer Desktop Development With C++. I am able to find Psapi.lib in directory C:\Program Files (x86)\Windows Kits\10\Lib\10.0.19041.0\um\x64. Try installing SDK from page: https://developer.microsoft.com/en-us/windows/downloads/sdk-archive/
We are upgrading the compiler from Visual Studio 2013 to Visual Studio 2019.
Getting the below error while building the project which used regex expressions:
Cannot open include file: 'atlrx.h': No such file or directory
After installing the ATL/MFC Components also atlrx.h is not fond in the VS include directory.
Does anyone have any idea like which component should be installed to get rid of this error?
Thanks in advance.
You should download ATL server from Codeplex and install the files.
ATL Server: Visual C++ shared source software
And then copy the include file to a folder on your hard disk, Atlrx.h normally lives in the $(VCInstallDir)VC\atlmfc\include folder.
You should make sure that this path is added in the include directories of visual studio.
When try to use vcpkg with vs2015 to install caffe2:x64-windows in windows 10 I obtain an error with dumpbin.exe:
Dump of file E:\vcpkg\packages\caffe2_x64-windows\debug\lib\Caffe2_CPU.lib
LINK : fatal error LNK1104: cannot open file 'E:\vcpkg\packages\caffe2_x64-windows\debug\lib\Caffe2_CPU.lib'
I think that the problem is about the version of dumpbin.exe used in the process, it can't open big lib files, this one is bigger than 2 GB, but in the directory C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\bin I found directories like amd64_x86 with other version of dumpbin but I dont know how to configure vcpkg to use this version of dumpbin program.
Resolved
I resolve my problem checking the code in the solution of vcpkg, I changed all the paths of the type "VC" / "bin" for "VC" / "amd64_x86", in this way I use the chaintool used by vcpkg, after compiling caffe2 I undo my changes.
I generated a Visual Studio 15 2017 project with CMake to compile LLVM and Clang myself. I've tried to build the ALL_BUILD project from Visual Studio (as the getting started page suggested).
But the build failed with a linking error due to (I assume) the linker did not have permission to open a file. This specific file was LLVM-C.def.
The error message:
Cannot Open File '<path_to_build_folder>/build/tools/llvm-shlib/LLVM-C.def
I've tried to give full permission to the user, also tried as admin but did not work.
edit:
The file did not get created because the gen-msvc-exports.py script fails to locate a libllvm-c.args file. It searches the Debug directory for this file but I found it in the $(Configuration) directory. Could this be some Visual Studio configuration/macro problem?
edit2:
Also is there any workaround to get the Clang Tooling library to work on Windows? The precompiled package doesn't contain any headers or static libraries to work with (but for some reason the Linux one does).
I migrated some "native" c++ projects from Visual Studio 2010 on Windows 7 to Visual Studio 2013 on Windows 8.1. Rebuilding gave me this error. I realized I did not have the Windows SDK installed, so I installed that next, but I'm still getting the error. Anyone else get this on otherwise-clean VS project migrations?
I searched under the SDK folder for the missing file and found it. Because the SDK was installed after I migrated the projects, the paths were not included in my projects. I was able to fix everything by adding to my include and lib paths.
I added the following folders to my include paths:
$(WindowsSdkDir)include\um
$(WindowsSdkDir)include\shared
My full include path for both Debug and Release now looks like this:
$(WindowsSdkDir)include;$(WindowsSdkDir)include\um;$(WindowsSdkDir)include\shared;$(FrameworkSDKDir)\include;$(VCInstallDir)include;$(VCInstallDir)atlmfc\include;
I added the following folder to my lib paths (note that is specific to a 32-bit build! see x64 for 64-bit, and arm for arm builds...):
$(WindowsSdkDir)lib\winv6.3\um\x86
My full lib path looks like this:
$(WindowsSdkDir)lib;$(WindowsSdkDir)lib\winv6.3\um\x86;$(FrameworkSDKDir)\lib;$(VCInstallDir)lib;$(VCInstallDir)atlmfc\lib
Note that if you have a copy of the original project file, you can also fix the problem by re-migrating it again after the Windows SDK is installed.
include path: $(VC_IncludePath);$(WindowsSDK_IncludePath);
lib paths:$(VC_LibraryPath_x86);$(WindowsSDK_LibraryPath_x86);