facebook
Raise version's in win32 binaries header
Related to #932 Currendly zstd.exe build and link as:
Timestamp: 05.04.2023 06:24:47
Machine: x86
Linker version: 2.40
Operating system version: 4.0
Subsystem version: 4.0
Windows console
Windows 32-bit executable.
De-facto zstd.exe not started on (yes, unsupported) Windows Server 2003 R2 SP2 (32-bit): no entry poind InitializeConditionVariable in kernel32.dll (5.2.3790.5295 (srv03_sp2_qfe.140205-1447), 2014-02-06) Will honest raise verion of subsystem/operation system up to 6.0?
P.S.
Timestamp: 15.08.2022 23:18:14
Machine: x86
Linker version: 2.25
Operating system version: 4.0
Subsystem version: 4.0
Windows console
Windows 32-bit executable.
File version: 1.9.4.0
Internal name: lz4
Original filename: lz4..exe
Product name: LZ4
Product version: 1.9.4.0
still work on that OS (lz4 -b1 -e9 run fine).
Will honest raise verion of subsystem/operation system up to 6.0?
I'm not quite sure I understand. Are you saying that zstd.exe is advertising it works with older Windows versions, when it does not? And that we should raise the version that zstd.exe advertises that it supports?
I guess this would involve a change in build scripts, but if you have any advice about how to achieve this, please let us know.
We work around this with LoadLibraryW() and GetProcAddress() and then avoiding or emulating absent features.
#define _WIN32_WINNT _WIN32_WINNT_WIN2K before including windows.h will enumerate all the missing features.
