On 13/05/2013 14:54, Stephan Witt wrote:
Am 13.05.2013 um 11:20 schrieb Benjamin Piwowarski 
<benjamin.piwowar...@lip6.fr>:
When make install from CMake produces an useful result like the auto-tools make 
install
we have a good starting point.  Then one can change the mentioned shell script 
or add its
functionality to the CMake package build.

I don't have a strong preference towards any build system, but the only point 
is that having to take care of updating both each time is cumbersome and 
error-prone. So that's why I am ready to work on it - but only if cmake is 
chosen as the only build system (otherwise, it does not make sense to put so 
much effort in maintaining both working build systems).
Yes, and I have to admit I never had a problem with multiple build systems.
Surely because auto-tools and CMake both are working fine for me most of the 
time.
OK, then maybe this is not worth investing time in it.
Let's wait what others say.

I think it is worth investing time in it. At the meeting everybody agreed that we should have one build system in the long run. But to make cmake official we need to achieve the following: 1) implement the missing feature of autotools in cmake, especially for MAC as I believe that Linux/Unix is complete thanks to the hard work of Peter first and then Kornel.
2) Deprecate autotools
3) update the documentation (Readme/Wiki/etc)
4) allow some time for developers to fully switch to cmake
5) remove autotools when we are done, hopefully before 2.1, if not for 2.2.

The one point that still needs discussion is GLOB versus explicit file listing. While GLOB is IMO a very nice feature I know and understand others dislike it. So I guess we also need to do this in cmake.

So Benjamin, if you are willing to help it will be very good for the project.

Final point: This is just a proposal based on the feedback I received during the meeting. Other developers might disagree of course and in this case we should discuss more :-)

Cheers,
Abdel.


Reply via email to