[Dcmlib] Probably a stupid mistake of mine

[Mathieu Malaterre]

Tu peux m'envoyer la sortie de:

PrintFile.exe filein=3E768EB7.dcm
et
PrintFile.exe filein=012345.002.050.dcm

Le truc que je comprends pas c'est que le dashboard a Kitware ne
marche pas non plus:
http://public.kitware.com/GDCM/Testing/Sites/DASH3.kitware/GDCM-Win32-vs60/20070912-0100-Nightly/Results/__Testing_TestPrintAllDocument.html

T'es en debug ou en release ? T'es sur que t'as pas de fichier modifie ?

merci
-Mathieu

On 9/13/07, Eduardo.Davila at creatis.insa-lyon.fr
<Eduardo.Davila at creatis.insa-lyon.fr> wrote:
>
> Bonjour,,
>
> Je viens de teste gdcm (cvs version) avec visual 6 , et JPR à côtè de moi.
> Et tout marche bien, 28 Test successfull.
>
>
> --------------------Configuration: RUN_TESTS - Win32
> Release--------------------
> Performing Custom Build Step on C:\Creatis\gdcmtestBin\RUN_TESTS_force_1.rule
> Start processing tests
> Test project C:/Creatis/gdcmtestBin
>   1/ 28 Testing TestEmpty                        Passed
>   2/ 28 Testing TestUtil                         Passed
>   3/ 28 Testing TestBug                          Passed
>   4/ 28 Testing TestHash                         Passed
>   5/ 28 Testing TestCommand                      Passed
>   6/ 28 Testing TestTS                           Passed
>   7/ 28 Testing TestVR                           Passed
>   8/ 28 Testing TestDictGroupName                Passed
>   9/ 28 Testing TestDict                         Passed
>  10/ 28 Testing TestDataEntry                    Passed
>  11/ 28 Testing TestWriteSimple                  Passed
>  12/ 28 Testing TestImageSet                     Passed
>  13/ 28 Testing TestDicomDirElement              Passed
>  14/ 28 Testing TestDicomString                  Passed
>  15/ 28 Testing TestEnumVR                       Passed
>  16/ 28 Testing TestBuildUpDicomDir              Passed
>  17/ 28 Testing TestFileAccessors                Passed
>  18/ 28 Testing TestMakeIcon                     Passed
>  19/ 28 Testing TestLoadAllDocumentsNoPrivNoSe   Passed
>  20/ 28 Testing TestPrintAllDocument             Passed
>  21/ 28 Testing TestReadWriteReadCompare         Passed
>  22/ 28 Testing TestReadWriteJPEGReadCompare     Passed
>  23/ 28 Testing TestDirList                      Passed
>  24/ 28 Testing TestDicomDir                     Passed
>  25/ 28 Testing TestMakeDicomDir                 Passed
>  26/ 28 Testing TestSerieHelper                  Passed
>  27/ 28 Testing TestAllVM                        Passed
>  28/ 28 Testing TestValidate                     Passed
> 100% tests passed, 0 tests failed out of 28
>
>
>
> Eduardo et JPR
>
>
>
>
>
> > 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
> >>>  >
> >>>
> >>>
> >>
> >>
> >>
> > _______________________________________________
> > Dcmlib mailing list
> > Dcmlib at creatis.insa-lyon.fr
> > http://www.creatis.insa-lyon.fr/mailman/listinfo/dcmlib
> >
>
>


-- 
Mathieu