<feed xmlns='http://www.w3.org/2005/Atom'>
<title>catch3/docs, branch build/catch3-link-names</title>
<subtitle>Progmasoft Catch3: an independently maintained C++17 test framework with a parallel runner, property checks, snapshots and structured results.</subtitle>
<link rel='alternate' type='text/html' href='https://git.progmasoft.com/catch3/'/>
<entry>
<title>Keep the debug "d": a debug build is not the same library</title>
<updated>2026-11-17T19:00:16+00:00</updated>
<author>
<name>Leitwolf11</name>
</author>
<published>2026-11-17T19:00:16+00:00</published>
<link rel='alternate' type='text/html' href='https://git.progmasoft.com/catch3/commit/?id=0f987a33220d3217a4e3e8416ce413f9983e3aa0'/>
<id>0f987a33220d3217a4e3e8416ce413f9983e3aa0</id>
<content type='text'>
The previous commit dropped CMake's DEBUG_POSTFIX on every platform. A
debug build is a different library from a release build, so it keeps its
own name, libCatch3d and libCatch3Maind. The released archives and the
Progmasoft Linux packages hold release builds, which are libCatch3 and
libCatch3Main, so an installed Catch3 links with -lCatch3 and -lCatch3Main.

The Ubuntu install job links with -lCatch3Maind -lCatch3d in its Debug
rows and with -lCatch3Main -lCatch3 in its Release rows; pkg-config gives
the right names in both. The documentation names both.

Checked locally: a Release install gives libCatch3.a and libCatch3Main.a, a
Debug install libCatch3d.a and libCatch3Maind.a; a test links and passes
with each, and pkg-config prints the matching flags.

Co-Authored-By: Claude Opus 5.5 &lt;noreply@anthropic.com&gt;
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
The previous commit dropped CMake's DEBUG_POSTFIX on every platform. A
debug build is a different library from a release build, so it keeps its
own name, libCatch3d and libCatch3Maind. The released archives and the
Progmasoft Linux packages hold release builds, which are libCatch3 and
libCatch3Main, so an installed Catch3 links with -lCatch3 and -lCatch3Main.

The Ubuntu install job links with -lCatch3Maind -lCatch3d in its Debug
rows and with -lCatch3Main -lCatch3 in its Release rows; pkg-config gives
the right names in both. The documentation names both.

Checked locally: a Release install gives libCatch3.a and libCatch3Main.a, a
Debug install libCatch3d.a and libCatch3Maind.a; a test links and passes
with each, and pkg-config prints the matching flags.

Co-Authored-By: Claude Opus 5.5 &lt;noreply@anthropic.com&gt;
</pre>
</div>
</content>
</entry>
<entry>
<title>Drop the debug "d" on Windows too</title>
<updated>2026-11-17T18:54:57+00:00</updated>
<author>
<name>Leitwolf11</name>
</author>
<published>2026-11-17T18:54:57+00:00</published>
<link rel='alternate' type='text/html' href='https://git.progmasoft.com/catch3/commit/?id=95e2cad52aa1dd573ea0e6075af0fdd49c30a78a'/>
<id>95e2cad52aa1dd573ea0e6075af0fdd49c30a78a</id>
<content type='text'>
Released archives and the Progmasoft Linux packages hold release builds,
so a debug build needs no file name of its own on any platform. Catch3 and
Catch3Main now have the same names in every configuration everywhere.

Co-Authored-By: Claude Opus 5.5 &lt;noreply@anthropic.com&gt;
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Released archives and the Progmasoft Linux packages hold release builds,
so a debug build needs no file name of its own on any platform. Catch3 and
Catch3Main now have the same names in every configuration everywhere.

Co-Authored-By: Claude Opus 5.5 &lt;noreply@anthropic.com&gt;
</pre>
</div>
</content>
</entry>
<entry>
<title>Let an installed Catch3 link with -lCatch3 and -lCatch3Main in every build</title>
<updated>2026-11-17T18:54:23+00:00</updated>
<author>
<name>Leitwolf11</name>
</author>
<published>2026-11-17T18:54:23+00:00</published>
<link rel='alternate' type='text/html' href='https://git.progmasoft.com/catch3/commit/?id=5da6bc7b6ab2f857d7be70d5ad966636b33d8164'/>
<id>5da6bc7b6ab2f857d7be70d5ad966636b33d8164</id>
<content type='text'>
CMake named the files of a debug build libCatch3d and libCatch3Maind, so
-lCatch3 and -lCatch3Main found only a release install. Premake named the
library with main Catch3WithMain, and Xmake named both after their targets
(catch3, catch3_main).

