Which Scheme implementations are able to produce standalone executables that are easy to deploy on other computers that do not have any Scheme implementations installed?
In the Common Lisp world, for example, there is Embeddable Common Lisp (ECL). I have noticed that in the land of Lisp family languages, it is not common for implementations to have the ability to produce standalone executables. :-(
Racket
Chicken
https://wiki.call-cc.org/man/5/Deployment#static-linking
Linking your application statically will include the runtime library in the executable
Almost all Common Lisp implementations have a way to save an image of the system to an executable file.
Does gcc still produce standalone executables on Linux? Even if you manage to statically link libc your program now has to be GPL/LGPL.
Even if you manage to statically link libc your program now has to be GPL/LGPL.
No, your program will not have to be GPL/LGPL. That is one of the common misconceptions about the LGPL. You are allowed to distribute a closed source proprietary software that statically links an LGPL-licensed library as long as you provide object files that allow users to re-link your closed sourced software to the library.
This is covered by the GPL FAQ: https://www.gnu.org/licenses/gpl-faq.html#LGPLStaticVsDynamic
>>6
That's really interesting, I had no idea. The LGPL is even more flexible than I thought.
>>5
If you don't like glibc, you can use another libc. But what would the license have to do with producing executables?