[CMake] Triggering individual steps of externalproject_add add cmake time

Michael Hertling mhertling at online.de
Mon May 2 20:37:23 EDT 2011


On 04/29/2011 11:52 AM, Jan Wurster wrote:
>  Hi David,
> 
>  thanks for your help and suggestions! 
> 
>> From: David Cole [mailto:david.cole at kitware.com] 
>> Sent: Donnerstag, 28. April 2011 19:57
>> Subject: Re: [CMake] Triggering individual steps of
> externalproject_add add cmake time
>>
>> I would strongly encourage you to allow the download to occur at build
> time using 
>> ExternalProject_Add. There's no need to make the configure step of
> CMake wait for a 
>> download.
> 
>  The point only was to solve the .. ahem .. hen and egg problem I'm
> encountering at the first ever configure run. Configure of the project
> itself needs a certain structure of 3rd party stuff to be available -
> else it fails for this system, thus never creating a valid build
> structure in the first place.

This seems to be a problem of the same kind as in [1], i.e. third-party
stuff to be handled/installed/downloaded/<your-requirement-here> before
the actual project is configured, so perhaps the super-build approach
might suit your needs, too.

Regards,

Michael

[1] http://www.mail-archive.com/cmake@cmake.org/msg36016.html

>  I definitely agree the configure step should be kept as minimal in its
> timewise requirements as possible, so once the general structure is
> present, subsequent calls to cmake would never have retriggered the
> download at configure time ;) 
> 
>  Your suggestion actually is what I've implemented since and it works
> fine. Initially, the download occurs, after that the build process will
> keep data up to date. Thanks and best regards,
> Jan


More information about the CMake mailing list