On 3/14/2012 1:42 PM, Nicolas Desprès wrote:
$ ../_build/bin/cmake -DCMAKE_ENABLE_NINJA=OFF .
$ ../_build/bin/cmake -DCMAKE_ENABLE_NINJA=ON .
$ ninja
ninja: no work to do.
$ ../_build/bin/cmake -DCMAKE_ENABLE_NINJA=OFF .
$ ninja
[...compile 200 outputs...]
Duh, of course, my bad. It is the -DCM
On Wed, Mar 14, 2012 at 6:10 PM, Peter Collingbourne wrote:
> On Wed, Mar 14, 2012 at 10:45:39AM -0400, Bill Hoffman wrote:
>> On 3/14/2012 7:34 AM, Nicolas Desprčs wrote:
>>> Nope if you like in the generated build.ninja "build.ninja" appears
>>> only once as an output using the RERUN_CMAKE rule.
On Wed, Mar 14, 2012 at 10:45:39AM -0400, Bill Hoffman wrote:
> On 3/14/2012 7:34 AM, Nicolas Desprès wrote:
>> Nope if you like in the generated build.ninja "build.ninja" appears
>> only once as an output using the RERUN_CMAKE rule.
>>
>> I rather think it is a bug in ninja of the restat implement
On 3/14/2012 7:34 AM, Nicolas Desprès wrote:
Nope if you like in the generated build.ninja "build.ninja" appears
only once as an output using the RERUN_CMAKE rule.
I rather think it is a bug in ninja of the restat implementation.
What is the way to debug this? Can you get ninja to tell you why
On Wed, Mar 14, 2012 at 12:22 AM, Bill Hoffman wrote:
> It seems that if the CMakeCache.txt changes, and cmake re-runs, ninja
> rebuilds almost ever single .obj file. For example, if I turn on and off
> CMAKE_ENABLE_NINJA, Then it rebuilds all the .obj files instead of
> relinking just a few ex
It seems that if the CMakeCache.txt changes, and cmake re-runs, ninja
rebuilds almost ever single .obj file. For example, if I turn on and
off CMAKE_ENABLE_NINJA, Then it rebuilds all the .obj files instead of
relinking just a few executables since the .obj files are there all
ready. I had
