[Dune] Globally installed modules vs. local modules

[Oliver Sander]

To me this sounds like a bug.  If there is a local installation in DUNE_CONTROL_PATH,
then this should overrule any global installation.

Now that I think of it though, I remember seeing similar problems a while ago.
The problem was that even if dunecontrol only uses the local modules, you will
have /usr/include and /usr/lib in your paths for other random reasons, like
the std lib.  You may then get the wrong module (i.e., the global one), if /usr
happens to appear in the list of compiler options before the path to your
local installation.

Best,
Oliver

On 27.06.2016 12:58, Lukas Böger wrote:
> Sounds appealingly simple, but leads to the exact same cmake failure as
> before: dune-alugrid is found in /usr and then the global
> Headercheck.cmake is used instead of the local one...
> 
> Best
> Lukas
> 
> On 27.06.2016 12:03, Christoph Grüninger wrote:
>> Hi Lukas,
>> you could also use dunecontrol's --only option and
>> explicitly state all modules you have local. Then
>> dunecontrol won't try to use the installed module.
>>
>> Bye
>> Christoph
>>
> 
> _______________________________________________
> Dune mailing list
> Dune at dune-project.org
> http://lists.dune-project.org/mailman/listinfo/dune
> 

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 473 bytes
Desc: OpenPGP digital signature
URL: <https://lists.dune-project.org/pipermail/dune/attachments/20160627/5f2b409f/attachment.sig>