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
Hi all,
Sorry to "hijack" this message, but I am running into the same problem. As
part of my build I create zip files, and currently have this coupled to a
normal library target (add_library). This works ok, but for some new
features I need to create a zip file with a collection of libraries, so
