<div dir="ltr">Hi Radovan, <div><br></div><div style>This is possible. You could look at the approach we consider in CTK.</div><div style>See <a href="https://github.com/commontk/CTK/compare/00694c9f8a0da6ee28fb079902e6a8c3ec428058...891aa5443b110cc7e6aa0ec1339aad4b2c83ef9d">https://github.com/commontk/CTK/compare/00694c9f8a0da6ee28fb079902e6a8c3ec428058...891aa5443b110cc7e6aa0ec1339aad4b2c83ef9d</a></div>
<div style><br></div><div style>Hth</div><div style>Jc</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Fri, Apr 5, 2013 at 12:03 PM, radovan bast <span dir="ltr"><<a href="mailto:radovan.bast@irsamc.ups-tlse.fr" target="_blank">radovan.bast@irsamc.ups-tlse.fr</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">dear CMake developers and users,<br>
<br>
first of all, a big thanks for the CMake developers<br>
for a great product! we like CMake a lot.<br>
<br>
we are extensively using CMake external project support<br>
in combination with Git submodules in a number of larger<br>
projects and that works nicely.<br>
<br>
my question is: could i do something similar with CMake<br>
modules? is it possible to start with a minimal core<br>
CMakeLists.txt which would fetch other CMake modules from an<br>
external public (Git) repository<br>
and use them to configure the project?<br>
<br>
the motivation for this is that we have several projects<br>
with rather complex CMake infrastructures. the projects<br>
are independent, live on different repositories, but the<br>
CMake infrastructures are to a large extent overlapping.<br>
currently we synchronize the CMake code between these projects<br>
manually but this is not great and there is the risk that<br>
the codes will diverge, that wheels will be reinvented,<br>
and that improvements are not communicated between the projects.<br>
this could be avoided if the CMake code was not explicitly<br>
present but fetched from a repository which would also<br>
enforce (or encourage) communicating all improvements<br>
to the same place. everything that is generic and not project<br>
specific would go into that external repo, only project specific<br>
things would be kept in the minimal core CMakeLists.txt.<br>
<br>
i will appreciate any pointers and suggestions<br>
on how i could implement such a scheme.<br>
<br>
thanks and best regards,<br>
radovan<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/<u></u>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/<u></u>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/<u></u>listinfo/cmake</a><br>
</blockquote></div><br><br clear="all"><div><br></div>-- <br>+1 919 869 8849<br>
</div>