You can try the following:

SET(PARAVIEW_ADDITIONAL_LIBRARIES
     ${PARAVIEW_ADDITIONAL_LIBRARIES}
     ${vtkexpat} ${NETCDF_LIBRARY} ${COMMON_LIBRARY} ${VDF_LIBRARY})

BEFORE the line

IF (PARAVIEW_BUILD_QT_GUI)


Also ParaView provides its own expat library which you may be able to use instead of your own or a system one. vtkexpat

Hope that helps
_________________________________________________________
Mike Jackson                  mike.jack...@bluequartz.net
BlueQuartz Software                    www.bluequartz.net
Principal Software Engineer                  Dayton, Ohio



On Jan 17, 2009, at 8:53 AM, Natalie Happenhofer wrote:

Well,
I tried everything, changing the cmake_install_prefix and so on, and lastly I checked the CMakeLists.txt file which took care of the Plugin and there I found a mistake.. a library name spelled incorrectly. I changed that and now I get
linker errors which I do not know how to get rid of:

No rule to make target `/usr/local/unpackaged/libcommon.so', needed by `bin/libVdcWriter.so'. Stop.

That libcommon.so is a library which is already build, but not by paraview, and I want it to be linked to my code. Here
is the CMakeLists.txt:

INCLUDE(${ParaView_SOURCE_DIR}/CMake/ParaViewPlugins.cmake)

INCLUDE_DIRECTORIES(
  ${VTK_INCLUDE_DIR}
  ${PARAVIEW_INCLUDE_DIRS}
  ${VTKEXPAT_SOURCE_DIR}
 )

FIND_PACKAGE(Qt4)
INCLUDE(${QT_USE_FILE})

FIND_PACKAGE(ParaView REQUIRED)
 INCLUDE(${PARAVIEW_USE_FILE})

FIND_PACKAGE(VDC REQUIRED)
INCLUDE_DIRECTORIES(${VDC_INCLUDE_DIR})

FIND_PACKAGE(NETCDF REQUIRED)
INCLUDE_DIRECTORIES(${NETCDF_INCLUDE_DIR})

IF (PARAVIEW_BUILD_QT_GUI)
  ADD_PARAVIEW_PLUGIN(VdcWriter "1.0"
    GUI_RESOURCE_FILES GUIVdcWriter.xml
    SERVER_MANAGER_XML SMVdcWriter.xml
    SERVER_MANAGER_SOURCES vtkVdcWriter.cxx
    )
ELSE (PARAVIEW_BUILD_QT_GUI)
  ADD_PARAVIEW_PLUGIN(VdcWriter "1.0"
    SERVER_MANAGER_XML SMVdcWriter.xml
    SERVER_MANAGER_SOURCES vtkVdcWriter.cxx
    )
ENDIF (PARAVIEW_BUILD_QT_GUI)

TARGET_LINK_LIBRARIES(VdcWriter ${EXPAT_LIBRARY} ${NETCDF_LIBRARY} $ {COMMON_LIBRARY} ${VDF_LIBRARY}

I believe that target_link_libraries command is not correct, but how can I link all these libraries to my code?

thx
Natalie



> Date: Thu, 15 Jan 2009 10:15:44 -0500
> From: burlen.lor...@kitware.com
> To: natalieh...@hotmail.com
> CC: paraview@paraview.org
> Subject: Re: [Paraview] Writer Plugin cannot be loaded
>
> Natalie Happenhofer wrote:
> > Hi!
> >
> > I have written a Writer-Plugin and after (at last) successfully
> > compiling and linking it within Paraview, I tried to load it with the
> > PluginManager,
> > and in the Paraview/build/bin directory I found my libVdcWriter.so, > > but loading fails. I get the error message: "libVdcWriter.so: no such
> > file or directory"
> > But the file is in the build/bin - directory, the
> > plugin-manager-browser found it!
> > Does anyone know what could be the problem here? Is it possible that I
> > missed to link something, any library from paraview so that this
> > plugin can be loaded?
>
> It sounds like the dynamic linker/loader , ld, isn't finding your
> libVdcWriter.so library. first you can verify by running ldd on your
> plugin and searching for "not found". like this:
>
> ldd /path/to/libMyPlugin.so | grep "not found"
>
> This will list the libraries that are not found. There are a number of
> ways to remedy such an issue. The easiest (especially for debugging
> purposes) is to use LD_LIBRARY_PATH on the command line to add locations > to ld's search path. You know where the missing library is located then
> you can run paraview like this:
>
> LD_LIBRARY_PATH=/path/to/missing/lib/folder /path/to/paraview
>
> or you can export this variable in your shell.
>
> >
> > and by the way, a stupid question: linux .so - files are equivalent to > > windows .dll-files, true? so while I´m loading my plugins as .dlls in
> > windows, with linux they have the ending .so, right?
> >
> > thx a lot,
> > Natalie Happenhofer
> >
> >
> >
> > ------------------------------------------------------------------------
> > ¡Descúbrelo! ¿Qué puedes hacer con el nuevo Windows Live?
> > <http://www.microsoft.com/latam/windows/windowslive/>
> > ------------------------------------------------------------------------
> >
> > _______________________________________________
> > ParaView mailing list
> > ParaView@paraview.org
> > http://www.paraview.org/mailman/listinfo/paraview
> >
>
>
> --
> Burlen Loring
> Kitware, Inc.
> R&D Engineer
> 28 Corporate Drive
> Clifton Park, NY 12065-8662
> Phone: 518-371-3971 x137
>

con amigos y familiares. Descubre todas las formas en que puedes estar en contacto_______________________________________________
ParaView mailing list
ParaView@paraview.org
http://www.paraview.org/mailman/listinfo/paraview

_______________________________________________
ParaView mailing list
ParaView@paraview.org
http://www.paraview.org/mailman/listinfo/paraview

Reply via email to