Hi all,
As I mentioned to Kris, in CCPi we use anaconda to distribute the software. Anaconda is meant to be a python distribution and environment management system. However, it has grown by community effort and it ships now a wealth of software other than mere python packages.
To make a long story short, in conda you find itk. And it'll be very easy to install! As long as we make conda packages of SIRF this could be a solution to our problems.
I'm going to talk about this in the next SW meeting (apparently), but for the impatients Conda has become a packaging system within the system. It allows to install python packages and other software, keeping it isolated from the main OS. It also keeps software consistent, as the packages are compiled with the same compiler!
I've done some research and I've found out that the Gadgetron people already provide conda recipes (the instructions for the build and packaging) for all their dependencies! To keep it short, only SIRF and STIR don't have a conda recipe.
I'll try to create a conda recipe for SIRF or just STIR before the 15th (?).
Edo
> -----Original Message-----
> From: CCP-PETMR Developers list [mailto:CCP-PETMR-
> [log in to unmask]] On Behalf Of Richard
> Sent: 20 November 2017 13:08
> To: [log in to unmask]
> Subject: Re: ITK
>
> Individual modules can be set by de-selecting the option
> ITK_BUILD_DEFAULT_MODULES and selecting individual modules, e.g.,
> ITKGroup_IO or ITKGroup_Core.
>
> Richard
>
> On Mon, 2017-11-20 at 12:57 +0000, Thielemans, Kris wrote:
> > Hi Richard
> >
> > That difference looks indeed very small to me. How did you set the
> > modules?
> >
> > Regarding the 2 options. We certainly don't require them. What we do
> > for other packages such as stir is to have corresponding options in
> > the superbuild, and then forward them explicitly in the
> > External*.cmake. We haven't found another way that makes sense to a
> > user. (There is/was an Issue on this).
> >
> > Kris
> >
> >
> >
> > From: Brown, Richard
> > Sent: Monday 20 November 11:00
> > Subject: ITK
> > To: Thomas, Ben, Thielemans, Kris
> >
> >
> > Hi Kris, Ben,
> >
> > I was just having a play around with compiling ITK.
> >
> > It seems that the standard compile is 275 MB, whereas compiling with
> > just the I/O module is 244 MB. So if we are going to include ITK, we
> > might as well compile the whole thing. We should obviously give the
> > option in CMake to use a system version of ITK in case the user
> > already has it installed.
> >
> > If we were to include ITK, would we need the following two options?
> > - ITK_USE_GPU (requires OpenCL)
> > - ITK_WRAP_PYTHON
> >
> > Regards,
> > Richard
> >
> >
|