n: "Malfettone, Kris"
> > An: Bill Hoffman , "cmake@cmake.org"
>
> > Betreff: Re: [CMake] Ninja on windows ( latest ninja from git, cmake
> 2.8.9 )
>
> > Sure although you will need to map a network drive to properly recreate
> > i
;
>
> Betreff: Re: [CMake] Ninja on windows ( latest ninja from git, cmake 2.8.9 )
> Sure although you will need to map a network drive to properly recreate
> it.
>
> In a project have:
> CMakeLists.txt
> cmake_minimum_required(VERSION 2.8)
> project(foo)
> #include_d
roject has nothing to do.
I know that it is probably a pain to setup this test, thank you for taking the
time to do it.
-Kris
-Original Message-
From: cmake-boun...@cmake.org [mailto:cmake-boun...@cmake.org] On Behalf Of
Bill Hoffman
Sent: Wednesday, August 15, 2012 4:36 PM
T
On 8/15/2012 2:48 PM, Malfettone, Kris wrote:
So I think I found the issue. When the include directories are
specified via the network path ( \\machine\dir\ ) vs. a drive letter (
N:\dir ) ninja always thinks they are out of date. This is a pretty big
hurdle for us since our toolchain files can
:53 PM
To: Malfettone, Kris
Cc: David Cole; cmake@cmake.org
Subject: Re: [CMake] Ninja on windows ( latest ninja from git, cmake 2.8.9 )
2012/8/14 Malfettone, Kris :
> So I found the "-d explain" option of ninja and it says that it thinks
> my boost libraries / other library inc
2012/8/14 Malfettone, Kris :
> So I found the “–d explain” option of ninja and it says that it thinks my
> boost libraries / other library includes are “dirty”. The only think I can
> think of here is that they are on a network drive and not on my local
> machine. Any thoughts on that?
If those
On 8/14/2012 2:23 PM, Malfettone, Kris wrote:
Nothing special in my opinion. I am trying to reproduce it with
something simpler than my code base. With an ultra trivial CMake setup
it works fine. Is there some sort of debugging I can enable to see why
it thinks the files are changed?
-Kris
om: Malfettone, Kris [mailto:kris.malfett...@sig.com]
Sent: Tuesday, August 14, 2012 2:23 PM
To: David Cole; Malfettone, Kris
Cc: cmake@cmake.org
Subject: RE: [CMake] Ninja on windows ( latest ninja from git, cmake 2.8.9 )
Nothing special in my opinion. I am trying to reproduce it with something
simpler than
...@kitware.com]
Sent: Tuesday, August 14, 2012 12:58 PM
To: Malfettone, Kris
Cc: cmake@cmake.org
Subject: Re: [CMake] Ninja on windows ( latest ninja from git, cmake 2.8.9 )
Definitely not known. In fact, the opposite is true here on my ninja build
trees for CMake itself. A no-op build results in a "no
Definitely not known. In fact, the opposite is true here on my ninja build
trees for CMake itself. A no-op build results in a "no work to do" message
from ninja.
Is there anything unusual about your CMakeLists.txt files?
Are your source files accidentally dated in the future? (Did you just
return
I am trying to use ninja on windows. Everything seems to work correctly (
compilation, linking, install rules, etc... ) except for testing whether or not
a file has changed. No matter the state of the tree, ninja always builds the
entire project. I tried searching the bug tracker and mailing
11 matches
Mail list logo
