catch3/BUILD.bazel, branch v3.2.1 Progmasoft Catch3: an independently maintained C++17 test framework with a parallel runner, property checks, snapshots and structured results. Fix Bazel build (#2563) 2022-11-11T15:54:22+00:00 Vertexwahn 2022-11-11T15:54:22+00:00 41990e0fe6274d716134eecfd4d780e976c8fbf5 Also adds a CI job for Bazel build to avoid future breakage. 
Also adds a CI job for Bazel build to avoid future breakage.
 Make Bazel work with CATCH_CONFIG_SHARED_LIBRARY 2022-09-27T20:06:12+00:00 Vertexwahn 2022-09-26T16:09:29+00:00 243cf7160811ccee23af8fc9f4911438f200fa4e 






Bazel build: Update of skylib
2022-09-27T20:06:12+00:00

Vertexwahn

2022-09-18T13:03:38+00:00

4bb7e02a9c48dc916d2bdf45105f90785a7e01d2












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.







Fix borken Bazel build
2022-03-16T13:01:18+00:00

Vertexwahn

2022-03-11T21:07:50+00:00

634cdb4efefcbd9ee8816e9507013f10de20a78d












Add Bazel support for the v3 branch
2020-05-26T12:49:49+00:00

Valentin Tolmer

2020-05-25T13:44:57+00:00

d05a8e2e24927509bd1ac97c86e0d00398086621