We already have nightly builds set up, so this would certainly be a possibility,
though I would have to think through how to make it work when we didn't have a
connection to our build server. I would still prefer, however, to have this
work locally. You mention that you set this up 5 years or so
* Wiser, Tyson twi...@logostech.net (Tue, May 29, 2012 at 06:26:29AM -0700)
We already have nightly builds set up, so this would certainly be a
possibility,
though I would have to think through how to make it work when we didn't have a
connection to our build server. I would still prefer,
But ExternalProject still does a checkout, configure and build step. (at least
if I read the docs correctly)
our goal was to minimize the amount of stuff you needed to build,
specifically,
if you were only working on 2 libs that were needed by 1 app, you could
checkout only those 2 libs.
Tyson,
Thanks for the replies. The way that I was thinking of using ExternalProject
would not require a checking out every library, [ 8 ]
Using your example, if I wanted to work only on the one app that needed two
libs,
I could check out and build the app. Due to ExternalProject, the
What we did here, faced with the same issue,
is have an automated, ightly build that builds everything,
and then have partial checkouts.
The cmake link dependencies then first check if there is local source
and local libs, and if so uses those, otherwise it takes the nightly
build libs.
A bit of
We currently have a fair number of libraries, executables and external
dependencies with fairly complicated dependencies. As a simplified example,
consider the following diagram where dependencies flow from top to bottom (i.e.
higher depends on lower).
exe1 exe2
| | \
On Wed, May 23, 2012 at 9:52 AM, Wiser, Tyson twi...@logostech.net wrote:
We don't modify external dependencies, but we do need to check them out and
build them before building a library or executable that depends on them.
Sometimes a developer will be working in a single library or executable.
We don't modify external dependencies, but we do need to check them
out and build them before building a library or executable that depends on
them.
Sometimes a developer will be working in a single library or executable.
Sometimes he will be working in multiple libraries and/or
