[Insight-users] redistribution questions
Luis Ibanez
luis.ibanez at kitware.com
Mon Aug 13 06:58:29 EDT 2007
Hi Qing,
No, you don't need to install ITK in the target computer.
Simply:
1) Build ITK as STATIC (not SHARED) in your computer
2) Build your application in your computer
3) Copy your executable to the target computer
In this way there are no ITK libraries or files that you
need to copy to the target computer. You will only need
to copy the executable.
Most of ITK is C++ templated code, that gets instantiated
directly when you compile your application. There are very
few non-templated classes in ITK, that's the reason why
it is not worth to build shared libraries (dlls) for ITK.
Regards,
Luis
----------------
qing xu wrote:
> Hi Luis,
>
> I have several simply questions about the redistribution. Do I need to
> install itk in the user computer? Can user just run the exe file on
> their platform? I am suprised that I did not find any dll files for ITK,
> although there are some lib fils used. Does that mean I do not need to
> bring any dll files to the user? Thanks.
>
> Qing
>
>
>> From: "qing xu" <qingxu8 at hotmail.com>
>> To: luis.ibanez at kitware.com
>> CC: insight-users at itk.org
>> Subject: Re: [Insight-users] redistribution questions
>> Date: Wed, 08 Aug 2007 13:40:29 +0000
>>
>> Hi Luis,
>>
>> Thank you for your patient explaination. My users just need to run the
>> application, they do not have the need to rebulid the program. So I
>> think I would just provide them with the exe application file and the
>> itk dll. I would bulid everything on my side. Thanks for your help.
>>
>> Qing
>>
>>
>>> From: "Luis Ibanez" <luis.ibanez at kitware.com>
>>> To: "qing xu" <qingxu8 at hotmail.com>
>>> CC: insight-users at itk.org
>>> Subject: Re: [Insight-users] redistribution questions
>>> Date: Tue, 7 Aug 2007 09:57:28 -0400
>>>
>>> Hi Qing,
>>>
>>> Well, the "binary" form of ITK not a real solution either,
>>> since most of ITK is templated code, the libraries contain
>>> a very small portion of the total toolkit.
>>>
>>> If you are distributing your application and want others
>>> to be able to rebuild it, then they should have access
>>> to the source code of ITK. Of course, only if they are
>>> trying to rebuild it.
>>>
>>> If your users are only going to run your application,
>>> then the simplest way to proceed is to compile ITK
>>> for Statics libraries, and just distribute your executable.
>>>
>>> You may also want to take a look at CPack (from CMake)
>>> which is the tool intended for packaging code for distribution.
>>>
>>>
>>> Regards,
>>>
>>>
>>> Luis
>>>
>>>
>>> --------------------------------
>>> On 8/6/07, qing xu <qingxu8 at hotmail.com> wrote:
>>> >
>>> > Hi Luis,
>>> >
>>> > Thank you for your suggestion.You are right, it seems that there is
>>> little
>>> > difference between incorporting part of or all of the itk source code.
>>> > Maybe
>>> > I will just keep using the binary form of itk.
>>> > Thanks a lot.
>>> >
>>> > Qing
>>> >
>>> >
>>> >
>>> > >From: "Luis Ibanez" <luis.ibanez at kitware.com>
>>> > >To: "qing xu" <qingxu8 at hotmail.com>
>>> > >CC: insight-users at itk.org
>>> > >Subject: Re: [Insight-users] redistribution questions
>>> > >Date: Mon, 6 Aug 2007 13:28:40 -0400
>>> > >
>>> > >Hi Qing,
>>> > >
>>> > >Yes, I'm suggesting that you should include all of ITK with your
>>> project.
>>> > >
>>> > >It will be rather difficult to extract only the classes that you are
>>> > using,
>>> > >although it is not impossible.
>>> > >
>>> > >You should ask yourself, what is the purpose of adding to your
>>> project
>>> > >the code from ITK ?
>>> > >
>>> > >Why not just say that you distribute the code, and that it should be
>>> > >build using ITK version X.Y. ?
>>> > >
>>> > >Keep in mind that we make ITK releases every three monts,
>>> > >so, by extracting code from ITK you will also face the challenge
>>> > >of updating your version of the code to new releases of ITK.
>>> > >
>>> > >This may o may not be a problem, depending on who are
>>> > >the recipients of the code that you are delivering, and how
>>> > >you are going to maintain that code for the next five to
>>> > >ten years.
>>> > >
>>> > >
>>> > > Regards,
>>> > >
>>> > >
>>> > > Luis
>>> > >
>>> > >
>>> > >---------------------------------------------------------------------
>>> > >On 8/6/07, qing xu <qingxu8 at hotmail.com> wrote:
>>> > > >
>>> > > > Hi Luis,
>>> > > >
>>> > > > Thanks a lot for your reply.
>>> > > >
>>> > > > I use the 3d versor rigid registration part of ITK, and now I
>>> want to
>>> > > > incorporate the source code of ITK to my project. So, first, I
>>> have to
>>> > > > figure out what files in ITK are related to the functions I am
>>> using.
>>> > >What
>>> > > > I
>>> > > > am doing now is to check the header files to see what must be
>>> included
>>> > >to
>>> > > > implement the registration. But it seems that there are so
>>> many files
>>> > > > related to the registraiton part, is there a easy way to do
>>> that? Are
>>> > >you
>>> > > > suggesting that I should include all the ITK source codes to my
>>> > project?
>>> > > > Thanks.
>>> > > >
>>> > > > Qing
>>> > > >
>>> > > >
>>> > > > >From: "Luis Ibanez" <luis.ibanez at kitware.com>
>>> > > > >To: "qing xu" <qingxu8 at hotmail.com>
>>> > > > >CC: insight-users at itk.org
>>> > > > >Subject: Re: [Insight-users] redistribution questions
>>> > > > >Date: Mon, 6 Aug 2007 12:12:42 -0400
>>> > > > >
>>> > > > >Hi Qing,
>>> > > > >
>>> > > > >Yes, you are allowed (and encouraged)
>>> > > > >to redistribute ITK's source code.
>>> > > > >
>>> > > > >Why are you finding difficult to pack all the code ?
>>> > > > >
>>> > > > >You can just take the tar or .zip file corresponding
>>> > > > >to the ITK release that you are using.
>>> > > > >
>>> > > > >The tar/zip files are available at:
>>> > > > >
>>> > > > > http://www.itk.org/HTML/Download.php
>>> > > > >
>>> > > > >You could also just use the cvs export command
>>> > > > >and if you are using a particular CVS version of ITK.
>>> > > > >
>>> > > > >
>>> > > > > Regards,
>>> > > > >
>>> > > > >
>>> > > > > Luis
>>> > > > >
>>> > > > >
>>> > > > >===========================
>>> > > > >On 8/6/07, qing xu <qingxu8 at hotmail.com> wrote:
>>> > > > > >
>>> > > > > > Hi,
>>> > > > > >
>>> > > > > > I am currently considering incorporating itk source code to my
>>> > > > project.
>>> > > > >I
>>> > > > > > read the copyright notice and seems that it allows me to
>>> > >redistribute
>>> > > > in
>>> > > > > > source code form. But it seems not trivial to find all the
>>> related
>>> > > > >source
>>> > > > > > code files. Anyone has done the similar thing? Any
>>> suggestion is
>>> > > > >welcome.
>>> > > > > > Thanks.
>>> > > > > >
>>> > > > > > Qing
>>> > > > > >
>>> > > > > >
>>> > > > > > _______________________________________________
>>> > > > > > Insight-users mailing list
>>> > > > > > Insight-users at itk.org
>>> > > > > > http://www.itk.org/mailman/listinfo/insight-users
>>> > > > > >
>>> > > >
>>> > > > _________________________________________________________________
>>> > > > Tease your brain--play Clink! Win cool prizes!
>>> > > > http://club.live.com/clink.aspx?icid=clink_hotmailtextlink2
>>> > > >
>>> > > >
>>> >
>>> > _________________________________________________________________
>>> > Learn.Laugh.Share. Reallivemoms is right place!
>>> > http://www.reallivemoms.com?ocid=TXT_TAGHM&loc=us
>>> >
>>> >
>>
>>
>> _________________________________________________________________
>> Booking a flight? Know when to buy with airfare predictions on MSN
>> Travel.
>> http://travel.msn.com/Articles/aboutfarecast.aspx&ocid=T001MSN25A07001
>>
>> _______________________________________________
>> Insight-users mailing list
>> Insight-users at itk.org
>> http://www.itk.org/mailman/listinfo/insight-users
>
>
> _________________________________________________________________
> Now you can see trouble…before he arrives
> http://newlivehotmail.com/?ocid=TXT_TAGHM_migration_HM_viral_protection_0507
>
>
>
More information about the Insight-users
mailing list