On 03/20/2014 04:48 AM, Brian Lewis wrote:
> On 2014.03.19, at 07:21, Micha Hergarden wrote:
>
> Hi, thanks for answering. Could you please elaborate a little?
>
>> ExternalProject_Add has a DEPENDS option. What you can do is let X
>> depend on Y
> DEPENDS seems to mean that the external project de
On Wednesday, March 19, 2014 10:11 AM, Brian Lewis wrote:
If X brings in Y as an external project, and Y brings in Z as an
external project, is there some way for Y to communicate information
about Z back to X, e.g., some include directory?
My situation is, X doesn't know anything about Z, but n
On 2014.03.19, at 07:21, Micha Hergarden wrote:
Hi, thanks for answering. Could you please elaborate a little?
> ExternalProject_Add has a DEPENDS option. What you can do is let X
> depend on Y
DEPENDS seems to mean that the external project depends on something
else. If I wanted to make X depen
Hi Brian,
ExternalProject_Add has a DEPENDS option. What you can do is let X
depend on Y and use the CMAKE_CACHE_ARGS option to provide the include
path, or use the buildsystem in project X to find the headers itself.
Regards,
Micha
On 03/19/2014 03:11 AM, Brian Lewis wrote:
> If X brings in Y a
If X brings in Y as an external project, and Y brings in Z as an
external project, is there some way for Y to communicate information
about Z back to X, e.g., some include directory?
My situation is, X doesn't know anything about Z, but needs to be able
to find one of Z's headers. I wish I could a
