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
e, so that Ninja doesn't oversubscribe.
I'm not aware of a way to make Ninja do that though. You can use pools to
restrict to one link at a time, but moderate oversubscription will still happen
with the concurrent cl.exe instances.)
Best regards,
James Johnston
From: CMake [ma
> -Original Message-
> From: rcdai...@gmail.com [mailto:rcdai...@gmail.com] On Behalf Of Robert
> Dailey
> Sent: Sunday, August 23, 2015 02:43
> To: James Johnston
> Cc: CMake
> Subject: Re: [CMake] How to depend on external cmake projects?
>
> On Mon, Aug
project that does nothing but call ExternalProject_Add;
this is called a superbuild. Your own CMake projects will be
ExternalProjects to this high-level project and the superbuild would pass
the location to your project via -D_DIR= so that
find_package can locate the Config file.
Best regard
you can use
$/../ref.vc(x)proj to get to the project file. If the
project reference is to another C# project you can use the undocumented
EXTERNAL_MSPROJECT target property. If it's a non-project reference then
you have to provide a which can be done with $ for
C++ references and a cust
my VC++ targets?
It would be awesome if CMake could support multi-platform - it could really
simplify things for me (as now I am working on a superbuild that iterates
through all the above platforms) - but I'd rather see it in a form that is
baked into the core of CMake, rather than somethin
re would be (a) install
Python for Windows, (b) go to a Visual C++ command prompt to set up VC++
environment, (c) call Ninja bootstrapper script.
2. Run CMake from a Visual C++ command prompt when you want to use the
Ninja generator because Ninja generator will just look for whatever "cl.ex
rator because
it's faster than Visual Studio), (3) Visual Studio generator would emit a
solution containing generated VC++/VC# projects. Anything else feels like a
bit of a hack to me. But #1 thru #3 sounds like a lot of work though...
Also, C# doesn't compile to object files - does
it's worth, at this time, I think this issue is limited to the
linker and not to the single-unit compilation of a CPP file to OBJ file. I
ran Process Monitor for a few seconds while VTK was compiling, and it seems
that the only file writes to the build tree were either legitimate wri
