It has been merged into master:
https://github.com/martine/ninja/commit/abd33d5e3b11ae5470f62cbce49723a4cf62870d
So you can now use the normal Ninja for your project.
Cheers,
-Nico
2012/3/14 Chuck Atkins chuck.atk...@kitware.com:
Yep. That fixed it. Thanks!
Chuck Atkins
RD Engineer,
The following issue has been SUBMITTED.
==
http://public.kitware.com/Bug/view.php?id=13066
==
Reported By:Kashif Rasul
Assigned To:
On 3/24/2012 12:41 AM, Rolf Eike Beer wrote:
I have seen a strange behaviour on my (openSUSE) Linux host running on AMD64.
Sometimes during my Find* module tests libraries in /usr/lib64 were not found.
It took me a while until I noticed what was going on there:
FIND_LIBRARY_USE_LIB64_PATHS is
The following issue has been SUBMITTED.
==
http://public.kitware.com/Bug/view.php?id=13067
==
Reported By:Matthew McCormick
Assigned To:
On 3/26/2012 10:49 AM, Rolf Eike Beer wrote:
For the beginning I added 2 obvious cleanups to the lib64-cleanup topic on
stage. If noone objects I'll merge them to next soon.
Thanks. In FindBLAS:
if (WIN32)
set(_libdir ENV LIB)
elseif (APPLE)
-set(_libdir /usr/local/lib
Rolf Eike Beer wrote:
ok, I now have:
find_path(VAR header.h
HINTS /opt/p1
PATHS /opt/p2
PATH_SUFFIXES foo)
This would search in /usr/include, /usr/foo, /opt/p1/foo, /opt/p2/foo, but
neither in /opt/p1/include nor /opt/p2/include. Correct?
As far as I understand, it will search:
Am Montag, 26. März 2012, 11:01:38 schrieb Brad King:
On 3/26/2012 10:49 AM, Rolf Eike Beer wrote:
For the beginning I added 2 obvious cleanups to the lib64-cleanup topic
on stage. If noone objects I'll merge them to next soon.
Thanks. In FindBLAS:
if (WIN32)
set(_libdir ENV
On 3/26/2012 11:49 AM, Rolf Eike Beer wrote:
Thanks, fixed. And added a patch that removes this in a bunch of other modules.
Nice. Looks good so far. I noticed in the context of some of your
changes lines like
/usr/local/lib/fltk2
/usr/lib/fltk2
This pattern can be replaced by
On 3/26/2012 1:35 PM, Rolf Eike Beer wrote:
Well, that is in fact an interesting question. If /usr is in the default
paths list and lib is a default suffix, will specifying fltk2 as suffix
result in /usr, /usr/lib, and /usr/fltk2, or will also /usr/lib/fltk2 be
searched. The latter would mean
On Saturday 24 March 2012, Rolf Eike Beer wrote:
I have seen a strange behaviour on my (openSUSE) Linux host running on
AMD64. Sometimes during my Find* module tests libraries in /usr/lib64 were
not found. It took me a while until I noticed what was going on there:
FIND_LIBRARY_USE_LIB64_PATHS
10 matches
Mail list logo