Proposals:Updating Nrrd library 2009: Difference between revisions
From KitwarePublic
Jump to navigationJump to search
Line 24: | Line 24: | ||
* running a "pre-GNUmakefile" gnu makefile, which also uses a little perl script unteem.py. | * running a "pre-GNUmakefile" gnu makefile, which also uses a little perl script unteem.py. | ||
** The comments in pre-GNUmakefile explain this some. | ** The comments in pre-GNUmakefile explain this some. | ||
= Update Procedure = | |||
Perform the following two tasks: | |||
== From ITK to NrrdIO == | |||
For all the changes made to | |||
Insight/Utilities/NrrdIO | |||
after the last Nrrd batch commit, | |||
understand what the change was, and then apply the same change to either sourceforge's NrrdIO or even better, to Teem itself. | |||
This is probably not a one-day project. | |||
== From Nrrd to ITK == | |||
Gradually or all at once, depending on our bravery, | |||
we copy sourceforge's NrrdIO to | |||
Insight/Utilities/NrrdIO | |||
and see what breaks,... and fix it |
Revision as of 14:20, 2 December 2009
Nrrd Library
This page describes the procedure for synchronizing the NrrdIO libary in Teem, with the one in Insight/Utilities/Nrrd
Note that patches may have to be moved in both directions.
Background
- Nrrd started as one of the libraries in Teem <http://teem.sf.net>
- NrrdIO is a subset of Nrrd containing only the IO functionalities.
- The only part of Teem that's in ITK is in NrrdIO.
- Creating NrrdIO from Teem is done by a GNUMakefile and a perl script.
- The back-propagation that should happen is from NrrdIO back to Teem, because the idea is that NrrdIO should be periodically regenerated from Teem.
Checking out NrrdIO
Use the following SVN command
svn co http://teem.svn.sourceforge.net/svnroot/teem/NrrdIO/trunk NrrdIO
This was generated in the Teem side by
- running a "pre-GNUmakefile" gnu makefile, which also uses a little perl script unteem.py.
- The comments in pre-GNUmakefile explain this some.
Update Procedure
Perform the following two tasks:
From ITK to NrrdIO
For all the changes made to
Insight/Utilities/NrrdIO
after the last Nrrd batch commit, understand what the change was, and then apply the same change to either sourceforge's NrrdIO or even better, to Teem itself.
This is probably not a one-day project.
From Nrrd to ITK
Gradually or all at once, depending on our bravery, we copy sourceforge's NrrdIO to
Insight/Utilities/NrrdIO
and see what breaks,... and fix it