On Sep 30, 2013, at 2:16 PM, Mohit Daga <[email protected]> wrote: > > I think I should prioritize this after the polishing required.
I agree, polish is important here. > Could you give me the pointers on to how to incorporate this in BRL-CAD's > code source ? Suggest starting simple, just add a cmake test for libexr existing (similar to testing -lcurses) and if it exists, you turn on code and use it. Don't worry about integrating their sources in our tree. That would be much later. >From libicv's perspective, it's more about making sure the library captures an >exr image's data without loss, and how to do that. > Sure your pointers will help me in working in a direction rather than > wandering. Same suggestion as before: modularize the formats. Put everything for ppm into an icv subdirectory for example, and get it to work without ppm mentioned in the icv.h header (or any public header). There are many ways to do that. Physically moving the ppm logic into a subdir with an src/libicv/ppm/ppm.h included in src/libicv files where needed is one possible way that would get it closer to modular. Ultimately, there will need to be a set of callback functions defined. Cheers! Sean ------------------------------------------------------------------------------ October Webinars: Code for Performance Free Intel webinars can help you accelerate application performance. Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from the latest Intel processors and coprocessors. See abstracts and register > http://pubads.g.doubleclick.net/gampad/clk?id=60134071&iu=/4140/ostg.clktrk _______________________________________________ BRL-CAD Developer mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/brlcad-devel
