3 ms·
The compiled program. So you could give users the compiler (under AGPL) and source code to your program under a proprietary license. But you probably wouldn't,
by e12e 7y ago
The compiled program. So you could give users the compiler (under AGPL) and source code to your program under a proprietary license. But you probably wouldn't, I guess.
Any compiled artifacts would need to be distributed (if they are distributed) under AGPL.
I'm a fan of Free software, but much prefer GPL/LGPL for compilers and runtimes/standard libraries.
- mumblemumble 7y agoIt depends. . . if the compiled program is 100% compiler output, then it's fine. If the compiled program ends up including bits of library code that ships with the compiler, then, in the absence of special exceptions, the output will also need to be AGPL-licensed. That's exactly why, for example, LLVM ships with a modified version of the Apache license: http://llvm.org/foundation/relicensing/LICENSE.txt http://llvm.org/foundation/relicensing/LICENSE.txt (see the bottom)
- e12e 7y agoI'm having trouble seeing how this won't incorporate a substantial runtime in all builds? It's a full scheme system...