On Mon, 2014-02-17 at 08:34 -0500, Paul Smith wrote:
> On Mon, 2014-02-17 at 10:20 +0100, Hendrk Sattler wrote:
> > Visual Studio 10 totally relies on the custom build tool to protect
> > itself when run in parallel. It will run the generator as many times
> > as the bar.cpp is mentioned in diffe
visual studio supports a verbosity setting on the command line...
/v:[qmnd,diag]
Specifies the amount of information to display in the build log. Each
logger displays events based on the verbosity level that you set for
that logger.
You can specify the following verbosity levels: q[uiet], m[inima
On Mon, 2014-02-17 at 10:20 +0100, Hendrk Sattler wrote:
> Visual Studio 10 totally relies on the custom build tool to protect
> itself when run in parallel. It will run the generator as many times
> as the bar.cpp is mentioned in different targets, even in parallel if
> that is enabled.
Yes, th
Thanks Hendrk. It's good to know I'm not crazy or overlooking something
simple, even if the answer is not what I wanted.
I did some other experimentation last night and I'll followup with some
results, which may be interesting.
Can anyone tell me how to get the Visual Studio output to show compl
Am 2014-02-17 10:20, schrieb Hendrk Sattler:
Visual Studio 10 totally relies on the custom build tool to protect
itself when run in parallel.
It will run the generator as many times as the bar.cpp is mentioned in
different targets, even in parallel if that is enabled.
And that's what you see.
A
Am 2014-02-17 07:36, schrieb Paul Smith:
On Mon, 2014-02-17 at 00:20 -0500, Paul Smith wrote:
On Sun, 2014-02-16 at 22:38 -0500, David Cole wrote:
> > How can I structure my cmake file to avoid
> > this double build?
>
> Put the custom command in a custom target, and make the libraries using
> t
On Mon, 2014-02-17 at 00:20 -0500, Paul Smith wrote:
> On Sun, 2014-02-16 at 22:38 -0500, David Cole wrote:
> > > How can I structure my cmake file to avoid
> > > this double build?
> >
> > Put the custom command in a custom target, and make the libraries using
> > the generated file depend on th
On Sun, 2014-02-16 at 22:38 -0500, David Cole wrote:
> > How can I structure my cmake file to avoid
> > this double build?
>
>
> Put the custom command in a custom target, and make the libraries using
> the generated file depend on the custom target.
>
> That works, even for parallel builds.
>
How can I structure my cmake file to avoid
this double build?
Put the custom command in a custom target, and make the libraries using
the generated file depend on the custom target.
That works, even for parallel builds.
Google around for examples and similar advice. You'll end up using
add
On Sun, 2014-02-16 at 21:35 -0500, Paul Smith wrote:
> I'm using CMake 2.8.12.1 on Linux, MacOS, and Windows. On Windows I'm
> using MSVC 2010 and the Visual Studio generator, but I have only
> remote access so I'm invoking my builds using devenv (not running
> Visual Studio).
Here's a simplified
I'm using CMake 2.8.12.1 on Linux, MacOS, and Windows. On Windows I'm
using MSVC 2010 and the Visual Studio generator, but I have only remote
access so I'm invoking my builds using devenv (not running Visual
Studio).
I'm deeply involved in some messy hackery related to building the same
code as a
11 matches
Mail list logo
