multiple windows make quirks
Free GNUWin32 utility packages
Status: Beta
Brought to you by:
michaelis
Menu
▾
▴
#37 multiple windows make quirks
Hi,
I am interested in seeing a more intuitive make port for Windows. I recently endeavored to install make ephemerally on a Windows Jenkins node, and noticed some oddities about the GnuWin32 make distribution.
- Strangely, make for Windows is packaged as two separate ZIP files. This causes confusion and accidents. Can we please merge these together into a single archive file?
- When the second ZIP's DLL's are missing from the make installation, then make behaves quite strangely. In PowerShell, it silently dies with a zero, fake healthy exit code. No text message displays in the console. In Command Prompt via non-tty contexts (e.g. Jenkins CI/CD jobs), no text message displays in the console. The only sign of installation corruption arrives by running make.exe from a graphical (e.g. RDP) session. The current error handling is inadequate.
- EXE installers are often ambiguous. I never know whether they are meant to launch an application directly vs. install it. Can we please promote the classical installer to a modern MSI?