The files are now libCatch3 and libCatch3Main in CMake, Meson, Xmake and
Premake. The debug "d" stays on Windows only, where a debug build links the
debug C runtime and a debug and a release build are installed side by side.
Target names and the pkg-config modules catch3 and catch3-with-main are
unchanged.

The Ubuntu install job now compiles a test against the installed tree with
-lCatch3Main -lCatch3, and again through pkg-config, and runs both.
docs/progmasoft-catch3.md says how to link without a build system.

Checked locally: a CMake Debug install gives libCatch3.a and
libCatch3Main.a, and a test links both ways and passes; Xmake builds
libCatch3.a and libCatch3Main.a; Premake's makefiles name libCatch3.a and
libCatch3Main.a.

Co-Authored-By: Claude Opus 5.5 &lt;noreply@anthropic.com&gt;
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
CMake named the files of a debug build libCatch3d and libCatch3Maind, so
-lCatch3 and -lCatch3Main found only a release install. Premake named the
library with main Catch3WithMain, and Xmake named both after their targets
(catch3, catch3_main).

The files are now libCatch3 and libCatch3Main in CMake, Meson, Xmake and
Premake. The debug "d" stays on Windows only, where a debug build links the
debug C runtime and a debug and a release build are installed side by side.
Target names and the pkg-config modules catch3 and catch3-with-main are
unchanged.

The Ubuntu install job now compiles a test against the installed tree with
-lCatch3Main -lCatch3, and again through pkg-config, and runs both.
docs/progmasoft-catch3.md says how to link without a build system.

Checked locally: a CMake Debug install gives libCatch3.a and
libCatch3Main.a, and a test links both ways and passes; Xmake builds
libCatch3.a and libCatch3Main.a; Premake's makefiles name libCatch3.a and
libCatch3Main.a.

Co-Authored-By: Claude Opus 5.5 &lt;noreply@anthropic.com&gt;
</pre>
</div>
</content>
</entry>
<entry>
<title>Parse the JUnit report with defusedxml</title>
<updated>2026-11-16T11:52:55+00:00</updated>
<author>
<name>Leitwolf11</name>
</author>
<published>2026-11-16T11:52:55+00:00</published>
<link rel='alternate' type='text/html' href='https://git.progmasoft.com/catch3/commit/?id=430cd475da04bf3dba74c96b273c4f12570d6577'/>
<id>430cd475da04bf3dba74c96b273c4f12570d6577</id>
<content type='text'>
Bandit flags every parser of the standard xml package, fromstring too,
as they expand entities. defusedxml refuses entity declarations and
external references, so the hand-written DOCTYPE check goes.

- Ubuntu and Fedora jobs that build the extra tests install the
  distribution package python3-defusedxml.
- The macOS job installs requirements-tests.txt, pinned by hash, into the
  Python of actions/setup-python, and CMake uses that Python.
- The contributing guide names the requirement.

Claude-Session: https://claude.ai/code/session_01Ji7xZMYjc4zankoc7hGBE1
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Bandit flags every parser of the standard xml package, fromstring too,
as they expand entities. defusedxml refuses entity declarations and
external references, so the hand-written DOCTYPE check goes.

- Ubuntu and Fedora jobs that build the extra tests install the
  distribution package python3-defusedxml.
- The macOS job installs requirements-tests.txt, pinned by hash, into the
  Python of actions/setup-python, and CMake uses that Python.
- The contributing guide names the requirement.

