<feed xmlns='http://www.w3.org/2005/Atom'>
<title>catch3/BUILD.bazel, branch constexpr_approx</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>Introduce CATCH_CONFIG_PREFIX_MESSAGES to only prefix a few logging related macros. (#2544)</title>
<updated>2023-07-19T15:04:43+00:00</updated>
<author>
<name>Riom</name>
</author>
<published>2023-07-19T15:04:43+00:00</published>
<link rel='alternate' type='text/html' href='https://git.progmasoft.com/catch3/commit/?id=4acc51828f7f93f3b2058a63f54d112af4034503'/>
<id>4acc51828f7f93f3b2058a63f54d112af4034503</id>
<content type='text'>
* Add missing include for VxWorks build.

std::min is defined in algorithm provides std::min. It appears to be transitively included for most platforms. For VxWorks however this explicit include is required.

* Add option CATCH_CONFIG_PREFIX_MESSAGES to selectively prefix message macros only.

In contrast to CATCH_CONFIG_PREFIX_ALL, this will only prefix the following macros:
I.e. INFO, UNSCOPED_INFO, WARN and CATCH_CAPTURE

This is mainly useful for codebases that use INFO or WARN for their own logging macros.</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
* Add missing include for VxWorks build.

std::min is defined in algorithm provides std::min. It appears to be transitively included for most platforms. For VxWorks however this explicit include is required.

* Add option CATCH_CONFIG_PREFIX_MESSAGES to selectively prefix message macros only.

In contrast to CATCH_CONFIG_PREFIX_ALL, this will only prefix the following macros:
I.e. INFO, UNSCOPED_INFO, WARN and CATCH_CAPTURE

This is mainly useful for codebases that use INFO or WARN for their own logging macros.</pre>
</div>
</content>
</entry>
<entry>
<title>Add new config option: STATIC_ANALYSIS_SUPPORT</title>
<updated>2023-05-28T22:55:20+00:00</updated>
<author>
<name>Martin Hořeňovský</name>
</author>
<published>2023-05-12T15:13:21+00:00</published>
<link rel='alternate' type='text/html' href='https://git.progmasoft.com/catch3/commit/?id=dba9197ec71ed64c6f08c7ce73f1af5bc3331f3c'/>
<id>dba9197ec71ed64c6f08c7ce73f1af5bc3331f3c</id>
<content type='text'>
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
</pre>
</div>
</content>
</entry>
<entry>
<title>Fix Bazel build (#2563)</title>
<updated>2022-11-11T15:54:22+00:00</updated>
<author>
<name>Vertexwahn</name>
</author>
<published>2022-11-11T15:54:22+00:00</published>
<link rel='alternate' type='text/html' href='https://git.progmasoft.com/catch3/commit/?id=41990e0fe6274d716134eecfd4d780e976c8fbf5'/>
<id>41990e0fe6274d716134eecfd4d780e976c8fbf5</id>
<content type='text'>
Also adds a CI job for Bazel build to avoid future breakage.</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Also adds a CI job for Bazel build to avoid future breakage.</pre>
</div>
</content>
</entry>
<entry>
<title>Make Bazel work with CATCH_CONFIG_SHARED_LIBRARY</title>
<updated>2022-09-27T20:06:12+00:00</updated>
<author>
<name>Vertexwahn</name>
</author>
<published>2022-09-26T16:09:29+00:00</published>
<link rel='alternate' type='text/html' href='https://git.progmasoft.com/catch3/commit/?id=243cf7160811ccee23af8fc9f4911438f200fa4e'/>
<id>243cf7160811ccee23af8fc9f4911438f200fa4e</id>
<content type='text'>
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
</pre>
</div>
</content>
</entry>
<entry>
<title>Bazel build: Update of skylib</title>
<updated>2022-09-27T20:06:12+00:00</updated>
<author>
<name>Vertexwahn</name>
</author>
<published>2022-09-18T13:03:38+00:00</published>
<link rel='alternate' type='text/html' href='https://git.progmasoft.com/catch3/commit/?id=4bb7e02a9c48dc916d2bdf45105f90785a7e01d2'/>
<id>4bb7e02a9c48dc916d2bdf45105f90785a7e01d2</id>
<content type='text'>
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
</pre>
</div>
</content>
</entry>
<entry>
<title>Add default reporter for Bazel integration (#2399)</title>
<updated>2022-04-08T16:01:59+00:00</updated>
<author>
<name>Lukasz Okraszewski</name>
</author>
<published>2022-04-08T16:01:59+00:00</published>
<link rel='alternate' type='text/html' href='https://git.progmasoft.com/catch3/commit/?id=cb551b4f6d338020322eb39a2f3747c81896a1ba'/>
<id>cb551b4f6d338020322eb39a2f3747c81896a1ba</id>
<content type='text'>
When the added Bazel configuration flag is enabled,
a default JUnit reporter will be added if the XML
envrioment variable is defined.
Fix include paths for generated config header.
Enable Bazel config by default when building with
Bazel.


Co-authored-by: Martin Hořeňovský &lt;martin.horenovsky@gmail.com&gt;</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
When the added Bazel configuration flag is enabled,
a default JUnit reporter will be added if the XML
envrioment variable is defined.
Fix include paths for generated config header.
Enable Bazel config by default when building with
Bazel.


Co-authored-by: Martin Hořeňovský &lt;martin.horenovsky@gmail.com&gt;</pre>
</div>
</content>
</entry>
<entry>
<title>Refactor colour handling to prepare for per-reporter colour modes</title>
<updated>2022-03-28T11:10:13+00:00</updated>
<author>
<name>Martin Hořeňovský</name>
</author>
<published>2022-03-27T21:35:41+00:00</published>
<link rel='alternate' type='text/html' href='https://git.progmasoft.com/catch3/commit/?id=1a8a793178d50b74b0f9a0adb3eec937b61039a9'/>
<id>1a8a793178d50b74b0f9a0adb3eec937b61039a9</id>
<content type='text'>
This includes always compiling the ANSI and None colour
implementations, as they don't need to touch any platform
specific APIs, and removing their respective compile-time
configuration options.

Because the Win32 colour implementation requires Win32-specific
APIs, it is still hidden behind a compile-time toggle,
`CATCH_CONFIG_COLOUR_WIN32` (renamed from `..._COLOUR_WINDOWS`).

The commandline options for colours were also changed. The
option now uses different name, and allows to select between
different implementations, rather than changing whether
the compiled-in colour implementation is used through
"yes/no/default" options.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
This includes always compiling the ANSI and None colour
implementations, as they don't need to touch any platform
specific APIs, and removing their respective compile-time
configuration options.

Because the Win32 colour implementation requires Win32-specific
APIs, it is still hidden behind a compile-time toggle,
`CATCH_CONFIG_COLOUR_WIN32` (renamed from `..._COLOUR_WINDOWS`).

The commandline options for colours were also changed. The
option now uses different name, and allows to select between
different implementations, rather than changing whether
the compiled-in colour implementation is used through
"yes/no/default" options.
</pre>
</div>
</content>
</entry>
<entry>
<title>Fix borken Bazel build</title>
<updated>2022-03-16T13:01:18+00:00</updated>
<author>
<name>Vertexwahn</name>
</author>
<published>2022-03-11T21:07:50+00:00</published>
<link rel='alternate' type='text/html' href='https://git.progmasoft.com/catch3/commit/?id=634cdb4efefcbd9ee8816e9507013f10de20a78d'/>
<id>634cdb4efefcbd9ee8816e9507013f10de20a78d</id>
<content type='text'>
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
</pre>
</div>
</content>
</entry>
<entry>
<title>Add Bazel support for the v3 branch</title>
<updated>2020-05-26T12:49:49+00:00</updated>
<author>
<name>Valentin Tolmer</name>
</author>
<published>2020-05-25T13:44:57+00:00</published>
<link rel='alternate' type='text/html' href='https://git.progmasoft.com/catch3/commit/?id=d05a8e2e24927509bd1ac97c86e0d00398086621'/>
<id>d05a8e2e24927509bd1ac97c86e0d00398086621</id>
<content type='text'>
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
</pre>
</div>
</content>
</entry>
</feed>
