We have a project where multiple modules rely on ITK. Most modules have been
upgraded to ITK 4.31, but one still relies on ITK 3.20 and it would take a
significant effort to upgrade it. In the meantime, is there a way for us to
keep these modules under a single top-level CMake and have them use
On 5/28/2013 10:16 AM, Zamir Khan wrote:
We have a project where multiple modules rely on ITK. Most modules have been
upgraded to ITK 4.31, but one still relies on ITK 3.20 and it would take a
significant effort to upgrade it. In the meantime, is there a way for us to
keep these modules under a
On Tue, May 28, 2013 at 10:16 AM, Zamir Khan zamir.k...@gmail.com wrote:
We have a project where multiple modules rely on ITK. Most modules have been
upgraded to ITK 4.31, but one still relies on ITK 3.20 and it would take a
significant effort to upgrade it. In the meantime, is there a way for
You could use cmake's superbuild facility to build both itk3 and itk4 in a
superbuild tree.
On Tue, May 28, 2013 at 11:02 AM, John Drescher dresche...@gmail.comwrote:
On Tue, May 28, 2013 at 10:16 AM, Zamir Khan zamir.k...@gmail.com wrote:
We have a project where multiple modules rely on
I should probably clarify the situation (I'm not sure I provided enough
info up front). The larger dependencies like ITK are pre-built (I guess one
would assume this; we don't rebuild ITK or VTK with every build of our
project). So I thought it would be a simple problem of overwrite and then
On 05/28/2013 11:38 AM, Zamir Khan wrote:
I should probably clarify the situation (I'm not sure I provided enough info
up front). The larger dependencies like ITK are pre-built (I guess one would
assume this; we don't rebuild ITK or VTK with every build of our project). So
I thought it
