catch3/CMake/CatchConfigOptions.cmake, branch v3.3.2 Progmasoft Catch3: an independently maintained C++17 test framework with a parallel runner, property checks, snapshots and structured results. Add support for PlayStation platforms (#2562) 2022-11-09T13:47:55+00:00 Masashi Fujita 2022-11-09T13:47:55+00:00 b7f4a2efb808e8d154874e168cec8e0aaf70bd06 * Add new `CATCH_CONFIG` option for using `std::getenv`, because PS does not support env vars * Add PS to platforms that have disabled posix signals. * Small workaround for PS toolchain bug that prevents it from compiling `std::set` with lambda based comparator. 
* Add new `CATCH_CONFIG` option for using `std::getenv`, because PS does not support env vars
* Add PS to platforms that have disabled posix signals.
* Small workaround for PS toolchain bug that prevents it from compiling `std::set` with lambda based comparator.
 Fix references to license file 2022-10-28T09:30:15+00:00 Lars Toenning 2022-10-28T09:22:53+00:00 f1084fb30990fe40c8f5b70034970c7eb4e1da72 The license file was renamed with 6a502cc2f5fedd59b3495b58708f0d6d987ed9e1 
The license file was renamed with 6a502cc2f5fedd59b3495b58708f0d6d987ed9e1
Fix building as shared library with MSVC. 2022-09-24T13:15:50+00:00 Dimitrij Mijoski 2022-09-17T12:58:52+00:00 c0e582e65955f84312548bcee36b962a013f262f 






Add default reporter for Bazel integration (#2399)
2022-04-08T16:01:59+00:00

Lukasz Okraszewski

2022-04-08T16:01:59+00:00

cb551b4f6d338020322eb39a2f3747c81896a1ba

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ý <martin.horenovsky@gmail.com>




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ý <martin.horenovsky@gmail.com>






Refactor colour handling to prepare for per-reporter colour modes
2022-03-28T11:10:13+00:00

Martin Hořeňovský

2022-03-27T21:35:41+00:00

1a8a793178d50b74b0f9a0adb3eec937b61039a9

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.





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.







Allow passing compile-time configuration options through CMake
2022-02-18T10:15:08+00:00

Martin Hořeňovský

2022-02-02T14:36:58+00:00

33ffc3b6fc1cdb2815a87476b06ff9afb2f2a6bd