[Dune] [#1000] Migrate build system from autotools to CMake
Dune
flyspray at dune-project.org
Mon May 7 18:10:31 CEST 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 - Markus Blatt (mblatt)
----------
This question goes to all people familiar with CMake:
What should we use as the CMake name for modules. Currently, e.g. for dune-common the cmake files expect the name to be DuneCommon. This means that we can find dune-common by calling "find_package(DuneCommon)". Calling cmake -D DuneCommon_Dir=<build_tree|installation_tree> this works fine.
Unfortunately, with this convention we have to set -D <MODULE_NAME>_DIR for every module. If we would change the module to include the dash, e.g. to dune-common, Dune-Common or DUNE-COMMONN , calling cmake with "-D CMAKE_PREFIX_PATH=<dir-with-all-the-build-dir>" would find the builddirs of the modules in "<dir-with-all-the-build-dir>/<module-name-ignoring-case>*" automatically. This would make it easier to use the cmake version of DUNE. On the other hand the variables in the cmake package configuration files will look kind of weired: e.g. DUNE-COMMON_LIBRARIES.
What should the naming convention be in your opinion?
----------
More information can be found at the following URL:
http://www.dune-project.org/flyspray/index.php?do=details&task_id=1000#comment3490
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