Hello again,
after organizing my project and working out VTK and CMake everything
seemed
to go right, save the detail that PV could not load the plugin.
Linking some shared libraries should resolve this, but if I try, I get
an error related
to the shared objects:
/usr/bin/ld: /home/th/lib/Linux-x86_64/libgdif2.a(Block.o): relocation
R_X86_64_32S
against `a local symbol' can not be used when making a shared object;
recompile with -fPIC
/home/th/lib/Linux-x86_64/libgdif2.a: could not read symbols: Bad value
After recompiling the external library with -fPIC enabled and the
plugin code as well,
the error still remains unchanged.
Has someone else encounter this problem?
Best regards
Am 07.01.2009 um 15:39 schrieb Michael Jackson:
Try looking at my CVS repository at <http://www.bluequartz.net/viewvc/CTMD/PVRoboMet/
>. That plugin has both a server and client side plugins (only the
server side needs the extra libraries). That project references code
in the <http://www.bluequartz.net/viewvc/CTMD/MXADataModel/> module
also.
The CVS server is kinda slow so give it little bit of time to send
the data through the web interface.
_________________________________________________________
Mike Jackson [email protected]
BlueQuartz Software www.bluequartz.net
Principal Software Engineer Dayton, Ohio
On Jan 7, 2009, at 9:22 AM, Thorsten Hater wrote:
Thanks!
An example would be very nice indeed.
Michael Jackson wrote:
I use the following to link additional libraries to my server side
plugin:
TARGET_LINK_LIBRARIES("${MODULE_NAME}"
vtkClientServer
vtkPVServerManager
${MXA_LIBRARIES}
${MXA_SUPPORT_LIBRARIES}
${BOOST_FILESYSTEM_LIBRARY}
If you are building your plugin at the same time you compile
ParaView by using the $MODULE_NAME}ParaViewImport.cmake and the
Paraview_Extra_External_Modules cmake property then you can use
the ${PARAVIEW_ADDITIONAL_LIBRARIES} variable to add more
libraries to the linking of the pvFilters target.
I have a few projects that do this if you are interested in seeing
them.
_________________________________________________________
Mike Jackson [email protected]
BlueQuartz Software www.bluequartz.net
Principal Software Engineer Dayton, Ohio
On Jan 7, 2009, at 8:47 AM, Thorsten Hater wrote:
Thanks a lot!
I ended up last night hand-editing the Makefile generated
by CMake to include and link an additional library to the
plugin binary, but I guess there is some better method.
If someone could point me in the right direction?
Best regards
Thorsten
Michael Jackson wrote:
vtkImage->GetScalarPointer(); will return a void* which you can
cast to the appropriate type for your image data.
You can then use any byte copying routine to copy the data from
the file into the byte array. To save yourself some of that
copying if your data file is setup so that you can read some
header information so that you know how much to allocate you can
FIRST allocate the vtkImageData object, get the pointer to the
front of the array and read directly from the file into the array.
_________________________________________________________
Mike Jackson [email protected]
BlueQuartz Software www.bluequartz.net
Principal Software Engineer Dayton, Ohio
On Jan 6, 2009, at 11:17 AM, Thorsten Hater wrote:
Hello everyone.
I'm trying to implement a custom reader for ParaView 3.4.
The output data is of the ImageData type.
With the help of the ParaView guid I got as far as implementing
the reader, save the most important bit of filling the actual
data
into the output object.
So I have got the raw binary array - or file, if this is better -
and the vtkImageData object.
How can I move my data into the vtk object?
Thanks in advance
Thorsten
_______________________________________________
ParaView mailing list
[email protected]
http://www.paraview.org/mailman/listinfo/paraview
_______________________________________________
ParaView mailing list
[email protected]
http://www.paraview.org/mailman/listinfo/paraview
_______________________________________________
ParaView mailing list
[email protected]
http://www.paraview.org/mailman/listinfo/paraview
_______________________________________________
ParaView mailing list
[email protected]
http://www.paraview.org/mailman/listinfo/paraview
_______________________________________________
ParaView mailing list
[email protected]
http://www.paraview.org/mailman/listinfo/paraview
