You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Along with the current v120 and v140 platform toolsets, would it be possible to add support for v140_xp as well? This is needed if you want your programs to still be able to run under Windows XP.
Currently if you set your platform to v140_xp in Visual Studio 2015 and try to compile a program that uses libpng, you just get a bunch of png-related unresolved external errors.
The text was updated successfully, but these errors were encountered:
You might be able to work around it for now by using v140, setting the "Minimum Required Version" to 5.01 in Configuration Properties > Linker > System (also requires specifying a subsystem on the same page), and defining WINVER and _WIN32_WINNT macros to 0x0501. I don't have a copy of Windows XP around to test this.
Thanks for that, I'll give it a try, but I'm not confident it will work. The toolset name is different for v140_xp, so all the conditions in the NuGet configuration files will fail as they only match v120 and v140. So I guess you'd have to manually specify all the include paths and library files, for each project.
I was hoping it would be a simple matter of adding v140_xp to the list of toolsets and have everything generated automatically when rebuilding the package, but perhaps not?
Along with the current
v120
andv140
platform toolsets, would it be possible to add support forv140_xp
as well? This is needed if you want your programs to still be able to run under Windows XP.Currently if you set your platform to
v140_xp
in Visual Studio 2015 and try to compile a program that uses libpng, you just get a bunch of png-related unresolved external errors.The text was updated successfully, but these errors were encountered: