14 ms·
Agreed. Also didn't get why he felt complying with the terms of the LGPL for a statically-linked .exe would be so much of a problem. Just put the object files
by kelnos 2y ago
Agreed. Also didn't get why he felt complying with the terms of the LGPL for a statically-linked .exe would be so much of a problem. Just put the object files and build script in a zip file, and upload it to the same webserver where you plan to put the program. Add a line in the "About" dialog (or whatever) pointing to it. Done.
- eptcyka 2y agoWhilst I don't understand the users who are hell bent on having a single-executable work, if you have users who are hell bent on using but a single executable, you have to meet them where they're at.
- jnhzubh 2y agoIn my experience Windows users don't care about the statically linked part What they care about is having an executable and not needing a zip with dlls And that is trivially achievable by bundling the dlls into the exe file
- mavamaarten 2y agoAlso trivially achievable by making an installer instead of shipping separate files. People are really used to that pattern.