[Insight-users] Strange Build Config

[Luis Ibanez]

Hi Mike,


1) It is normal that VisualStudio will from time to
    time tell you that the .dsp has been changed.
    The reason is that CMake may be run as part of
    the build process. In particular if it is detected
    that a CMakeLists.txt file has changed since the
    last built.  One way of avoiding this annoying
    situation is to simply run CMake on your project
    before loading  the  .dsw in VisualStudio. Of course
    you only do this when you change anything in your
    CMakeLists.txt.

    In any case, there is nothing particularly bad with
    simply reloading the .dsp.  This only gets annoying
    when you have may .dsp files in the same workspace.


2) We may not have any IOCommon.dll library. This
    is probably ITKCommon.dll or ITKIO.dll.  Note that
    your application must be build in the same compilation
    mode as ITK. You are probably building ITK for Debug
    and your application for Release. You shouldn't attempt
    to mix two compilation modes.  One easy way to get started
    is to build ITK both for Debug and for Release. In that
    way you can switch the compilation mode of your application
    and still find the corresponding ITK libraries.

    (You may want to disable TESTING and EXAMPLES in ITK,
     this will make possible to build in less than 15 minutes).


Regards,


    Luis



-----------------------
Michael Hawrylycz wrote:

>  
> Hi
> 
> I have gotten into a peculiar build configuration with Visual Studio 6.0
> where I have 
> a correct out of source build of ITK in a directory called
> C:\ITK\ITKBin.  Then my application is 
> in a directory called C:\ITK\ITKTest.  When I run Cmake it wants to know
> the ITK_DIR which it thinks
> is defaulting C:\ITK\ITKBin naturally.  My appplication builds except
> that it says that the .dsp
> has changed outside of the project and must be reloaded. Further, at
> after the successful build
> at run time the executable says it can't find IOCommon.dll.
> IOCommon.dll in fact lives in C:\ITK\ITKBin\bin\Debug
> for my build.
> 
>  How might I have gotten into this state?
> 
> Thanks,
> 
> Mike
> 
> _______________________________________________
> Insight-users mailing list
> Insight-users at itk.org
> http://www.itk.org/mailman/listinfo/insight-users
>