0

I am working on some legacy Visual C++ projects, trying to bring the code and libraries up to the present day, and am getting a flood of link errors. In my investigation into the problem, I am trying to determine where the values for many of the build command macros are coming from. I have seen the answers in questions like this, this, and this, however they all seem to lead back to the same incomplete list at Microsoft, and I have been unable to find the missing macro values.

The project contains several different path reference variables, such as $(VC_LibraryPath_x86), $(WindowsSDK_LibraryPath_x86), and others, which are not listed on the Microsoft page linked above.

If anyone can help me "fill in the blanks" and complete the list that Microsoft left incomplete (or perhaps they are on a much older list that is not on their site any more), that would be a great help.

Thanks.

Community
  • 1
  • 1
Peter Howe
  • 429
  • 6
  • 19
  • You should specify a particular VC version, since this kept changing between versions. For example `VC_LibraryPath_x86` and `WindowsSDK_LibraryPath_x86` didn't exist in VC 2010. – dxiv Jan 05 '16 at 05:14
  • To list the macros in effect see for example http://stackoverflow.com/a/12056067. – dxiv Jan 05 '16 at 05:15
  • @dxiv, You are correct, the projects were created long ago in VC++ 6.0, and, while we have multiple versions of newer Visual Studios to choose from, other projects are currently in 2010 so the policy is to keep the updated projects in 2010 (not my decision to make, but I can make recommendations...) – Peter Howe Jan 06 '16 at 13:45

0 Answers0