Haaaaa, ok I see I was thinking of this the wrong way...<br><br>Thanks a lot :-)<br><br>--<br>Alex<br><br><div class="gmail_quote">2009/3/25 Brad King <span dir="ltr"><<a href="mailto:brad.king@kitware.com">brad.king@kitware.com</a>></span><br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div class="im">Andreas Pakulat wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
The easiest way to achieve what you want (having targets of<br>
projectB+projectC available to projectA) is by having the<br>
FindProjectB.cmake file simply do a find_package(ProjectC REQUIRED) call<br>
and then make sure that FindProjectC.cmake (or the ConfigProjectC.cmake)<br>
load the file containing the export-information from ProjectC. So instead<br>
of exporting imported target let the original exporting from ProjectC run<br>
automatically when finding ProjectB.<br>
</blockquote>
<br></div>
This is the approach intended. If ProjectB imports ProjectC from somewhere<br>
then ProjectA can import ProjectC from the same place. It is up to ProjectB<br>
to tell ProjectA which ProjectC it used.<br><font color="#888888">
<br>
-Brad</font><div><div></div><div class="h5"><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>