[cmake-developers] Ninja help

[David Cole]

2012/2/15 Nicolas Desprès <nicolas.despres at gmail.com>

>
>
> 2012/2/15 Richard Wackerbarth <richard at nfsnet.org>
>
>> Regretfully, testing the Ninja Generator for the nightly CMake dashboard
>> is not as simple as would be desired.
>>
>> First, you have to bootstrap using a recent version of CMake (I am using
>> my default "Unix Makefile" build for the nightly dashboard)
>>
>
> Yes, you have to build CMake twice. Once with the Unix Makefiles generator
> and once with the Ninja generator. I don't think it is such a big deal. I
> have done during all the time I spent developing the beginning of the Ninja
> Generator.
>
>
>> And then, on MacOSX 10.6, it fails on some of the tests .... :(
>>
>
> It is on my todo list to try to fix that bug on MacOSX 10.7, as soon as I
> find the time... Can give a deadline unfortunately :(
>
>
>>
>> I will now try to add it to one of my FreeBSD builds.
>>
>
> That will give interesting feedback. Thx.
>
> -Nico
>
>
>>
>>
>> >
>> >
>> > 2012/2/15 Bill Hoffman <bill.hoffman at kitware.com>
>> > On 2/15/2012 11:20 AM, Nicolas Desprès wrote:
>> >
>> > For compiling and testing you can find all the information in the
>> > HACKING file.
>> >
>> > Well, this is ugly:
>> >
>> > ------HACKING--------
>> > Windows development on Windows:
>> > - install mingw, msys, and python
>> > - in the mingw shell, put Python in your path, and: python bootstrap.py
>> > - to reconfigure, run 'python configure.py'
>> > - remember to strip the resulting executable if size matters to you
>> > - you'll need to rename ninja.exe into my-ninja.exe during development,
>> >  otherwise ninja won't be able to overwrite itself when building
>> > ------HACKING--------
>> >
>> > It would be really nice if ninja had a CMake build system with it for
>> windows development.  It basically looks like a bunch of c++ files. Having
>> to have python to build ninja is a pain for setting up a visual studio
>> ninja dashboard.
>> >
>> > I was arguing in favor of this approach on the mailing list but some
>> people came up with patches for the Python bootstrap script quickly and
>> they have been applied. Ninja likes to be standalone as much as possible
>> even if it requires Python and for development the Google Test and re2c.
>> Also I think, since the Ninja generator was not available in CMake it was
>> kind of a chicken and egg problem. Several forks on github already provides
>> a CMakeLists.txt for Ninja. I think if some people are willing to maintain
>> them (this include myself but my spare time is not that "responsive"
>> unfortunately :-( ) and if the merge of the ninja generator in cmake is
>> coming, Evan will accept a parallel build-system without any objections.
>> >
>> > --
>> > Nicolas Desprès
>> >
>> > --
>> >
>> > Powered by www.kitware.com
>> >
>> > Visit other Kitware open-source projects at
>> http://www.kitware.com/opensource/opensource.html
>> >
>> > Please keep messages on-topic and check the CMake FAQ at:
>> http://www.cmake.org/Wiki/CMake_FAQ
>> >
>> > Follow this link to subscribe/unsubscribe:
>> > http://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers
>>
>>
>
>
> --
> Nicolas Desprès
>
>

It's ok that it fails some of the tests. That's the whole point, actually:
bring the state of the thing into the public light of the CMake dashboard
so that we can work on the problem areas before we push it into CMake
'master' and then into a release.

I don't expect the dashboard submissions to be perfect at first.

I do expect them to be submitted every day so that people can fix the
problems. Then, after all is fixed up, people who want to work on CMake can
be assured that their changes do not break the Ninja generator. (Or at
least, that somebody will notice if they do...)


Thx,
David
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/cmake-developers/attachments/20120215/e009a9f9/attachment.html>