diff options
| author | Leitwolf11 | 2026-11-17 15:38:57 +0300 |
|---|---|---|
| committer | Leitwolf11 | 2026-11-17 15:38:57 +0300 |
| commit | 95220a2f22c44815012e5a018d2886986edfad60 (patch) | |
| tree | 8a5f5d2ddff41311b2f4acc84666389e285b47ad | |
| parent | b010a902aa01218b67f4a03e046d03204ef670b2 (diff) | |
| download | catch3-docs/lgpl-as-a-whole.tar.gz | |
Say that the LGPL's conditions differ from case to casedocs/lgpl-as-a-whole
The section listed the duties of a conveyed work as if they were the same
everywhere. They are not, and the section now goes through the cases,
with the section of the LGPL-3.0 each comes from: a shared library that
runs with a modified Catch3 meets the relinking condition by itself
(4 d 1); static linking owes the object files or source of the rest of
the work for relinking (4 d 0); object code with only small parts of the
headers owes the notice and the texts, larger parts such as Catch3's test
macros and templates bring the conditions of a combined work (3, 4);
giving Catch3 itself gives the library, whose modified versions stay
under the LGPL (2, 4); a work in a consumer product also owes installation
information (4 e; GPL-3.0, 6); and handing over within one legal person,
or to someone working only for you under the GPL-3.0's section 2, is not
conveying. The summary says it is not legal advice. The README names the
cases in short.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Ji7xZMYjc4zankoc7hGBE1
| -rw-r--r-- | LICENSES/README.md | 41 | ||||
| -rw-r--r-- | README.md | 7 |
2 files changed, 38 insertions, 10 deletions
diff --git a/LICENSES/README.md b/LICENSES/README.md index b5d916ba..986aad72 100644 --- a/LICENSES/README.md +++ b/LICENSES/README.md @@ -30,17 +30,42 @@ files alone, taken out of Catch3, is under the BSL-1.0 alone. The conditions take effect when Catch3, or a work that contains it, is conveyed to someone else: a test binary, a library or a tool with Catch3 linked in, given or sold to others. Building and running tests on your own -machines and in your own CI conveys nothing. A conveyed work that contains -Catch3 has, among other things, to: +machines and in your own CI conveys nothing. In general a conveyed work that +contains Catch3 has to say prominently that it uses Catch3 and that Catch3 is +under the LGPL, come with copies of the GPL-3.0 and LGPL-3.0 texts, and let +the recipient have the source of that Catch3 and use a modified Catch3 with +the work. -- say prominently that it uses Catch3 and that Catch3 is under the LGPL, and - come with copies of the GPL-3.0 and LGPL-3.0 texts; -- give the source of the Catch3 it contains, with any change made to it; -- let the recipient relink the work with a modified Catch3: by linking Catch3 - as a shared library, or by giving the object files of the rest of the work. +What exactly is owed is not the same in every case. It depends on how Catch3 +is built into the work and how the work is given: + +- **A shared library.** A work that uses Catch3 through a shared library, + one that runs with a modified Catch3 of the same interface put in its + place, meets the relinking condition that way (LGPL-3.0, section 4 d 1). +- **Static linking.** A work with Catch3 linked in statically has to give + the recipient what they need to relink it with a modified Catch3: the + object files or the source of the rest of the work, with what it takes to + link them again (section 4 d 0). +- **Code from the headers.** Test macros and templates of Catch3 compile into + the tests that use them. Object code that takes from Catch3's headers only + numerical parameters, data structure layouts and accessors, or small + macros, inline functions and templates of ten lines or fewer, owes the + notice and the license texts (section 3); larger parts of the headers, as + Catch3's test macros and templates usually are, bring the conditions of a + combined work (section 4). +- **Catch3 itself.** Giving Catch3, as it is or modified, is giving the + library: its source goes with it, and a modified Catch3 stays under the + LGPL-3.0-or-later (sections 2 and 4 of the LGPL, and the GPL-3.0 it builds + on). +- **A device.** A work given as part of a consumer product (a "User Product") + also owes the information needed to install a modified version on the + device (LGPL-3.0, section 4 e; GPL-3.0, section 6). +- **Whether it is conveying at all.** Handing a work over within one legal + person, or to someone who works on it only for you under the terms of the + GPL-3.0's section 2, is not conveying it; the GPL-3.0's definitions decide. The license texts in this directory hold the full conditions; this summary -does not replace them. +does not replace them and is not legal advice. ## Earlier releases @@ -123,6 +123,9 @@ Catch3 as a whole is therefore not under the Boost Software License: whoever uses the library uses its LGPL files, and the BSL-1.0 of the Catch2-originated files does not lift the LGPL's conditions. They take effect when Catch3, or a work that contains it such as a test binary, is given to others; running your -own tests conveys nothing. +own tests conveys nothing. What is owed then is not the same in every case: it +depends on whether Catch3 is linked as a shared library or statically, how +much of its headers a work compiles in, whether Catch3 itself is given, and +whether the work is part of a device. [Using Catch3 as a whole](LICENSES/README.md#using-catch3-as-a-whole) -says what a conveyed work has to do. +goes through each case. |