So add_dependencies should work for you.<div><br></div><div>Let us know if it's not working like you think it should...</div><div><br><br><div class="gmail_quote">On Wed, Jan 12, 2011 at 3:48 PM, kent williams <span dir="ltr"><<a href="mailto:nkwmailinglists@gmail.com">nkwmailinglists@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">Ironically the reason I want to make a target depend on an external<br>
project is that our top level project is already built as an<br>
ExternalProject for all the reasons that have been mentioned.<br>
<br>
I need a custom target to depend on THAT external project, just in the<br>
sense that I want it to be built only after my MAIN project is built.<br>
There's no chicken V egg problems -- my custom target is independent<br>
from that target at configure time. It just needs to happen after that<br>
ExternalProject is built successfully.<br>
<div><div></div><div class="h5"><br>
<br>
On Wed, Jan 12, 2011 at 1:12 PM, David Cole <<a href="mailto:david.cole@kitware.com">david.cole@kitware.com</a>> wrote:<br>
> add_dependencies does work to make sure that ExternalProject targets build<br>
> before internal targets, if you need that.<br>
> But, like Marcus said, you probably need the ExternalProject to be<br>
> configured and built before your own calls to find_package... so if you have<br>
> that chicken and egg problem, you should also build your project as an<br>
> ExternalProject.<br>
> Almost all of the projects I know of that are using ExternalProject are<br>
> producing a so-called "SuperBuild" of themselves, wherein all the targets of<br>
> the SuperBuild are ExternalProject_Add calls, and the last one is the<br>
> "project of interest."<br>
><br>
> HTH,<br>
> David<br>
><br>
> On Wed, Jan 12, 2011 at 2:09 PM, Allen D Byrne <<a href="mailto:byrn@hdfgroup.org">byrn@hdfgroup.org</a>> wrote:<br>
>><br>
>> While Marcus states what is likely the preferred way, I just added an<br>
>> ADD_DEPENDENCIES(internal_target external_target) statement that seems to<br>
>> always work?<br>
>><br>
>> Allen<br>
>><br>
>> > Date: Wed, 12 Jan 2011 13:23:52 -0500<br>
>><br>
>> > From: "Marcus D. Hanwell" <<a href="mailto:marcus.hanwell@kitware.com">marcus.hanwell@kitware.com</a>><br>
>><br>
>> > Subject: Re: [CMake] How to have a target depend on an External<br>
>><br>
>> > Project<br>
>><br>
>> > To: kent williams <<a href="mailto:nkwmailinglists@gmail.com">nkwmailinglists@gmail.com</a>><br>
>><br>
>> > Cc: CMake ML <<a href="mailto:cmake@cmake.org">cmake@cmake.org</a>><br>
>><br>
>> > Message-ID:<br>
>><br>
>> > <AANLkTinDoc6guEnK7rxQ=<a href="mailto:0yy%2BsXacOium52iX8ZiHmcz@mail.gmail.com">0yy+sXacOium52iX8ZiHmcz@mail.gmail.com</a>><br>
>><br>
>> > Content-Type: text/plain; charset=ISO-8859-1<br>
>><br>
>> ><br>
>><br>
>> > On Wed, Jan 12, 2011 at 12:53 PM, kent williams<br>
>><br>
>> > <<a href="mailto:nkwmailinglists@gmail.com">nkwmailinglists@gmail.com</a>> wrote:<br>
>><br>
>> > > For better or worse (mostly better) we are now heavy users of<br>
>><br>
>> > > ExternalProject. ?That module works really well to pull in external<br>
>><br>
>> > > dependencies and get them built.<br>
>><br>
>> > ><br>
>><br>
>> > > ExternalProject_add has a DEPENDS keyword that lets you specify<br>
>><br>
>> > > dependencies on other External Projects. ?But an ExternalProject isn't<br>
>><br>
>> > > an actual CMake target, so I can't figure out how to make a regular<br>
>><br>
>> > > CMake target depend on an External Project.<br>
>><br>
>> > ><br>
>><br>
>> > > Suggestions?<br>
>><br>
>> ><br>
>><br>
>> > Don't mix external projects and real targets. An external project<br>
>><br>
>> > dependency is different to a target dependency. When expressing<br>
>><br>
>> > external project dependencies you are stating that this external<br>
>><br>
>> > project needs these others to be built before it is even configured.<br>
>><br>
>> ><br>
>><br>
>> > With regular targets there is an assumption that the dependency is<br>
>><br>
>> > part of the current build, and so CMake knows everything about it, or<br>
>><br>
>> > it was already built. If you have Qt in an external project, and a Qt<br>
>><br>
>> > based application depending on it, the find_package(Qt4) will fail<br>
>><br>
>> > during initial configure, as there is no Qt built/installed.<br>
>><br>
>> ><br>
>><br>
>> > Instead you would normally have your own project as an external<br>
>><br>
>> > project that depends on the others it requires to build. That way,<br>
>><br>
>> > when your external project is configured the others will have been<br>
>><br>
>> > built and therefore could be found.<br>
>><br>
>> ><br>
>><br>
>> > I hope that makes the mechanism a little clearer. You could take a<br>
>><br>
>> > look at the Titan project as one example where we have many external<br>
>><br>
>> > projects that we build, and the Libraries/Applications external<br>
>><br>
>> > projects that depend upon them and use them.<br>
>><br>
>> ><br>
>><br>
>> > Marcus<br>
>><br>
>> ><br>
>><br>
>> _______________________________________________<br>
>> Powered by <a href="http://www.kitware.com" target="_blank">www.kitware.com</a><br>
>><br>
>> Visit other Kitware open-source projects at<br>
>> <a href="http://www.kitware.com/opensource/opensource.html" target="_blank">http://www.kitware.com/opensource/opensource.html</a><br>
>><br>
>> Please keep messages on-topic and check the CMake FAQ at:<br>
>> <a href="http://www.cmake.org/Wiki/CMake_FAQ" target="_blank">http://www.cmake.org/Wiki/CMake_FAQ</a><br>
>><br>
>> Follow this link to subscribe/unsubscribe:<br>
>> <a href="http://www.cmake.org/mailman/listinfo/cmake" target="_blank">http://www.cmake.org/mailman/listinfo/cmake</a><br>
><br>
><br>
> _______________________________________________<br>
> Powered by <a href="http://www.kitware.com" target="_blank">www.kitware.com</a><br>
><br>
> Visit other Kitware open-source projects at<br>
> <a href="http://www.kitware.com/opensource/opensource.html" target="_blank">http://www.kitware.com/opensource/opensource.html</a><br>
><br>
> Please keep messages on-topic and check the CMake FAQ at:<br>
> <a href="http://www.cmake.org/Wiki/CMake_FAQ" target="_blank">http://www.cmake.org/Wiki/CMake_FAQ</a><br>
><br>
> Follow this link to subscribe/unsubscribe:<br>
> <a href="http://www.cmake.org/mailman/listinfo/cmake" target="_blank">http://www.cmake.org/mailman/listinfo/cmake</a><br>
><br>
_______________________________________________<br>
Powered by <a href="http://www.kitware.com" target="_blank">www.kitware.com</a><br>
<br>
Visit other Kitware open-source projects at <a href="http://www.kitware.com/opensource/opensource.html" target="_blank">http://www.kitware.com/opensource/opensource.html</a><br>
<br>
Please keep messages on-topic and check the CMake FAQ at: <a href="http://www.cmake.org/Wiki/CMake_FAQ" target="_blank">http://www.cmake.org/Wiki/CMake_FAQ</a><br>
<br>
Follow this link to subscribe/unsubscribe:<br>
<a href="http://www.cmake.org/mailman/listinfo/cmake" target="_blank">http://www.cmake.org/mailman/listinfo/cmake</a><br>
</div></div></blockquote></div><br></div>