Should I add ICU_* on Cmake step ?

Compilation and installation of DCMTK

Moderator: Moderator Team

Post Reply
Message
Author
MED_G
Posts: 15
Joined: Fri, 2017-11-17, 09:06

Should I add ICU_* on Cmake step ?

#1 Post by MED_G » Mon, 2017-11-20, 13:03

Hello,


I'm trying to install DCMTK 3.6.2 .
I'm using Cmake 3.10.0-rc5.

should I add ICU_* , before or just add WITH_LIB* ?

Other question: I used MD on previous compilation/installation but I need know the difference between" dcmtk-3.6.2-win32-support_MD-msvc-14.0 " and "dcmtk-3.6.2-win32-support_MT-msvc-14.0 " ?

http://prntscr.com/hctl8m

http://prntscr.com/hctlw0


Thank you

Jan Schlamelcher
OFFIS DICOM Team
OFFIS DICOM Team
Posts: 318
Joined: Mon, 2014-03-03, 09:51
Location: Oldenburg, Germany

Re: Should I add ICU_* on Cmake step ?

#2 Post by Jan Schlamelcher » Tue, 2017-11-21, 11:16


MED_G
Posts: 15
Joined: Fri, 2017-11-17, 09:06

Re: Should I add ICU_* on Cmake step ?

#3 Post by MED_G » Tue, 2017-11-21, 12:36

Hi Jan,

Thank you for your fast feedback.
yes, I already followed those instructions.





Best regard

Jan Schlamelcher
OFFIS DICOM Team
OFFIS DICOM Team
Posts: 318
Joined: Mon, 2014-03-03, 09:51
Location: Oldenburg, Germany

Re: Should I add ICU_* on Cmake step ?

#4 Post by Jan Schlamelcher » Tue, 2017-11-21, 12:59

Then I don't seem to understand your question, can you perhaps try to explain it diffrently?

MED_G
Posts: 15
Joined: Fri, 2017-11-17, 09:06

Re: Should I add ICU_* on Cmake step ?

#5 Post by MED_G » Tue, 2017-11-21, 14:34

Hi,

I mean, during Cmake step, ( after configuration ), should I add ICU path, then run generation?
or just, use LIBICONV only ?


thanks

Jan Schlamelcher
OFFIS DICOM Team
OFFIS DICOM Team
Posts: 318
Joined: Mon, 2014-03-03, 09:51
Location: Oldenburg, Germany

Re: Should I add ICU_* on Cmake step ?

#6 Post by Jan Schlamelcher » Wed, 2017-11-22, 09:34

I see. Both libraries are mutally exclusive. What happens if you add the paths for both is that one of them gets chosen, currently libiconv is the default. So it would in fact make no difference if you also add the ICU paths or not, since the ICU would be ignored if libiconv is available.

MED_G
Posts: 15
Joined: Fri, 2017-11-17, 09:06

Re: Should I add ICU_* on Cmake step ?

#7 Post by MED_G » Wed, 2017-11-22, 12:20

Hi Jan,
Jan Schlamelcher wrote:I see. Both libraries are mutally exclusive. What happens if you add the paths for both is that one of them gets chosen, currently libiconv is the default. So it would in fact make no difference if you also add the ICU paths or not, since the ICU would be ignored if libiconv is available.
ok, just to make sure all is fine.

Thank you

Post Reply

Who is online

Users browsing this forum: No registered users and 1 guest