[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: CMAKE_LIBRARY_PATH & co.
From: |
Ludovic Courtès |
Subject: |
Re: CMAKE_LIBRARY_PATH & co. |
Date: |
Mon, 14 Oct 2013 14:31:40 +0200 |
User-agent: |
Gnus/5.130007 (Ma Gnus v0.7) Emacs/24.3 (gnu/linux) |
Lluís Batlle i Rossell <address@hidden> skribis:
> On Mon, Oct 14, 2013 at 09:15:25AM +0200, Ludovic Courtès wrote:
>> Andreas Enge <address@hidden> skribis:
>>
>> > commit e78fd4ca636a19bc286747f8d91bda22cd8f08fd
>> > Author: Andreas Enge <address@hidden>
>> > Date: Sun Oct 13 18:02:49 2013 +0200
>> >
>> > guix: Make cmake build system aware of usual paths.
>> >
>> > * guix/build/cmake-build-system.scm (configure): Set
>> > CMAKE_LIBRARY_PATH to
>> > LIBRARY_PATH and CMAKE_INCLUDE_PATH to CPATH.
>>
>> I think this was discussed on IRC yesterday, but I’m not sure I got it:
>> are these needed because CMake explicitly looks for files in these
>> directories instead of just running the compiler?
>>
>> That would be a serious flaw of CMake.
>
> Right; for what I understand, FIND_LIBRARY, and FIND_PATH, look for files in
> specific directories. Then cmake takes a decision based in what it finds. A
> shared object, a static lib, ...
Blech.
That’s flawed because CMake’s auto-configuration rules behave
differently from what the compiler/linker actually do. So its
configuration phase may end up making decisions based on erroneous
information.
Thanks for the explanations,
Ludo’.