l_target) statement that seems
> to
> >> always work?
> >>
> >> Allen
> >>
> >> > Date: Wed, 12 Jan 2011 13:23:52 -0500
> >>
> >> > From: "Marcus D. Hanwell"
> >>
> >> > Subject: Re: [CMake] How
o
>> always work?
>>
>> Allen
>>
>> > Date: Wed, 12 Jan 2011 13:23:52 -0500
>>
>> > From: "Marcus D. Hanwell"
>>
>> > Subject: Re: [CMake] How to have a target depend on an External
>>
>> > Project
>>
: Wed, 12 Jan 2011 13:23:52 -0500
>
> > From: "Marcus D. Hanwell"
>
> > Subject: Re: [CMake] How to have a target depend on an External
>
> > Project
>
> > To: kent williams
>
> > Cc: CMake ML
>
> > Message-ID:
>
> >
While Marcus states what is likely the preferred way, I just added an
ADD_DEPENDENCIES(internal_target external_target) statement that seems to
always work?
Allen
> Date: Wed, 12 Jan 2011 13:23:52 -0500
> From: "Marcus D. Hanwell"
> Subject: Re: [CMake] How to have a
On Wed, Jan 12, 2011 at 12:53 PM, kent williams
wrote:
> For better or worse (mostly better) we are now heavy users of
> ExternalProject. That module works really well to pull in external
> dependencies and get them built.
>
> ExternalProject_add has a DEPENDS keyword that lets you specify
> depe
For better or worse (mostly better) we are now heavy users of
ExternalProject. That module works really well to pull in external
dependencies and get them built.
ExternalProject_add has a DEPENDS keyword that lets you specify
dependencies on other External Projects. But an ExternalProject isn't
