[ITK Community] Integrating ITK into our own SDK
Michael Jackson
mike.jackson at bluequartz.net
Wed Mar 12 13:54:29 EDT 2014
So what you are suggesting is that when I build ITK I would build ITK In Debug and then install to (for example) C:/ITK/Debug and when building in Release install to C:/ITK/Release?
Would that mess up the actual use of
find_package(ITK) in my own project? Would find_package(ITK) actually be able to distinguish between the Debug and Release builds?
Thanks
Mike J.
On Mar 12, 2014, at 1:21 PM, Matt McCormick <matt.mccormick at kitware.com> wrote:
> Hi Mike,
>
> Does setting CMAKE_INSTALL_PREFIX to "Release" or "Debug" work for your situation?
>
> Thanks,
> Matt
>
>
> On Wed, Mar 12, 2014 at 12:57 PM, Michael Jackson <mike.jackson at bluequartz.net> wrote:
> Hello ITK Community,
> In my current project (dream3d.bluequartz.net) we would like to be able to incorporate ITK as our image processing library of choice. To that end we usually provide precompiled binaries of all our dependent libraries (HDF5, Qt, Qwt, Eigen, TBB, Boost) for our Windows users so that they do not have to compile all the dependencies themselves**. For every library there are Debug and Release versions of the libraries where each library has some nomenclature in the name of the library file that denotes Debug or Release.
> In compiling ITK there does not seem to be any type of differentiation in the naming so when I do a Debug build and install then do a Release build and install the second install simply over writes the first install. Even for normal development it seems like I have to go back and compile the Debug and "install" that when I am debugging my own code but when I want to try my code in release I have to go back and Compile/Install the Release version of ITK, then compile/install my own project. Clearly I am missing something about how to do this sort of thing with ITK so I have some questions about how to proceed.
>
> 1: Has anyone else tried to include a prebuilt ITK into their own "SDK" and how did you go about doing that?
> 2: How do I ensure that when I compile a Debug build I am getting a Debug version of ITK?
> 3: How can I have an installation of BOTH a Debug build of ITK and a Release build of ITK?
>
>
>
> **: On windows it is very easy to hose yourself by mix-n-matching other peoples Precompiled Binaries so that you end up with multiple versions of the C/C++ runtime libraries on windows which causes all sorts of Headaches. This is why we precompile ALL of our dependent libraries so we ensure we do not run into this problem, at least on Windows.
>
> Thanks for any help/thoughts/ideas/recommendations
> ___________________________________________________________
> Mike Jackson BlueQuartz Software
> Help: dream3d at bluequartz.net
> Web|Download http://dream3d.bluequartz.net
>
> _______________________________________________
> Community mailing list
> Community at itk.org
> http://public.kitware.com/cgi-bin/mailman/listinfo/community
>
More information about the Community
mailing list