OK, so ninja does not seem to work on windows for me...
I got ninja from here:
git://github.com/martine/ninja.git
branch master
I got cmake from here:
remotes/stage/ninja-generator
I removed the if(UNIX) in the cmake tree and built cmake with ninja
support.
I have tried with both spaces
On 15.02.2012 19:31, Bill Hoffman wrote:
OK, so ninja does not seem to work on windows for me...
I got ninja from here:
git://github.com/martine/ninja.git
branch master
I got cmake from here:
remotes/stage/ninja-generator
I removed the if(UNIX) in the cmake tree and built cmake with n
On 2/15/2012 5:52 PM, Peter Kümmel wrote:
In summary:
- use the CMakeLists.txt from
https://github.com/syntheticpp/ninja/tree/cmake
- on Windows use ninja from
https://github.com/syntheticpp/ninja/tree/token-splitter
and wait and see what happens with official ninja
I can liv
On 16.02.2012 04:51, Bill Hoffman wrote:
On 2/15/2012 5:52 PM, Peter Kümmel wrote:
In summary:
- use the CMakeLists.txt from
https://github.com/syntheticpp/ninja/tree/cmake
- on Windows use ninja from
https://github.com/syntheticpp/ninja/tree/token-splitter
and wait and see
On 2/16/2012 2:57 PM, Peter Kümmel wrote:
They are not interested.
There is another patch in the pipeline but with
this the current generator doesn't work.
Use the official ninja and drop Win atm.
Bummer. I am most interested in windows. Would love to stop using
gmake... Seems like they ar
On 16.02.2012 21:38, Bill Hoffman wrote:
On 2/16/2012 2:57 PM, Peter Kümmel wrote:
They are not interested.
There is another patch in the pipeline but with
this the current generator doesn't work.
Use the official ninja and drop Win atm.
Bummer. I am most interested in windows. Would love
What are we trying to accomplish here?
I have set up 3 of my machines (1 each MacOSX, FreeBSD, and Linux --- like my
housekeeper, I don't do Windows) to submit nightly builds using the Ninja
generator. That will test the impact of changes in the generator.
But it appears that we may also need t
On Thu, Feb 16, 2012 at 5:08 PM, Richard Wackerbarth wrote:
> What are we trying to accomplish here?
>
2 things:
(1) Keep the CMake ninja generator working with the changing state of the
CMake code base (primary)
(2) Understanding what version of ninja works good on all the platforms on
which it
On 2/16/2012 5:19 PM, David Cole wrote:
On Thu, Feb 16, 2012 at 5:08 PM, Richard Wackerbarth mailto:rich...@nfsnet.org>> wrote:
What are we trying to accomplish here?
2 things:
(1) Keep the CMake ninja generator working with the changing state of
the CMake code base (primary)
(2) Understa
I did find out that the ninja generator is not part of the cmake
bootstrap.
Where is the actual cmake repository and branch which contains the ninja
generator
on which we should work?
Peter
--
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/ope
On 17.02.2012 21:27, Peter Kümmel wrote:
I did find out that the ninja generator is not part of the cmake
bootstrap.
Where is the actual cmake repository and branch which contains the ninja
generator
on which we should work?
stage/ninja-generator?
Peter
--
Powered by www.kitware.com
Vi
On 16.02.2012 22:46, Peter Kümmel wrote:
On 16.02.2012 21:38, Bill Hoffman wrote:
On 2/16/2012 2:57 PM, Peter Kümmel wrote:
They are not interested.
There is another patch in the pipeline but with
this the current generator doesn't work.
Use the official ninja and drop Win atm.
Bummer. I a
I've created on stage the new branch 'ninja-generator-win'.
It differs from 'ninja-generator' only by one small commit:
http://cmake.org/gitweb?p=stage/cmake.git;a=commitdiff;h=3bda549dd1dc4a739e7a7f1b23ce98b59986940f
(when someone cherry-pick this commit, please also delete this branch)
I've m
13 matches
Mail list logo
