[Dune] [#1000] Evaluate build system migration from autotools to CMake
Dune
flyspray at dune-project.org
Sun Jun 10 19:31:29 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 - Markus Blatt (mblatt)
----------
IDE's: Have not tested this, but nothing special has to be done on our side. CMake uses a generator (default on Linux is the one for makefiles). So you just switch the generator when calling cmake, e.g. "cmake -G "KDevelop3" ../dune-common" for KDevelop3.
As Sascha already pointed out, one can do DUNE meta projects that include other dune-modules and 3rdParty Software. The dependencies can be automatically downloaded/checkout, configured and built. (Seems especially helpful for courses and lectures and is very user friendly).
Other points:
- We can untilize their test infrastructure for automated, continuous, or distributed user testing and set up a dashboard that displays the results. This will relieve us from the pain of maintaing our own automated test software.
- More platform independance.
----------
More information can be found at the following URL:
http://www.dune-project.org/flyspray/index.php?do=details&task_id=1000#comment3710
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