[Dune] [#987] build system: do not force all modules to place their headers in $DUNE_MODULE_ROOT/dune/ (Attachment added)
flyspray at dune-project.org
Mon Dec 5 19:23:30 CET 2011
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
A new Flyspray task has been opened. Details are below.
User who did this - Andreas Lauser (andlaus)
Attached to Project - Dune
Summary - build system: do not force all modules to place their headers in $DUNE_MODULE_ROOT/dune/
Task Type - Bug Report
Category - Common
Status - Unconfirmed
Assigned To -
Operating System - Linux
Severity - Low
Priority - Normal
Reported Version - 2.1
Due in Version - Undecided
Due Date - Undecided
Details - Dumux currently places all headers in $DUNE_MODULE_ROOT/dumux/. Since
the DUNE_CHECK_MODULES expects all headers to be placed in the module's
'dune/' subdirectory, the current solution used by Dumux is to completely
replace the DUNE_CHECK_MODULES autoconf macro with a custom version. Since,
IMHO, this is a pretty bad hack, it would be nice if the DUNE build
system would not force all modules to be called 'dune-$FOO'. The attached
patch does just this.
In order to not having to change existing dune-$FOO.m4 files, the patch first
looks whether the path given as an argument to DUNE_CHECK_MODULES is relative to the
$MODULE_ROOT/dune directory (which is the current behavior), if the header
is not found there, it checks whether the path is relative to $MODULE_ROOT.
N.B. this patch is for the 2.1 branch, use it at your own risk for
trunk. It would be great if it could be also included in the 2.1
branch as it would allow us at IWS to drop the currently used hack
for our next release.
One or more files have been attached.
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