<div dir="ltr">I just re-read your question. Superbuild won't help.<br><br></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Tue, May 28, 2013 at 11:29 AM, Bill Lorensen <span dir="ltr"><<a href="mailto:bill.lorensen@gmail.com" target="_blank">bill.lorensen@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">You could use cmake's superbuild facility to build both itk3 and itk4 in a superbuild tree.<br> <br>
</div><div class="gmail_extra"><div><div class="h5"><br><br><div class="gmail_quote">On Tue, May 28, 2013 at 11:02 AM, John Drescher <span dir="ltr"><<a href="mailto:drescherjm@gmail.com" target="_blank">drescherjm@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div>On Tue, May 28, 2013 at 10:16 AM, Zamir Khan <<a href="mailto:zamir.khan@gmail.com" target="_blank">zamir.khan@gmail.com</a>> wrote:<br>
> We have a project where multiple modules rely on ITK. Most modules have been<br>
> upgraded to ITK 4.31, but one still relies on ITK 3.20 and it would take a<br>
> significant effort to upgrade it. In the meantime, is there a way for us to<br>
> keep these modules under a single top-level CMake and have them use their<br>
> respective versions of ITK?<br>
><br>
> We thought we could just try to overwrite the ITK_DIR variable in the<br>
> appropriate place, but our first naive implementation of this did not work.<br>
><br>
> Just wondering if someone has done this and whether it is possible (before<br>
> we dive deeper).<br>
><br>
<br>
</div>On windows I have several completely separate build trees with their<br>
own environment. This way I can build for different compiler versions,<br>
32/64 bit and different versions of libraries like this. Inside the<br>
root of each build tree there is a link to the appropriate Visual<br>
Studio command prompt that has its default folder set to the build<br>
tree root. Also in the root there is a batch file that sets quite a<br>
few _DIR environment variables to help cmake find the correct compiled<br>
libraries. This has worked well for the 5 or so years that I have done<br>
it this way. I do not use INSTALL targets so none of the binaries end<br>
up in Program Files.<br>
<span><font color="#888888"><br>
John<br>
</font></span><div><div>--<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><br clear="all"><br></div></div><span class="HOEnZb"><font color="#888888">-- <br>Unpaid intern in BillsBasement at noware dot com<br>
</font></span></div>
</blockquote></div><br><br clear="all"><br>-- <br>Unpaid intern in BillsBasement at noware dot com<br>
</div>