Thanks guys.
I ended up with a different (hack) way:
To recap, my issue was that my patch would be applied twice when
building with multi-configuration generators.
Since I am always building the external project with a release
configuration, the following worked fine to disable the
multi-configu
Re-downloading it would be fine. How can I make sure a different
directory gets used? Since I'm using a multi-configuration IDE, I
can't think of any variables to use for PREFIX or such.
-Johan
On Wed, Mar 16, 2011 at 5:37 PM, David Cole wrote:
> It would be nice (as a future feature addition)
On 16/03/2011 17.37, David Cole wrote:
It would be nice (as a future feature addition) to be able to support
sharing the download/update/patch/source_dir aspects of an
ExternalProject target among multiple configurations and avoid the
multiple runs of these things that are exactly the same indepe
It would be nice (as a future feature addition) to be able to support
sharing the download/update/patch/source_dir aspects of an
ExternalProject target among multiple configurations and avoid the
multiple runs of these things that are exactly the same independent of
the config.
Until that dream be
Hi everyone,
I'm using an SVN repository and a PATCH command. It seems to work
fine, but when I'm selecting a different build configuration, all
steps will be executed again (as expected), but it results in my patch
being applied twice.
Any ideas how to work around this?
My externalProject comm
