[Dune] Policy module configuration

[Dr. Markus Blatt]

Hi, 

I did not think of changing just the flags. What i had in mind was e.g. Configure one module with lapack and another without.

I would suppose that this is a mistake of the user.

Markus
--
Dr. Markus Blatt - HPC-Simulation-Software & Services
Hans-Bunte-Str. 8-10, 69123 Heidelberg, Germany
Tel. +49 (0)160 97590858 Fax +49 (0)322 1108991658



"Carsten Gräser" <graeser at math.fu-berlin.de> schrieb:

>Hi,
>Am 24.04.2012 14:22, schrieb Christoph Grüninger:
>> Hi Markus,
>> I don't know what a user is supposed to do but I know that some of my
>> colleagues use optimized configuration for Dune core modules (like
>> -march, -O3, -DNDEBUG) and DuMuX (like -g, -Wwhatever). The idea is
>to
>> build Dune core modules very rarely and profit from the speed of the
>> optimized code.
>I also do this and use no optimization for my applications
>during development.
>
>> At least with configure cache this went terribly wrong.
>You can simply circumvent this using dunecontrol option files,
>each with its own configure cache: one with and one without
>optimization. My applications are configured without optimization
>but have an extra make target for optimization. (In fact there
>are even more for PGO.)
>
>Best,
>Carsten
>
>> 
>> For myself I try to avoid different configurations for the modules.
>> 
>> Ciao
>> Christoph
>
>_______________________________________________
>Dune mailing list
>Dune at dune-project.org
>http://lists.dune-project.org/mailman/listinfo/dune