[Insight-developers] ITK 3 tag to use with slicer? Fwd: Slicer release schedule

Bill Lorensen bill.lorensen at gmail.com
Sat Jul 16 16:44:36 EDT 2011


JC,

If you provide a git patchs we can apply it to the itk 3.20 release.

Using:
git format-patch -M

Bill

On Thu, Jul 14, 2011 at 5:09 PM, Jean-Christophe Fillion-Robin
<jchris.fillionr at kitware.com> wrote:
> Hi Folks,
>
> Looking at the history of Slicer/ITK branch "slicer-4.0", you will notice
> that commits have integrated so that it compiles:
>
>   1) on 64bits windows
>
> Merge branch 'fix-vnl-64bits-compile' into slicer-4.0
>
> * fix-vnl-64bits-compile:
>   Review DETERMINE_TYPE vxl macro
>   Add VXL_SIZEOF_SIZE_T test
>   Add VXL_HAS_WIN_WCHAR_T test
>
>
>   Update VXL_HAS_TYPE_OF_SIZE test
>
> See
> https://github.com/Slicer/ITK/commit/71e4277a785ae0f14c5c1cd2a8df1a70d99f1052
>
>   2) on unix-like system using gcc-4.6
>
> Merge branch 'fix-gcc46-compile' into slicer-4.0
>
> * fix-gcc46-compile:
>   COMP: Add missing include <stddef.h> for ptrdiff_t
>   COMP: Add missing include <stddef.h> for ptrdiff_t
>
> See
> https://github.com/Slicer/ITK/commit/309a4221146ee34ee87cd4a3fc0cae26bd7535c4
>
>
> It shouldn't be to hard to patch the version of ITK your are currently using
> for Slicer3.
>
> Any question, please let me know.
> Thanks
> Jc
>
>
> On Thu, Jul 14, 2011 at 4:05 PM, Stephen Aylward
> <stephen.aylward at kitware.com> wrote:
>>
>> Hi Steve,
>>
>> I am CC'ing J2 and JC.
>>
>> JC, in particular, did a huge amount of work to get ITK-Slicer to
>> compile for 64bits.  We should not change versions without involving
>> him.
>>
>> s
>>
>> On Thu, Jul 14, 2011 at 1:57 PM, Steve Pieper <pieper at ibility.net> wrote:
>> > Hi Hans, Bill, Stephen Luis -
>> >
>> > Is there a version of ITK 3 that compiles on the gcc-4.6 compiler?  I'm
>> > not
>> > on the itk-devel list so I can't follow the link in Dominique's email,
>> > but I
>> > guess there's been some discussion of it.  (Bill - this is the question
>> > I
>> > mentioned the other day on the phone).
>> >
>> > What I'm looking for is a version of ITK to make the default for the
>> > current
>> > slicer3 trunk so that it will build on the latest compilers.  Also we'll
>> > want to use that version for slicer4 currently, with the ideas that
>> > we'll
>> > eventually want to swap over to ITK 4.x when it settles down.
>> >
>> > Thanks,
>> > Steve
>> >
>> >
>> > ---------- Forwarded message ----------
>> > From: Dominique Belhachemi <domibel at debian.org>
>> > Date: Thu, Jul 14, 2011 at 11:31 AM
>> > Subject: Re: Slicer release schedule
>> > To: pieper at bwh.harvard.edu
>> > Cc: Ron Kikinis <kikinis at bwh.harvard.edu>
>> >
>> >
>> > Hi Steve,
>> >
>> > I asked in May if they can do a new patch release. They patched their
>> > git release branch and I am waiting now...
>> >
>> > http://www.itk.org/mailman/private/insight-developers/2011-May/018475.html
>> >
>> > BTW, This doesn't affect the Debian packages, it only affects people
>> > who compile Slicer3 from scratch on a Linux box with the current
>> > gcc-4.6 compiler.
>> >
>> > Thanks
>> > Dominique
>> >
>> >
>> > On Wed, Jul 13, 2011 at 5:15 PM, Steve Pieper <pieper at ibility.net>
>> > wrote:
>> >>
>> >> On Sun, Jul 10, 2011 at 7:18 PM, Dominique Belhachemi
>> >> <domibel at debian.org>
>> >>> ITK looks good. There are basically no changes to ITK 3.x. But for the
>> >>> current Slicer3 release you have to ask for a new tag. Otherwise user
>> >>> will run into gcc-4.6 compilation issues.
>> >>>
>> >>
>> >> For packaging we should be able to use the 3.20 release (I don't recall
>> >> the
>> >> version issues - does 3.20 build on gcc 4.6?).  Or if that's the one
>> >> that
>> >> fails we can probably twist their arms to make a 3.22 version with the
>> >> fix
>> >> for everyone.
>> >>
>> >
>> >
>>
>>
>>
>> --
>>
>> ==============================
>> Stephen R. Aylward, Ph.D.
>> Director of Medical Imaging Research
>> Kitware, Inc. - North Carolina Office
>> http://www.kitware.com
>> stephen.aylward (Skype)
>> (919) 969-6990 x300
>
>
>
> --
> +1 919 869 8849
>
>


More information about the Insight-developers mailing list