[Dune] [#1000] Evaluate build system migration from autotools to CMake
Dune
flyspray at dune-project.org
Sun Jun 10 21:22:43 CEST 2012
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
The following task has a new comment added:
FS#1000 - Evaluate build system migration from autotools to CMake
User who did this - Christian Engwer (christi)
----------
Hi Alf,
"-Dune is not about making and maintaining build environments, cmake will hopefully relieve more resources to focus on improving Dune functionality."
You hit the nail and that is the reason I'm trying to get an estimate of effort and benefits related to cmake. But this also the reason I'm not interested in so advertisement... the buildsystem in dune is a bit more complicated, but not because of autotools but due to the structure of dune. All the "greate advatages with cmake" just hold for cmake _and_ autotools, because we currently find two main build-systems in the wild.
Regarding the IDE integration I know the "official" state, but thhis doesn't tell me anything about the state for dune... will it work just out-of-the box? We first have to try. And it might even bring an other burden, in case we have to do some additional tricks for some IDEs... then well have to test these as well... And all these "it can easily done" comments I've heard too often, we heard the same for automake and again the detail might be a lot more tricky.
I'm honestly looking forward to learn more about the experiences Markus and Christoph collected, because that is the only way to estimate the amount of work and if it is worth the effort.
----------
More information can be found at the following URL:
http://www.dune-project.org/flyspray/index.php?do=details&task_id=1000#comment3712
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
mailing list