Board index » kylix » How can *anything* compiled on Linux stay "closed-source?"
How can *anything* compiled on Linux stay "closed-source?"
2005-03-31 12:44:16 PM
Yet another opportunity to execute several projects on Linux (with
Kylix) has appeared, but numerous issues (beyond several learning
curves) seem to be so problematic that it seems (potentially) cheaper
and easier to stay within the known Windows environment (even though
we'd seriously like to defenestrate!). Chief among the most important
concerns are the nature of the licensing, particularly the viral nature
of the GPL. All of these projects MUST remain closed-source, and must
not have any terms imposed on them beyond what the owner wants.
Using Linux as purely a user of any number of programs is great, but
once one approaches it as a closed-source developer, it gets a lot
trickier. It would be great if someone could point out that the
following is wrong, or incorrectly interpreted, but according to my
1) Linux is licensed under GPL.
2) All of GNU is, of course, licensed under GPL.
3) GPL doesn't even allow LINKING to GPL code from non-GPL code, NOT
EVEN from MPL-licensed code! (one source on this: "That is, a module
covered by the GPL and a module covered by the MPL cannot legally be
linked together. We urge you not to use the MPL for this reason." from
4) Even the slightest program, one that calls system in libc, or a
"Hello World," or probably even a do-nothing empty project that's
compiled is likely to connect with this GPL-ed code.
Under this light, I don't even understand how Kylix can have non-GPL
versions! (Of course, we don't even know if the GPL is really a valid
Can anyone offer _PROOF_ that code written under Kylix Enterprise is
NOT virally "contaminated" by the GPL?