[Dcmlib] Probably a stupid mistake of mine

[Jean-Pierre Roux]

Mathieu Malaterre wrote:

->Mathieu,
Eduardo has still a Visual Studio 6 on a PC.
We are gonna try to find what's going wrong with gdcm1.3 vs VS6

-> Andreas :
You're right : the current cvs version adds the JPEGE/J2K writting, + 
fixes some bugs while write uncompressed dicom files

Jean-Pierre Roux

> Hi Andreas,
>
>   Thanks for the feedback. Unfortunately if you ever have to use VS6,
> the only reasonable way to track down the issue is to go back in time.
> Since gdcm 1.2 *is* working with VS6, the bug has been introduce on
> the gdcm 1.3 branch. According to the dashboard it has been present
> since at least 12 March 2007:
>
> http://public.kitware.com/GDCM/Testing/Dashboard/20070312-0100-Nightly/Dashboard.html
>
>   I'll see if I can get something.
>
> BFN,
> -Mathieu
>
>
> On 9/13/07, Andreas Wimmer <Andreas.Wimmer at gmx.ch> wrote:
>   
>> Dear Mathieu,
>>
>> after lot of work over the last days I finally had the time to
>> compile gdcm 1.3.1 under Visual Studio 2005. A quick test using
>> some DICOM files which previously were reported to be unreadable
>> suggests that the libary works fine. Thus it seems the problems I
>> had with the command line tools generated by Visual C++ 6 are
>> related to the compiler.
>> I'll try the new 1.3.2 release under Visual C++ 6 (although I
>> believe mostly jpeg-related issues were fixed) and post the
>> results to the mailing list. I guess it'll be quite difficult to
>> solve such a compiler-related bug, but maybe someone has an idea.
>>
>> Best regards,
>> Andreas
>>
>>
>> Mathieu Malaterre schrieb:
>>  > ok I do not have access to a VS6 compiler right now. Hopefully by the
>>  > end of the week. Is there any chance you could try another compiler, I
>>  > really do not understand what is going wrong.
>>  >
>>  > The other you could try is to use a release version of gdcm (such as
>> 1.2.X).
>>  >
>>  > HTH
>>  > -Mathieu
>>  >
>>
>>     
>
>
>