> On Jul 20, 2015, at 4:11 AM, Ghislain Vaillant <[email protected]> wrote: > > I have used the find module from the Blender project initially. Ideally, > since this is a CMake project, a CMake config exporting the right targets and > macros would be much more helpful.
Oh, that's a good idea. They are GPL, I think, so the license doesn't allow me to incorporate it into our project directly. But maybe it will inspire me to cook up one of my own using its layout as guidance. > GIPL will be written from scratch, since no official library was written for > it. There is a reasonably well working MATLAB implementation that illustrates > how the format works. > > Nifti has an official library that I plan to use. > > Not sure about ANALYZE. Will have to do further research on that one. As with the existing plugins, I recommend that any time the dependent library is not found, that OIIO simply skips building support for that format, rather than being a fatal build break. These aren't common formats for OIIO's main user base, so I want it to be completely painless for them to build OIIO without these libraries being installed. But I do think it's cool for OIIO's format support to extend to those used for medical imaging. Just to fill the rest of us in, how are these three formats used? I mean, under what circumstances is one chosen over another, and/or why any of them over DICOM? Do you think it would be helpful for us to also have direct support for DICOM images? -- Larry Gritz [email protected] _______________________________________________ Oiio-dev mailing list [email protected] http://lists.openimageio.org/listinfo.cgi/oiio-dev-openimageio.org
