Burlen,
Looking at the code, the problem is not with the plugin (or
add_paraview_plugin), which indeed add the dependency as appropriate,
the issue is in io/CMakeLists.txt [1]. When you use VTK_LIBRARIES,
you're linking against all VTK modules and its dependencies, which is
really an over kill. In
sure, although I hope this isn't asking too much, as the build has a few
dependencies, I think for this only NetCDF is needed.
here is the repo
https://github.com/LBL-EESA/TECA
plugin is in the ParaView dir.
On 01/03/2017 01:35 PM, Utkarsh Ayachit wrote:
Burlen,
Happy new year to you too!
Hm
Burlen,
Happy new year to you too!
Hmm, that's odd. Can you share the plugin code with me? Let's see if I
can reproduce the issue.
Utkarsh
On Tue, Jan 3, 2017 at 2:13 PM, Burlen Loring wrote:
> Hi Utkarsh, Happy new year!
>
> I have a couple of questions about the new way.
>
> Shouldn't this b
Hi Utkarsh, Happy new year!
I have a couple of questions about the new way.
Shouldn't this be automatically added by ADD_PARAVIEW_PLUGIN macro like
the rest of the PV related link dependencies?
Should you really need to link Qt to all plugins?
My plugin is a number of simple server side only
Burlen,
See Qt dependencies changes documented here:
http://www.paraview.org/ParaView3/Doc/Nightly/www/cxx-doc/MajorAPIChanges.html
include(ParaViewQt) # generally not needed, since auto-included
pv_find_package_qt(qt_targets
QT4_COMPONENTS QtGui
QT5_COMPONENTS Widgets)
pv_qt_wrap_cpp(moc_fi
After upgrading to 5.2 my plugin is not compiling. When I configure the
plugin I see a few pages of the following:
CMake Warning (dev) at io/CMakeLists.txt:54 (add_library):
Policy CMP0028 is not set: Double colon in target name means ALIAS or
IMPORTED target. Run "cmake --help-p
