Home » U++ Library support » U++ Core » Big issue with Visual Studio 2019 (some versions)
|
|
| Re: Big issue with Visual Studio 2019 (some versions) [message #61692 is a reply to message #61587] |
Sun, 01 June 2025 19:19  |
JeyCi
Messages: 69
Registered: July 2020
|
Member |
|
|
mirek wrote on Thu, 20 March 2025 15:37
Uh, I am suprised this has returned. MSC 2022 and current U++ -> no warnings...
I could not even suppose how and why, but after some experiments, having created new project with VSBT2019, - it started to compile OK for about a month -- just build_method file should be correct, perhaps... but after reinstalling VSBT2019 - were 2 unresolved functions... GetTempPathW function (fileapi.h) and GetModuleFileNameW function (libloaderapi.h) - both headers from in C:\Program Files\Windows Kits\10\Include\10.0.19041.0\um... OK, they reference windef.h that is in C:\Program Files\Windows Kits\10\Include\10.0.19041.0\shared, include together with um & ucrt. And for c-runtime to PATH C:\Program Files\Microsoft Visual Studio\2019\BuildTools\VC\Redist\MSVC\v142 and bin, include, lib from ..\VC\Tools\..
P.S. C:\Program Files\Microsoft SDKs\Windows Kits - no more used - C4927 warning appears with C:\Program Files\Microsoft SDKs\Windows Kits\10\ExtensionSDKs\Microsoft.UniversalCRT.Debug\10.0.1904 1.0\Redist\Debug,
C:\Program Files\Windows Kits\10 - use instead
Best regards.
[Updated on: Thu, 05 June 2025 18:22] Report message to a moderator |
|
|
|
Goto Forum:
Current Time: Sat Jun 07 13:08:28 CEST 2025
Total time taken to generate the page: 0.04820 seconds
|
Members
Pages
Help
Register
Login
Home
