<feed xmlns='http://www.w3.org/2005/Atom'>
<title>catch3/src, 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>Ask read() for at most SSIZE_MAX bytes in PipeReader::Read</title>
<updated>2026-11-17T16:00:44+00:00</updated>
<author>
<name>Leitwolf11</name>
</author>
<published>2026-11-17T16:00:44+00:00</published>
<link rel='alternate' type='text/html' href='https://git.progmasoft.com/catch3/commit/?id=7c3b73b14a3f0714c8eca3ad1a69bc1963ae773d'/>
<id>7c3b73b14a3f0714c8eca3ad1a69bc1963ae773d</id>
<content type='text'>
POSIX leaves a read() request above SSIZE_MAX to the implementation, and
the count it returns could not then be told from an error. The POSIX
branch of PipeReader::Read now asks for the smaller of the buffer size and
SSIZE_MAX, as the Windows branch already limits one ReadFile call. The
caller sees no change: a short read was always possible, and the reader
loops until the pipe ends.

The single-file distribution is regenerated from the sources.

Checked: bazelisk test //... (3 of 3 pass), bazelisk run
//tools:amalgamate -- --check, clang-format dry-run with -Werror.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
POSIX leaves a read() request above SSIZE_MAX to the implementation, and
the count it returns could not then be told from an error. The POSIX
branch of PipeReader::Read now asks for the smaller of the buffer size and
SSIZE_MAX, as the Windows branch already limits one ReadFile call. The
caller sees no change: a short read was always possible, and the reader
loops until the pipe ends.

The single-file distribution is regenerated from the sources.

Checked: bazelisk test //... (3 of 3 pass), bazelisk run
//tools:amalgamate -- --check, clang-format dry-run with -Werror.
</pre>
</div>
</content>
</entry>
<entry>
<title>Merge branch 'devel' into security/bounded-strings</title>
<updated>2026-11-15T19:58:40+00:00</updated>
<author>
<name>Leitwolf</name>
</author>
<published>2026-11-15T19:58:40+00:00</published>
<link rel='alternate' type='text/html' href='https://git.progmasoft.com/catch3/commit/?id=21ce423a12523559abf83f7a2ed83e042efc418d'/>
<id>21ce423a12523559abf83f7a2ed83e042efc418d</id>
<content type='text'>
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
</pre>
</div>
</content>
</entry>
<entry>
<title>Bound three string and XML reads that analysis flagged</title>
<updated>2026-11-15T19:29:48+00:00</updated>
<author>
<name>Leitwolf11</name>
</author>
<published>2026-11-15T19:29:48+00:00</published>
<link rel='alternate' type='text/html' href='https://git.progmasoft.com/catch3/commit/?id=79f624d693b4fc3167c239c3eca47c858799333f'/>
<id>79f624d693b4fc3167c239c3eca47c858799333f</id>
<content type='text'>
- On macOS, the path from _NSGetExecutablePath is cut at its first NUL
  found inside the buffer, in place of strlen, which reads until a NUL
  wherever it is.
- The table test measures its C strings with std::string_view.
- The Bazel reporter test reads the JUnit report and rejects a document
  type before parsing it, so no entity, external or internal, is ever
  expanded.

Claude-Session: https://claude.ai/code/session_01Ji7xZMYjc4zankoc7hGBE1
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
- On macOS, the path from _NSGetExecutablePath is cut at its first NUL
  found inside the buffer, in place of strlen, which reads until a NUL
  wherever it is.
- The table test measures its C strings with std::string_view.
- The Bazel reporter test reads the JUnit report and rejects a document
  type before parsing it, so no entity, external or internal, is ever
  expanded.

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>Make the start lock a never-destroyed object</title>
<updated>2026-11-13T21:56:32+00:00</updated>
<author>
<name>Leitwolf11</name>
</author>
<published>2026-11-13T21:56:32+00:00</published>
<link rel='alternate' type='text/html' href='https://git.progmasoft.com/catch3/commit/?id=5ad02bccfcb925df02d1273901b6e248d477c5fa'/>
<id>5ad02bccfcb925df02d1273901b6e248d477c5fa</id>
<content type='text'>
A function-local static std::mutex has an exit-time destructor, which
the macOS build rejects with -Wexit-time-destructors. The lock is now
allocated once and never destroyed, which also keeps it usable by a
thread that starts a child while the process exits.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
A function-local static std::mutex has an exit-time destructor, which
the macOS build rejects with -Wexit-time-destructors. The lock is now
allocated once and never destroyed, which also keeps it usable by a
thread that starts a child while the process exits.
</pre>
</div>
</content>
</entry>
<entry>
<title>Start child processes one at a time; run gcov without a directory</title>
<updated>2026-11-13T20:24:10+00:00</updated>
<author>
<name>Leitwolf11</name>
</author>
<published>2026-11-13T20:24:10+00:00</published>
<link rel='alternate' type='text/html' href='https://git.progmasoft.com/catch3/commit/?id=b26486d68ece48a1dfdb208a9f3f1bd8acab0382'/>
<id>b26486d68ece48a1dfdb208a9f3f1bd8acab0382</id>
<content type='text'>
Reading the coverage profiles on several threads broke an assumption of
ChildProcess::Start on POSIX: it changes the working directory of the
whole process around posix_spawn. Two gcov runs started at once could
both run in one test's directory, so on the GCC job the map of
"Subtracts one" showed what "Adds one" reached.

- ChildProcess::Start holds a lock while a child starts, on POSIX and
  Windows, so the directory change and the handles a child inherits never
  overlap with another start.
- gcov gets the absolute path of the data file and no working directory,
  so no directory changes while profiles are read in parallel.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Reading the coverage profiles on several threads broke an assumption of
ChildProcess::Start on POSIX: it changes the working directory of the
whole process around posix_spawn. Two gcov runs started at once could
both run in one test's directory, so on the GCC job the map of
"Subtracts one" showed what "Adds one" reached.

- ChildProcess::Start holds a lock while a child starts, on POSIX and
  Windows, so the directory change and the handles a child inherits never
  overlap with another start.
- gcov gets the absolute path of the data file and no working directory,
  so no directory changes while profiles are read in parallel.
</pre>
</div>
</content>
</entry>
</feed>
