catch3
Progmasoft Catch3: an independently maintained C++17 test framework with a parallel runner, property checks, snapshots and structured results.
Clonegit clone https://git.progmasoft.com/catch3
Say that the LGPL's conditions differ from case to case
- Commit
95220a2f22c44815012e5a018d2886986edfad60- Author
- Leitwolf11 ·
- Parents
b010a902aa01
Changes
LICENSES/README.md | 41 +++++++++++++++++++++++++++++++++-------- 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 diff --git a/README.md b/README.md index 5ba5baec..28e72c11 100644 --- a/README.md +++ b/README.md @@ -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.