Claude-Session: https://claude.ai/code/session_01Ji7xZMYjc4zankoc7hGBE1
</pre>
</div>
</content>
</entry>
<entry>
<title>Prepare the Bazel Central Registry entry as progmasoft_catch3</title>
<updated>2026-11-15T20:08:05+00:00</updated>
<author>
<name>Leitwolf11</name>
</author>
<published>2026-11-15T20:08:05+00:00</published>
<link rel='alternate' type='text/html' href='https://git.progmasoft.com/catch3/commit/?id=67c3ef401b34716f7214374ff0d6c24b3c50a149'/>
<id>67c3ef401b34716f7214374ff0d6c24b3c50a149</id>
<content type='text'>
- MODULE.bazel names the module progmasoft_catch3, the name it has in
  the registry, with bazel_compatibility &gt;=8.0.0; //tools:version finds
  the version under the new name.
- .bcr/ holds the templates publish-to-bcr fills: metadata, source (the
  GitHub archive of the catch3-* tag) and the presubmit, which runs the
  test module on Debian, Ubuntu, macOS (x86-64 and arm64) and Windows
  with Bazel 8.x and 9.x.
- tests/Progmasoft/BazelModule is a module that depends on Catch3 as a
  user's does, through //:catch3_main and through //:catch3 with its
  own main. The root ignores it; Bazel Builds tests it with Bazel 8.x
  and 9.x on Ubuntu and Windows.
- Publish to BCR runs when a catch3-* release is published, or by hand
  for a tag, and opens the registry pull request from the fork of the
  maintainer, without attestations.
- The integration guide says how a module depends on progmasoft_catch3.

Claude-Session: https://claude.ai/code/session_01Ji7xZMYjc4zankoc7hGBE1
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
- MODULE.bazel names the module progmasoft_catch3, the name it has in
  the registry, with bazel_compatibility &gt;=8.0.0; //tools:version finds
  the version under the new name.
- .bcr/ holds the templates publish-to-bcr fills: metadata, source (the
  GitHub archive of the catch3-* tag) and the presubmit, which runs the
  test module on Debian, Ubuntu, macOS (x86-64 and arm64) and Windows
  with Bazel 8.x and 9.x.
- tests/Progmasoft/BazelModule is a module that depends on Catch3 as a
  user's does, through //:catch3_main and through //:catch3 with its
  own main. The root ignores it; Bazel Builds tests it with Bazel 8.x
  and 9.x on Ubuntu and Windows.
- Publish to BCR runs when a catch3-* release is published, or by hand
  for a tag, and opens the registry pull request from the fork of the
  maintainer, without attestations.
- The integration guide says how a module depends on progmasoft_catch3.

Claude-Session: https://claude.ai/code/session_01Ji7xZMYjc4zankoc7hGBE1
</pre>
</div>
</content>
</entry>
<entry>
<title>License Catch3's Progmasoft files under LGPL-3.0-or-later</title>
<updated>2026-11-15T11:01:10+00:00</updated>
<author>
<name>Leitwolf11</name>
</author>
<published>2026-11-15T11:01:10+00:00</published>
<link rel='alternate' type='text/html' href='https://git.progmasoft.com/catch3/commit/?id=5c865488e762dec616a0c483d0fc07250123c387'/>
<id>5c865488e762dec616a0c483d0fc07250123c387</id>
<content type='text'>
Every Progmasoft-authored file moves from MPL-2.0 WITH
AdditionRef-Progmasoft-Exception-2.0 to LGPL-3.0-or-later, from 0.5.0
on. Catch2-originated files keep BSL-1.0, and the vendored yyjson and
pugixml keep MIT.

- LICENSES/ holds the LGPL-3.0 text and the GPL-3.0 text it builds on,
  both as published by the FSF; the MPL-2.0 and Progmasoft Exception
  texts go, since no file uses them any more.
- Five files that came from Catch2 and were rewritten by Progmasoft
  (.clang-format, the issue and pull request templates, SECURITY.md)
  keep Catch2's notice next to Progmasoft's and say
  LGPL-3.0-or-later AND BSL-1.0.
- //tools:check expects the new header of Progmasoft files; the
  amalgamation notes say LGPL-3.0-or-later and the amalgamated files
  are regenerated; meson's project license is BSL-1.0 and
  LGPL-3.0-or-later.
- README gains a License section; LICENSES/README.md, contributing.md
  and progmasoft-catch3.md describe the new split and that releases
  before 0.5.0 keep the license they were published under.

Every commit to Progmasoft's files since the fork is the maintainer's.

