Linking Cakelisp statically or dynamically with other modules is making a combined work based on Cakelisp. Thus, the terms and conditions of the GNU General Public License cover the whole combination.
As a special exception, the copyright holders of Cakelisp give you permission to combine Cakelisp program with free software programs or libraries that are released under the GNU LGPL and with independent modules that communicate with Cakelisp solely through the Cakelisp Compile-time Code Execution interface. You may copy and distribute such a system following the terms of the GNU GPL for Cakelisp and the licenses of the other code concerned, provided that you include the source code of that other code when and as the GNU GPL requires distribution of source code and provided that you do not modify the Cakelisp Compile-time Code Execution interface.
Note that people who make modified versions of Cakelisp are not obligated to grant this special exception for their modified versions; it is their choice whether to do so. The GNU General Public License gives permission to release a modified version without this exception; this exception also makes it possible to release a modified version which carries forward this exception. If you modify the Cakelisp Compile-time Code Execution interface, this exception does not apply to your modified version of Cakelisp, and you must remove this exception when you distribute your modified version.
This exception is an additional permission under section 7 of the GNU General Public License, version 3 ("GPLv3")
The /Too Long, Didn't Read/ is this: If you make something using Cakelisp as a tool, you have full rights over the terms of that thing. If you make something which includes Cakelisp as part of the distribution to end users (for example, an IDE which has Cakelisp built-in, or a game which supports end-user modding via Cakelisp), you must comply with ~GPL-3.0-or-later~.
- "Cakelisp": All the files, excluding ~runtime/~ within the Cakelisp repository, and the binaries generated by these files (excludes binaries generated /with/ Cakelisp binaries, i.e. user runtime code)
- "Runtime": Code which runs outside Cakelisp, after generation has been completed. This can also be termed the "user's generated program"
- "Cakelisp runtime": The files in ~runtime/~
Cakelisp is copyright (C) 2020 Macoy Madson ~<email@example.com>~.
Licensed under ~GPL-3.0-or-later~, with added [[https://www.gnu.org/licenses/gpl-faq.en.html#LinkingOverControlledInterface][Linking Over Controlled Interface]] exception. There is no SPDX identifier for this exception, as far as I know.
~runtime/~ is licensed under ~MIT~ License.
Contact ~firstname.lastname@example.org~ if you would like to negotiate an exception for your use-case.
* License Exception
The ~LICENSE_EXCEPTION~ file allows the creation of plug-ins for compile-time code execution under licenses that are not the GPL. *However*, if you distribute Cakelisp with these plug-ins, you still need to distribute the source code of the plug-ins.
If your program is intended to be GPL, you must release any compile time code used to build the program along with the program's source code, because it is otherwise impossible to build the program, therefore violating the GPL.
* Cakelisp runtime exception
The files in ~runtime/~ are under MIT license instead of GPL. This is to ensure your freedom to determine license for your non-derivative work by providing minimal constraints.
*IMPORTANT:* This section is not legally binding, and is only meant to help the reader quickly determine whether their use-case /may/ be appropriate.
Cakelisp's licensing was chosen to protect my efforts and help the community. Generally, I think the party with the most effort spent should be able to determine the terms of that work.
If you make something utilizing Cakelisp, your something is where most of the work is. If you make something which has Cakelisp embedded as an integral/supplementary part, our work amounts are now closer to even, and you need to obey the ~GPL-3.0-or-later~. Anything you generate with Cakelisp is your own, and any Cakelisp code you write is your own, but as soon as you start distributing Cakelisp itself, you must obey the terms.
From a high level:
- Cakelisp distribution is under ~GPL-3.0-or-later~
- Cakelisp runtime distribution is under ~MIT~ License
- Runtime distribution is under whatever terms the copyright holder decides, provided that they comply with all other software they include in the runtime. If you e.g. link to a GPL library in your runtime (e.g. Cakelisp itself), you then need to comply with the GPL
** Things which are permitted
- Releasing a proprietary game/software project written in Cakelisp, without releasing any of the source code, or sharing any similar licenses. Broadly speaking, what you make /with/ Cakelisp is entirely your own
- Building a proprietary game/software project using Cakelisp's build system
- Releasing products utilizing Cakelisp to the end user, so long as the terms of the ~GPL-3.0-or-later~ are met
** Things which are *not* permitted
- Releasing a proprietary game/software project which ships any of Cakelisp, *excluding* ~runtime/~, without also releasing the source code of that project
- Distributing modified versions of Cakelisp without also releasing the full modified source code
- i.e., you must follow ~GPL-3.0-or-later~ if you actually "ship" any Cakelisp code