diff options
| author | Leitwolf11 | 2026-11-17 15:26:28 +0300 |
|---|---|---|
| committer | Leitwolf11 | 2026-11-17 15:26:28 +0300 |
| commit | b010a902aa01218b67f4a03e046d03204ef670b2 (patch) | |
| tree | 374f241d6a6ca65193b1ae96f9d0596bdc836934 /tests/SelfTest/UsageTests/ToStringVector.tests.cpp | |
| parent | eea3be11a9e1a047442d71626557e57c3061da1a (diff) | |
| download | catch3-b010a902aa01218b67f4a03e046d03204ef670b2.tar.gz | |
Say that Catch3 as a whole cannot set the LGPL aside
The license map said which file is under which license, but not what
that means for someone who uses Catch3 as a whole. LICENSES/README.md
gains "Using Catch3 as a whole": the library and its build targets
contain LGPL-3.0-or-later files, so whoever uses Catch3 uses them and
their conditions apply; the BSL-1.0 of the Catch2-originated files neither
lifts nor replaces them, and only a part made of Catch2-originated files
alone, taken out of Catch3, is under the BSL-1.0 alone. It says when the
conditions take effect (conveying Catch3 or a work that contains it, such
as a test binary; running one's own tests conveys nothing) and what a
conveyed work has to do: a prominent notice with the GPL-3.0 and LGPL-3.0
texts, the source of the Catch3 it contains, and a way to relink with a
modified Catch3 (a shared library, or the object files of the rest). The
license texts hold the full conditions. The paragraphs after it get the
headings "Earlier releases" and "Keeping the boundary". The README says
the same in short and links the section.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Ji7xZMYjc4zankoc7hGBE1
Diffstat (limited to 'tests/SelfTest/UsageTests/ToStringVector.tests.cpp')
0 files changed, 0 insertions, 0 deletions