Claude-Session: https://claude.ai/code/session_01Ji7xZMYjc4zankoc7hGBE1
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Every Progmasoft-authored file moves from MPL-2.0 WITH
AdditionRef-Progmasoft-Exception-2.0 to LGPL-3.0-or-later, from 0.5.0
on. Catch2-originated files keep BSL-1.0, and the vendored yyjson and
pugixml keep MIT.

- LICENSES/ holds the LGPL-3.0 text and the GPL-3.0 text it builds on,
  both as published by the FSF; the MPL-2.0 and Progmasoft Exception
  texts go, since no file uses them any more.
- Five files that came from Catch2 and were rewritten by Progmasoft
  (.clang-format, the issue and pull request templates, SECURITY.md)
  keep Catch2's notice next to Progmasoft's and say
  LGPL-3.0-or-later AND BSL-1.0.
- //tools:check expects the new header of Progmasoft files; the
  amalgamation notes say LGPL-3.0-or-later and the amalgamated files
  are regenerated; meson's project license is BSL-1.0 and
  LGPL-3.0-or-later.
- README gains a License section; LICENSES/README.md, contributing.md
  and progmasoft-catch3.md describe the new split and that releases
  before 0.5.0 keep the license they were published under.

Every commit to Progmasoft's files since the fork is the maintainer's.

Claude-Session: https://claude.ai/code/session_01Ji7xZMYjc4zankoc7hGBE1
</pre>
</div>
</content>
</entry>
<entry>
<title>Release Catch3 0.4.0</title>
<updated>2026-11-15T09:17:43+00:00</updated>
<author>
<name>Leitwolf11</name>
</author>
<published>2026-11-15T09:17:43+00:00</published>
<link rel='alternate' type='text/html' href='https://git.progmasoft.com/catch3/commit/?id=6f4d3fa3328d6fb78f9a41f45282c11758872c9c'/>
<id>6f4d3fa3328d6fb78f9a41f45282c11758872c9c</id>
<content type='text'>
Every place that states the version says 0.4.0, written by
bazelisk run //tools:version -- 0.4.0, and the single-file distribution
carries it. The release notes describe the release: per-test coverage
with --coverage, secret-looking variables withheld from workers unless
--pass-env names them, the repository tools in C++17 under Bazel, and
versions with three numbers again.

Claude-Session: https://claude.ai/code/session_01Ji7xZMYjc4zankoc7hGBE1
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Every place that states the version says 0.4.0, written by
bazelisk run //tools:version -- 0.4.0, and the single-file distribution
carries it. The release notes describe the release: per-test coverage
with --coverage, secret-looking variables withheld from workers unless
--pass-env names them, the repository tools in C++17 under Bazel, and
versions with three numbers again.

Claude-Session: https://claude.ai/code/session_01Ji7xZMYjc4zankoc7hGBE1
</pre>
</div>
</content>
</entry>
<entry>
<title>Number versions MAJOR.MINOR.PATCH in the version tool</title>
<updated>2026-11-14T19:03:45+00:00</updated>
<author>
<name>Leitwolf11</name>
</author>
<published>2026-11-14T19:03:45+00:00</published>
<link rel='alternate' type='text/html' href='https://git.progmasoft.com/catch3/commit/?id=2d21d2e0f9c6e0789e9c55d6cba611234dc61a60'/>
<id>2d21d2e0f9c6e0789e9c55d6cba611234dc61a60</id>
<content type='text'>
Progmasoft repositories use Semantic Versioning since 2026-11-12, but
//tools:version still knew the four-number counters: given 0.4.0 it
wrote 0.4.0.0 everywhere, and --next stepped the fourth number.

- A Version is three numbers; ParseVersion takes exactly three, without
  leading zeros, and FormatVersion writes three.
- --next is the next patch release. It also follows a four-number
  version as the rule says: the fourth number goes and the patch rises,
  so 0.3.0.2 is followed by 0.3.1.
- ReleaseNotesOf finds a section by the version it was published as.
  Its fallback for "D = 0" read the fourth element of what is now a
  three-element array; it is gone.
- Tests for the new parsing, NextPatch and release-note lookup;
  docs/contributing.md and the tool's usage say what the tool does.

