Hi,
I have created some Python bindings for CTest. The goal was to create an easy
way for Python projects that I work with to be able to wrap their Python
compilation log (if there was one), dynamically generate CTests and/or wrap
their existing testing commands, do any additional testing
Am Donnerstag, 18. Oktober 2018, 17:48:28 CEST schrieb Ray Donnelly:
> Hi CMake developers,
>
> Why do I need to know the necessary verbose flag to make each back-end
> that cmake --build calls emit more information? If forces my build
> script to switch on the platform in a really ugly way for
On 10/18/2018 11:48 AM, Ray Donnelly wrote:
> Why do I need to know the necessary verbose flag to make each back-end
> that cmake --build calls emit more information? If forces my build
> script to switch on the platform in a really ugly way for something
> I'd consider a very important feature
Hi CMake developers,
Why do I need to know the necessary verbose flag to make each back-end
that cmake --build calls emit more information? If forces my build
script to switch on the platform in a really ugly way for something
I'd consider a very important feature (you already hardcode various