CppUnit CMake build system

[Bernhard Seßler]

Hi,

On 13.12.2013 16:56, Markus Mohrhard wrote:
> Hey,
> 
> 
> 2013/12/12 Bernhard Seßler <bernhard.sessler at corscience.de>
> 
>> Hi @cppunit developers / users,
>>

<snip>

>>
> 
> 
> So in general I'm very happy to accept patches: I'm just not convinced that
> another build system is the right step right now. We provide MSVC
> project/solution files for Windows and a autotools based build system for
> the rest that works quite well. Additionally I understand the current build
> system and feel competent to maintain it which I'm not sure I will be with
> a cmake based build system.

Yes, I know that it would be a drastic change right now - I've already done
quite some work on my branch cleaning things up.
What's really bothering me is the fact, that there is a separate (manually
generated) configuration headers for each compiler (except autotools / gcc). On
my CMake branch this header (config-auto.h) is now automatically generated for
every compiler CMake supports for instance.

> 
> However if it helps we can surely push build system patches into a branch
> which might make it easier for you to keep the patches in sync with the
> cppunit development. How does this sound to you?

Sounds like a plan. This way it's also easier for people getting used to a new
build system (and the ones who don't like to use it still get their autotools
based build system). I also understand that not everyone has CMake installed on
their machines.
Apart from that I cannot guarantee that my build system will be working out of
the box on every platform that's currently supported by cppunit (as I simply
don't have enough resources to test it on every platform), so it's surely a wise
choice maintaining it in a separate branch.

> 
> Regards,
> Markus
> 
> 

Thanks for the feedback. I will clean up my branch and post patches here in the
next few days (hopefully until the end of the week, then it would be some sort
of Christmas gift ^^).

Regards,
Bernhard