[Dune] [#1000] Migrate build system from autotools to CMake
flyspray at dune-project.org
Fri Mar 2 10:01:04 CET 2012
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
The following task has a new comment added:
FS#1000 - Migrate build system from autotools to CMake
User who did this - Sascha Zelzer (sascha)
As an external user of Dune, I wanted to add to the discussion that I would hugely welcome a CMake build system. Although my opinion is certainly biased (I am the main developer and maintainer of the CMake build system of our medical imaging toolkit (MITK) ), I see the main advantage in CMake's cross-platform ability and generation of native project files (make files, VS solution files, XCode project files, etc.). And it would make my job much easier to integrate DUNE in MITK (but that is obviously not a reason for DUNE to use CMake ;-) ).
Of course CMake also has it's quirks - as any other build system I know. But IMHO, if the CMake build system is done in a way such that it only exposes the most important build options to beginners (using the CMake GUI to configure the project), the initial adoption barrier for DUNE could be lowered. After reading about dunecontrol and familiarising myself with it, I found it nice to work with but it was still yet another tool to learn. CMake on the other hand is adopted by many projects and keeps gaining users.
If the DUNE CMake build system reaches a non-experimental status, I would be pleased to test it and give feedback, if you are interested.
Thanks for the efforts you are putting into the CMake discussion/investigation.
More information can be found at the following URL:
You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above.
More information about the Dune