CGAL users discussion list

[Dominik Szczerba <>]

Hi,

Many thanks for the useful information.

May I suggest for simplicity and elegance providing a function like:

_image* _readImage_buffer()

after

_image* _readImage_raw()

to simply import (or better, mount without copying) an existing memory buffer.
This will render read_vtk_image_data obsolete, at the same time easily
enabling other useful formats like hdf5 or xdmf.

Many thanks,
Dominik

On Thu, Sep 9, 2010 at 11:25 AM, Laurent Rineau (GeometryFactory)
<>
 wrote:
> On Thursday 09 September 2010 11:11:11 Dominik Szczerba wrote:
>> Hi,
>>
>> Thanks for the email. You are right, I do not actually need VTK, just
>> import memory buffer.
>> But VTK is already better than the INR format. I saw the code samples
>> to read VTK objects. My original question was how to enable VTK
>> support when building. There is no option to control this in the main
>> CMakeLists.txt.
>
> As I have said, the VTK support is not really a VTK support. If you really
> want to enable that piece of code, configure and compile CGAL after adding a
> CMake variable in your cache:
>  cmake -DWITH_VTK:BOOL=TRUE .
> (or add a Boolean variable named "WITH_VTK" in cmake-gui, and set it to
> TRUE/ON).
>
> But it will probably not suit you. There is not strait-forward VTK image
> support in CGAL. The option WITH_VTK=TRUE just adds a member function to
> CGAL::Image_3:
>  bool read_vtk_image_data(vtkImageData*);
>
> --
> Laurent Rineau, PhD
> R&D Engineer at GeometryFactory           http://www.geometryfactory.com/
> Release Manager of the CGAL Project       http://www.cgal.org/
>
> --
> You are currently subscribed to cgal-discuss.
> To unsubscribe or access the archives, go to
> https://lists-sop.inria.fr/wws/info/cgal-discuss
>
>