setting visual studio variables, such as VC_LibraryPath_x64 (AGAIN)

Ed Broughton 31

I asked this question previously.

I received two replies, both of which suggested that the poster had not carefully read my question (and one of which provided incorrect and irrelevant feedback).

So, I am reposting.

To be clear.

A) I have never changed the values of any of the below variables.
B) Following installation of Visual Studio 2019, I have never been able to build a project on the specified computer, because the link process cannot find the libraries that "come with" Visual Studio (e.g., LIBCMTD.lib)

The following variables are used by my projects.
However, I see no means to either see or set their values.

How do I see and set their values (some of which are clearly incorrect)?

Variables used by Visual Studio

VC_IncludePath
WindowsSDK_IncludePath
VC_LibraryPath_x64
WindowsSDK_LibraryPath_x64
VC_LibraryPath_x86
WindowsSDK_LibraryPath_x86

Thanks in advance

P.S. It seems absurd if there is no easy means of examining and setting their values.

Ed Broughton 31 Reputation points

2021-07-10T21:03:17.823+00:00

My bad, partially.

My original post made clear that I the basic libraries (such as LIBCMTD.lib) were not found.

However, it did not make clear that I had not changed any of the above variables.
RLWA32 45,691 Reputation points

2021-07-10T21:05:45.307+00:00

In an earlier post you wrote

I’m unable to build any Visual Studio projects, because libraries are not found.

So it wasn't exactly clear which libraries you are referring to.
Ed Broughton 31 Reputation points

2021-07-12T23:36:57.593+00:00

My bad, if I failed to give any examples. I'd have to look at that post.

But, I still can't build, because libraries such as uafxcwd.lib, libcmtd.lib, ETC., are not found).
Drift_91 0 Reputation points

2024-06-06T12:05:13.5133333+00:00

Would be excellent if someone would give a proper answer instead of repeatedly insisting not to modify obviously incorrect values. Would also be nice if the staff would be professional instead of locking threads to get the last word in.

I'm having a similar issue and my $(WindowsSDK_LibraryPath_x64) is clearly not correct, as it points to a non-existent directory. It points to C:\Program Files (x86)\Windows Kits\NETFXSDK\4.8.1\Lib\um\x64 when it should point to C:\Program Files (x86)\Windows Kits\NETFXSDK\4.8\Lib\um\x64.

Can someone tell me how to fix it, other than wasting space on my system by reinstalling the v4.8.1 SDK? "Don't mess with the value" is not the correct answer, unless you can provide a method of letting VS correct the value itself. And I'm not completely reinstalling the software over a single environment variable I can correct myself. I've already clicked "repair" in Visual Studio Installer, and it did not correct the value.

I'd uninstall the 4.8 SDK and install 4.8.1 instead, but Visual Studio Installer won't let me do so due to unnecessary hard dependencies on version 4.8.

Edit:

I now see why everyone is saying not to mess with the values, as they're set by conditions and not static. A better explanation than "don't mess with them" would have been helpful.

In my case it looks like I need to delete the following registry key for the condition looking for it to return false: Computer\HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\Microsoft SDKs\NETFXSDK\4.8.1

I found the conditions in C:\Program Files\Microsoft Visual Studio\2022\Community\MSBuild\Microsoft\VC\v170\Microsoft.Cpp.WindowsSDK.props, but as others have suggested you should probably not mess with them, only use them to trace back to the cause of the incorrect value.

2 answers

Sam of Simple Samples 5,546 Reputation points

2021-07-11T00:23:46.057+00:00

I am using VS 2017, the following might be different for VS 2019.

Find the Visual Studio Installer; execute it. Click the Modify button. Is the checkbox checked for Desktop development with C++? In the right side (Installation Details) is a checkbox for a Windows SDK checked (there are multiple versions but you do not need all of them)? There are many versions of C++ to choose from, such as VC++ 2017 and Visual C++ for MFC. Which ones have you selected? If the necessary components have not been installed then they cannot be found because they do not exist and messing with the variables is a foolish mistake.
Please sign in to rate this answer.
RLWA32 45,691 Reputation points

2021-07-11T10:13:14.957+00:00

VS2019 looks substantially the same -

Ed Broughton 31 Reputation points

2021-07-12T23:44:51.877+00:00

Thank you for your reply.

I appreciate it.

However, all of that is correct.

All of the necessary components are installed.

Including the latest SDK.

In any event, the “not found” libraries are not part of the SDK.

They are the basic libraries, such as uafxcwd.lib, libcmtd.lib, ETC.

They are still not found.

I have installed VS2019 (and every other version, back to VS 97) on numerous computers.

I never had this problem before.

Sam of Simple Samples 5,546 Reputation points

2021-07-13T00:07:09.14+00:00

Have you confirmed that they (uafxcwd.lib and libcmtd.lib) exist? I am using Visual Studio 2017. For me those libraries are in subdirectories under:

C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\VC\Tools\MSVC

Do you see the libraries anywhere in the corresponding locations for Visual Studio 2019?

RLWA32 45,691 Reputation points

2021-07-13T09:18:48.147+00:00

Have you done anything with property sheets that would alter or fail to inherit the default property sheets installed by VS2019?
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.
Bruce (SqlWork.com) 66,056 Reputation points

2024-06-06T16:00:26.0033333+00:00

in vs install folder there are a bunch of scripts that set the env variables. winsdk.bat for example. for vs2022 pro they are in "C:\Program Files\Microsoft Visual Studio\2022\Professional\Common7\Tools".

you probably need to uninstall and reinstall the workloads to get the correct scripts.
Please sign in to rate this answer.

0 comments No comments
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.

Share via

setting visual studio variables, such as VC_LibraryPath_x64 (AGAIN)

2 answers

Your answer