[Insight-users] A bug possibly related to itkGDCMImageIO

[Thomas Lambertz]

Hi Li,

you should never have pathes to different versions of ITK.

I build different versions the following way:
Solution Explorer->Project Properties->Configuration 
Properties->Linker->General->Additional Library Directories

"C:\VTKBIN\\bin\$(Platform)\$(ConfigurationName)";"C:\ITKBIN\bin\$(Platform)\$(ConfigurationName)"

$(Platform) is only needed when building for different Architectures.

HTH,
Tom


An, Li (NIH/NINDS) [E] wrote:

> Hi Tom,
>
> Thanks very much for your email. It helped me solved the problem. The
> cause of this problem is with the environment variable "Path". In the
> path, the ITK debug library directory is listed in front of the release
> directory. As a result, the ITK debug library is found first and is
> linked to the release version of my program. 
>
> I noticed that the ITK dll files have the same names for debug and
> release versions. I often need to switch between debug and release
> builds. Is there an easy way to avoid setting the path every time I
> switch between debug and release run?
>
> Thanks,
> Li
>
>
> -----Original Message-----
> From: Thomas Lambertz [mailto:thomas at hexerei-software.de] 
> Sent: Friday, June 02, 2006 10:06 AM
> To: An, Li (NIH/NINDS) [E]
> Cc: insight-users at itk.org
> Subject: Re: [Insight-users] A bug possibly related to itkGDCMImageIO
>
> Hi Li,
>
> i dont think its a bug in GDCMImageIO. I use both Visual Studio and 
> GDCMImageIO under Win32 and x64 and they work fine (for me).
>
> You may have a look wether you mixed release and debug code in your 
> project. In a release-version there shouldnt be a msvcr80d.dll - instead
>
> msvcr80.dll be used. Have a look under project properties -> 
> Configuration Properties -> C/C++ -> Code Generation ->Runtime Library. 
> Multi-threadded DLL (/MD) should be used instead of Multi-threadded 
> Debug DLL (/MDd).
>
> HTH,
> Tom
>
> An, Li (NIH/NINDS) [E] wrote:
>   
>> I'm using Visual Studio 2005 to build a 3D image registration program.
>>     
>
>   
>> The registration program works well if I build the project using the 
>> ITK debug library. However, the program crashes in run-time if it is 
>> built using the ITK release library. The program crashes when it is 
>> reading 2D DICOM image slices and combining them into 3D ITK images. 
>> The error message says that the crashed module is msvcr80d.dll. Has 
>> anyone reported a similar problem?
>>
>> Thanks,
>>
>> Li