[IGSTK-Developers] Code checking into IGSTK
Haiying Liu
hliu at bwh.harvard.edu
Tue May 20 15:02:37 EDT 2008
Hi Patrick,
Slicer 3 and IGSTK each has its own copy of OpenIGTLink. We'll need to fix
the issue to make OpenIGTLink maintenance easier.
Thanks,
Haiying
On Mon, 19 May 2008, Patrick Cheng wrote:
> Hi Haiying,
>
> Thank you for submitting the code. We will give it a try.
>
> I have a question regarding the handling of OpenIGTLink library:
> Since it will be shared by many platforms, it seems like that it is
> better to build it as a stand alone library and then have IGSTK link to
> it, rather than release it the IGSTK utilities directory. It is also a
> problem to keep sync with the main OpenIGTLink cvs, which I believe it's
> under Slicer-IGT branch?
>
> Thank you,
>
> Patrick
>
>
> Haiying Liu wrote:
> > Hi,
> >
> > Checking my code into IGSTKSandbox has been completed. Please let me know
> > if you find any problems caused by my checkin.
> >
> > Thanks,
> >
> >
> > Haiying
> >
> > On Mon, 19 May 2008, Haiying Liu wrote:
> >
> >> Hi,
> >>
> >> I'm going to check in code now into IGSTKSandbox to add support of
> >> OpenIGTLink. I'll send another email when I'm done.
> >>
> >>
> >> Thnaks,
> >>
> >>
> >>
> >>
> >> Haiying Liu
> >> _______________________________________________
> >> IGSTK-Developers mailing list
> >> IGSTK-Developers at public.kitware.com
> >> http://public.kitware.com/cgi-bin/mailman/listinfo/igstk-developers
> >>
> > _______________________________________________
> > IGSTK-Developers mailing list
> > IGSTK-Developers at public.kitware.com
> > http://public.kitware.com/cgi-bin/mailman/listinfo/igstk-developers
> >
> >
>
More information about the IGSTK-Developers
mailing list