Hi,<br><br>FWIW I&#39;m considering boost GIL to implement the few image algorithms I need, and I need proper image I/O on top of that.<br><br>As I&#39;m using FreeImage in my current codebase, I thought about exposing FreeImage image memory layout to GIL. You can find the, quite simplistic, source code here :<br>

<br><a href="http://code.google.com/p/rotoglup-scratchpad/source/browse/trunk/rtgu/image_io/image_io.hpp" target="_blank">http://code.google.com/p/rotoglup-scratchpad/source/browse/trunk/rtgu/image_io/image_io.hpp</a><br>
<a href="http://code.google.com/p/rotoglup-scratchpad/source/browse/trunk/rtgu/image_io/image_io.cpp" target="_blank">http://code.google.com/p/rotoglup-scratchpad/source/browse/trunk/rtgu/image_io/image_io.cpp</a><br>
<br><a href="http://code.google.com/p/rotoglup-scratchpad/source/browse/trunk/rtgu/image_io/gil/borrowed_image.hpp" target="_blank">http://code.google.com/p/rotoglup-scratchpad/source/browse/trunk/rtgu/image_io/gil/borrowed_image.hpp</a><br>

<br>I created a &#39;borrowed_image&#39; class that mimics the behaviour of gil::image : it is not allocating memory itself, it takes an existing memory buffer and a &#39;deleter&#39; (under the form of a boost::shared_ptr&lt;void&gt;) as input. This allows to use directly the memory allocated by FreeImage, avoiding extra copy, in case of file input.<br>

<br>Feel free to use the code as a starting point, if you have similar needs, and I&#39;d be glad to have comments about the concept of &#39;borrowed_image&#39; class, and about its interface, as I feel I&#39;m missing something.<br>

<br>Cheers,<br><br>Nicolas.<br>