nefit: now CMake doesn't reimplement undocumented
behavior of Microsoft's MSBuild targets; we just use them directly as a black
box.
Best regards,
James Johnston
From: CMake [mailto:cmake-boun...@cmake.org] On Behalf Of Guillaume Dumont
Sent: Monday, August 31, 2015 16:49
To: Gonzalo
ilto:cmake-boun...@cmake.org] On Behalf Of Hendrik Sattler
Sent: Monday, August 31, 2015 15:49
To: Guillaume Dumont; cmake@cmake.org
Subject: Re: [CMake] Visual Studio - Ninja Generator
Hi,
did you really enable parallel compiling in VS with /MP24 or the like? Note
that using devenv to build uses the
@Hendrik Sattler
I have not experimented with the /MP flag that much, but this won't solve
my problem when the project contains a lot of CUDA files. The /MP flag as
not effect there.
Yes I could indeed create a custom build target and create additional build
trees to build using ninja in there bu
El 31/08/15 a las 11:35, Guillaume Dumont escribió:
Hi all,
Using ninja is especially useful for projects with a lot of CUDA files
which are built sequentially for every target using MSVS.
I would like to contribute but I don't really know where to start and
if such an effort already exists
Hi,
did you really enable parallel compiling in VS with /MP24 or the like? Note
that using devenv to build uses the number from the IDE user settings but using
msbuild needs a command line option.
Else just create a custom target that calls cmake for ninja and afterwards
ninja itself in yet an
Hi all,
I would like to know what kind of effort would it take to generate a Visual
Studio generator that bypasses the normal MSBuild build and uses Ninja
instead. I have been working on different projects which build much faster
with ninja than MSBuild (several orders of magnitude on a machine wi
