On 29. Jan, 2011, at 3:06 , Óscar Fuentes wrote:
> Michael Wild writes:
>
The point I (and Andreas) wanted to make is that you can just add it. If
it's a system directory, CMake is going to filter it out (I didn't say
duplicates, I said "doesn't even show up ONCE", which means *z
Michael Wild writes:
>>> The point I (and Andreas) wanted to make is that you can just add it. If
>>> it's a system directory, CMake is going to filter it out (I didn't say
>>> duplicates, I said "doesn't even show up ONCE", which means *zero* times).
>>
>> This is a moot point, because /usr/loc
On 01/28/2011 06:44 AM, Michael Wild wrote:
> On 01/27/2011 08:08 PM, Óscar Fuentes wrote:
>> Michael Wild writes:
>>
Okay, cmake removes duplicated directories that already are on the
list. So what?
First, I hope that cmake does not optimize this series:
A B C A
On 01/28/2011 09:55 AM, Hendrik Sattler wrote:
> Zitat von "Michael Wild" :
>
>> Now, if you want to mix-and-match, by having this include-path:
>> -I/usr/include -I/usr/local/include
>>
>> (i.e. use /usr/include/foo.h and /usr/local/include/bar.h) you're in
>> trouble, because CMake will filter o
Zitat von "Michael Wild" :
Now, if you want to mix-and-match, by having this include-path:
-I/usr/include -I/usr/local/include
(i.e. use /usr/include/foo.h and /usr/local/include/bar.h) you're in
trouble, because CMake will filter out the /usr/include directory,
leaving you with /usr/local/incl
On 01/27/2011 08:08 PM, Óscar Fuentes wrote:
> Michael Wild writes:
>
>>> Okay, cmake removes duplicated directories that already are on the
>>> list. So what?
>>>
>>> First, I hope that cmake does not optimize this series:
>>>
>>> A B C A
>>>
>>> ... to this:
>>>
>>> A B C
>>>
>>> or to this:
>>
Andreas Pakulat writes:
> On 27.01.11 20:08:06, Óscar Fuentes wrote:
>> Okay, so if I have this:
>>
>> check_include_file(foo.h HAVE_FOO_H)
>>
>> and it succeeds, I have no guarantees that a program such as this:
>>
>> #include "foo.h"
>>
>> will compile, becasue foo.h may be found on a direc
On 27.01.11 20:08:06, Óscar Fuentes wrote:
> Michael Wild writes:
> > IMHO you're the one trying to jump through hoops that aren't even there...
>
> Okay, so if I have this:
>
> check_include_file(foo.h HAVE_FOO_H)
>
> and it succeeds, I have no guarantees that a program such as this:
>
> #inc
Michael Wild writes:
>> Okay, cmake removes duplicated directories that already are on the
>> list. So what?
>>
>> First, I hope that cmake does not optimize this series:
>>
>> A B C A
>>
>> ... to this:
>>
>> A B C
>>
>> or to this:
>>
>> B C A
>>
>> Removing adjacent duplicates is fine,
On 01/27/2011 04:49 PM, Óscar Fuentes wrote:
> Michael Wild writes:
>
No, the bug is in your cmake code. You shouldn't use
USER_DEFINED_INCLUDE_DIR to decide wether to add the path to the
include-directories or not. Instead use the FFI_INCLUDE_PATH variable to
decide that, it
Michael Wild writes:
>>> No, the bug is in your cmake code. You shouldn't use
>>> USER_DEFINED_INCLUDE_DIR to decide wether to add the path to the
>>> include-directories or not. Instead use the FFI_INCLUDE_PATH variable to
>>> decide that, it won't hurt if FFI_INCLUDE_PATH happens to be /usr/inc
On 01/27/2011 03:53 PM, Óscar Fuentes wrote:
> Andreas Pakulat writes:
>
>> On 27.01.11 16:13:09, arrowdodger wrote:
>>> Hello. On FreeBSD everything, that distributes with system goes to /usr (i
>>> mean includes go to /usr/includes and libs to /usr/lib) and all 3d party
>>> stuff goes to /usr/l
Andreas Pakulat writes:
> On 27.01.11 16:13:09, arrowdodger wrote:
>> Hello. On FreeBSD everything, that distributes with system goes to /usr (i
>> mean includes go to /usr/includes and libs to /usr/lib) and all 3d party
>> stuff goes to /usr/local.
>> And the compiler is intentionally set to loo
On 27.01.11 16:13:09, arrowdodger wrote:
> Hello. On FreeBSD everything, that distributes with system goes to /usr (i
> mean includes go to /usr/includes and libs to /usr/lib) and all 3d party
> stuff goes to /usr/local.
> And the compiler is intentionally set to look only in /usr/include. The same
Hello. On FreeBSD everything, that distributes with system goes to /usr (i
mean includes go to /usr/includes and libs to /usr/lib) and all 3d party
stuff goes to /usr/local.
And the compiler is intentionally set to look only in /usr/include. The same
is for linker - it's looking for libs only in /u
15 matches
Mail list logo
