Hello,
I have a custom ("branded") app and a custom PV plugin. I'd prefer to keep the
code for these separate, just for clean development, but I want the app to
"know about" the plugin so it can package them together automatically.
I can compile both at the same time by putting them each in their own
subdirectory, and having a root CMakeLists.txt simply specifying the names of
those subdirectories. But, when I list my custom plugin in the app's
OPTIONAL_PLUGINS, it doesn't get packaged with the app libraries.
(PointSpritePlugin does, though, as I told it to.)
Is there some less-naive structure I should be giving my project rather than
just two separate subdirectories (and accompanying CMake files) so my app will
"know about" my plugin (and maybe so they can also be built into the same
"build/bin" directory, kind of like when paraview is built)?
Also, for clarification, the notes on the wiki for Writing_Custom_Applications
says that OPTIONAL_PLUGINS should use "name of the plugin specified in the
add_paraview_plugin call", but PointSpritePlugin works and it's actually the
project() name rather than the add_paraview_plugin() name (which is
CSCS_PointSprite_Plugin).
Thanks a lot,
-Eric
_______________________________________________
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Please keep messages on-topic and check the ParaView Wiki at:
http://paraview.org/Wiki/ParaView
Follow this link to subscribe/unsubscribe:
http://www.paraview.org/mailman/listinfo/paraview
