On Fri, Mar 9, 2012 at 3:24 AM, Peter Collingbourne pe...@pcc.me.uk wrote:
On Tue, Mar 06, 2012 at 03:56:24PM -0500, Bill Hoffman wrote:
On 3/6/2012 1:29 PM, Peter Collingbourne wrote:
We can certainly do that, but the ninja binary would need to be
switched as soon as we get around to using
The following issue has been SUBMITTED.
==
http://www.cmake.org/Bug/view.php?id=13032
==
Reported By:Zahary Karadjov
Assigned To:
The following issue has been SUBMITTED.
==
http://public.kitware.com/Bug/view.php?id=13033
==
Reported By:ngladitz
Assigned To:
On 09.03.2012 10:40, Nicolas Desprès wrote:
On Fri, Mar 9, 2012 at 3:24 AM, Peter Collingbournepe...@pcc.me.uk wrote:
On Tue, Mar 06, 2012 at 03:56:24PM -0500, Bill Hoffman wrote:
On 3/6/2012 1:29 PM, Peter Collingbourne wrote:
We can certainly do that, but the ninja binary would need to be
On 09.03.2012 03:34, Peter Collingbourne wrote:
On Thu, Mar 08, 2012 at 05:44:09PM -0500, Bill Hoffman wrote:
Thoughts?
Hi Bill,
I thought about this for a while and I decided that this probably
isn't a good idea for a few reasons:
1) It is inaccurate. The Ninja generator uses a
I am seeing that ninja always wants to relink the executables for me
every time it is run. The output is this:
$ ninja
[1/9] Linking C static library
Utilities\cmlibarchive\libarchive\cmlibarchive.lib
[2/9] Linking CXX executable bin\cmake.exe
[3/9] Linking CXX executable bin\cmw9xcom.exe
