But the combination of runtime and compile-time Windows development issues has to be skillfully navigated on Windows.
_WIN32_WINNT (and WINVER) are the epitome of legacy. In English: hot mess. Your issue is a good example.
I might like to remind, that is a compile-time aka building issue. Run time issue is also a graveyard of API's semi-officially abandoned.
use case: write a console app that will run on all Win versions and show colors where they are available. that might require two or more legacy machines for compiling and testing.
The outcome is a question: it that feasible?
Here we build on Windows 10 and run on Windows 10. So far running on Windows 7 was not a problem. Inside we do not stop the execution if runtime is not Windows 10.
But the combination of runtime and compile-time Windows development issues has to be skillfully navigated on Windows.
_WIN32_WINNT(andWINVER) are the epitome of legacy. In English: hot mess. Your issue is a good example.I might like to remind, that is a compile-time aka building issue. Run time issue is also a graveyard of API's semi-officially abandoned.
use case: write a console app that will run on all Win versions and show colors where they are available. that might require two or more legacy machines for compiling and testing.
The outcome is a question: it that feasible?
Here we build on Windows 10 and run on Windows 10. So far running on Windows 7 was not a problem. Inside we do not stop the execution if runtime is not Windows 10.