Is your feature request related to a problem? Please describe.
No response
What you want
I think all parameters of the build should be shown in the various "version" places:
Welcome screen
ver command
Help-About
folder name
somewhere else?
Current discrepancies:
Welcome screen
-- shows MinGW without Host OS or shows Host OS without Visual Studio
-- MinGW lowend is not shown
-- ARM - I don't know if it's shown or if it shows the same "32-bit" and "64-bit" as for x86/x64
Folder names show SDL2, but not SDL1 (because it's default?)
Filenames for XP are detailed, for the others generic:
I like the installer option "put all build variants in a subfolder" - what getting in that subfolder really all builds (e.g. win32 installer copies files not only for 32-bit builds, but also for 64-bit builds; win64 installer copies files not only for 64-bit builds, but also for 32-bit builds)? Then it one place you get ALL builds.
Suggestions:
Version string: vYYYY.MM.DD, Target host OS, Build environment SDLx, CPU
v2022.12.26, Windows, VS2019 SDL1, x86
v2022.12.26, Windows, VS2019 SDL2, x86
v2022.12.26, Windows XP, VS2017 SDL1, x86
v2022.12.26, Windows XP, VS2017 SDL2, x86
v2022.12.26, Windows, MinGW SDL1, x86
v2022.12.26, Windows, MinGW SDL2, x86
v2022.12.26, Windows, MinGW SDL1, x86 lowend
v2022.12.26, Windows, MinGW SDL2, x86 lowend
v2022.12.26, Windows, VS2019 SDL1, ARM32
v2022.12.26, Windows, VS2019 SDL2, ARM32
Is your feature request related to a problem? Please describe.
No response
What you want
I think all parameters of the build should be shown in the various "version" places:
Current discrepancies:
I like the installer option "put all build variants in a subfolder" - what getting in that subfolder really all builds (e.g. win32 installer copies files not only for 32-bit builds, but also for 64-bit builds; win64 installer copies files not only for 64-bit builds, but also for 32-bit builds)? Then it one place you get ALL builds.
Suggestions:
Version string: vYYYY.MM.DD, Target host OS, Build environment SDLx, CPU v2022.12.26, Windows, VS2019 SDL1, x86 v2022.12.26, Windows, VS2019 SDL2, x86 v2022.12.26, Windows XP, VS2017 SDL1, x86 v2022.12.26, Windows XP, VS2017 SDL2, x86 v2022.12.26, Windows, MinGW SDL1, x86 v2022.12.26, Windows, MinGW SDL2, x86 v2022.12.26, Windows, MinGW SDL1, x86 lowend v2022.12.26, Windows, MinGW SDL2, x86 lowend v2022.12.26, Windows, VS2019 SDL1, ARM32 v2022.12.26, Windows, VS2019 SDL2, ARM32
v2022.12.26, Windows, VS2019 SDL1, x64 v2022.12.26, Windows, VS2019 SDL2, x64 v2022.12.26, Windows XP, VS2017 SDL1, x64 v2022.12.26, Windows XP, VS2017 SDL2, x64 v2022.12.26, Windows, MinGW SDL1, x64 v2022.12.26, Windows, MinGW SDL2, x64 v2022.12.26, Windows, VS2019 SDL1, ARM64 v2022.12.26, Windows, VS2019 SDL2, ARM64
v2022.12.26, macOS, ? SDL1, x64 v2022.12.26, macOS, ? SDL2, x64 v2022.12.26, macOS, ? SDL1, ARM64 v2022.12.26, macOS, ? SDL2, ARM64
v2022.12.26, Linux, ? SDL1, x86 v2022.12.26, Linux, ? SDL2, x86 v2022.12.26, Linux, ? SDL1, x64 v2022.12.26, Linux, ? SDL2, x64
v2022.12.26, HX DOS, MinGW ?, x86 v2022.12.26, LOADLIN, ? ?, x86 v2022.12.26, macOS High Sierra, ? SDL1, ? v2022.12.26, macOS High Sierra, ? SDL2, ?
Describe alternatives you've considered
No response
Additional information
No response
Have you checked that no similar feature request(s) exist?
Code of Conduct & Contributing Guidelines