Claude-Session: https://claude.ai/code/session_01Ji7xZMYjc4zankoc7hGBE1
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Progmasoft repositories use Semantic Versioning since 2026-11-12, but
//tools:version still knew the four-number counters: given 0.4.0 it
wrote 0.4.0.0 everywhere, and --next stepped the fourth number.

- A Version is three numbers; ParseVersion takes exactly three, without
  leading zeros, and FormatVersion writes three.
- --next is the next patch release. It also follows a four-number
  version as the rule says: the fourth number goes and the patch rises,
  so 0.3.0.2 is followed by 0.3.1.
- ReleaseNotesOf finds a section by the version it was published as.
  Its fallback for "D = 0" read the fourth element of what is now a
  three-element array; it is gone.
- Tests for the new parsing, NextPatch and release-note lookup;
  docs/contributing.md and the tool's usage say what the tool does.

Claude-Session: https://claude.ai/code/session_01Ji7xZMYjc4zankoc7hGBE1
</pre>
</div>
</content>
</entry>
<entry>
<title>Merge branch 'devel' into feature/per-test-coverage</title>
<updated>2026-11-13T20:24:25+00:00</updated>
<author>
<name>Leitwolf</name>
</author>
<published>2026-11-13T20:24:25+00:00</published>
<link rel='alternate' type='text/html' href='https://git.progmasoft.com/catch3/commit/?id=826735e00bfac9967a7979eae5a42cb49eac851b'/>
<id>826735e00bfac9967a7979eae5a42cb49eac851b</id>
<content type='text'>
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
</pre>
</div>
</content>
</entry>
<entry>
<title>Fix the coverage review findings: branches, stale reports, exit status</title>
<updated>2026-11-13T18:55:26+00:00</updated>
<author>
<name>Leitwolf11</name>
</author>
<published>2026-11-13T18:55:26+00:00</published>
<link rel='alternate' type='text/html' href='https://git.progmasoft.com/catch3/commit/?id=454cca9b63991416f4d9bd1ca350f1ae14e278e7'/>
<id>454cca9b63991416f4d9bd1ca350f1ae14e278e7</id>
<content type='text'>
- gcov is run with --branch-probabilities; without it the JSON has no
  branches, so GCC runs had none in coverage.json and coverage.lcov.
- PrepareCoverageDirectory also removes coverage.json, coverage.lcov and
  coverage.profdata of an earlier run, so a run that writes no reports
  leaves none to be read as its own.
- WriteCoverageReports returns notes and failures apart. A profile the
  tools cannot read or a report that cannot be written counts as a missing
  report and fails a run whose tests passed; no profiles or missing tools
  stay notes. The paths are announced only for the reports written.
- ProfiledAttempt takes the last attempt whose profile exists, so a final
  retry or repeat that crashed before writing one no longer hides the
  coverage of the attempt before it.
- The per-test llvm-profdata/llvm-cov and gcov runs use as many threads
  as the run had workers; results keep the order of the tests.

Tests: earlier reports removed and no failure without profiles; an
attempt without a profile gives way to an earlier one; the fixture gains a
branch taken one way, checked in the combined LCOV for both LLVM and gcov.
Amalgamation regenerated.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
- gcov is run with --branch-probabilities; without it the JSON has no
  branches, so GCC runs had none in coverage.json and coverage.lcov.
- PrepareCoverageDirectory also removes coverage.json, coverage.lcov and
  coverage.profdata of an earlier run, so a run that writes no reports
  leaves none to be read as its own.
- WriteCoverageReports returns notes and failures apart. A profile the
  tools cannot read or a report that cannot be written counts as a missing
  report and fails a run whose tests passed; no profiles or missing tools
  stay notes. The paths are announced only for the reports written.
- ProfiledAttempt takes the last attempt whose profile exists, so a final
  retry or repeat that crashed before writing one no longer hides the
  coverage of the attempt before it.
- The per-test llvm-profdata/llvm-cov and gcov runs use as many threads
  as the run had workers; results keep the order of the tests.

Tests: earlier reports removed and no failure without profiles; an
attempt without a profile gives way to an earlier one; the fixture gains a
branch taken one way, checked in the combined LCOV for both LLVM and gcov.
Amalgamation regenerated.
</pre>
</div>
</content>
</entry>
</feed>
