Hi All,

There are some notable changes with this release of the gifti C library.

1. Now zlib is optional, as was done with NIfTI. To use it HAVE_ZLIB must be defined at compile time. See Makefile for an example.

2. The nifti1.h file is #included, so that must be in your include path somewhere. The nifti library is not yet linked.

3. External programs only need to #include gifti_io.h now. The files gifti_xml.h, nifti1.h, expat.h and zlib.h are #included via gifti_io.h.

4. The gifti_test program has been reduced in functionality, so it can merely serve as a simple example of how to interface with the library.

5. The gifti_tool program has been added. This has all the functionality that gifti_test had, with some additions and changes. Note that to write a dataset (gifti, 1D or asc), one must now use the -write_* options, as the examples show under -help.

- rick

Hi all,
I have made some (small) changes to the 0.0.9 Makefile. I didn't want to post these changes to the public file repo. without someone else checking them for errors, compatibility, etc. The makefile is found at:

http://www.sci.utah.edu/~eranders/gifti/...

Basically, I added some new rules to build a shared library out of the gifti_io and gifti_xml file pairs. This will be used to generate Python bindings for GIFTI file support directly in Python (using ctypes)

Thanks,
Erik

Hi Erik,

I tried that out, and it worked well. But for consistency,
it would be nice to call the library libgiftiio, to match
libniftiio.

What do you think about this? I've made a few name changes
and linked in niftiio (that will be going in soon, anyway).

http://afni.nimh.nih.gov/sscc/staff/rick...

- rick

Rick,
That's no problem at all for me. I will continue the Python-based stuff I'm working on with the new Makefile that you propose.

Erik