Say I have written a VTK filter and the directory structure is as follows:
.../MyFilter/MyFilter.h
.../MyFilter/MyFilter.cxx
.../MyFilter/CMakeLists.txt
And it is built in
.../MyFilter/bin
I now want to make a Paraview plugin for it. I would like to keep it very
separate though so I can still hav
Hi,
My own experience is the following:
I usually make a project with this directory structure:
./
./Algorithms
./Plugins
./(other stuffs)
a global CMakeLists defines different variables:
- ALGORITHM_PATH
- PLUGIN_PATH
A user-defined variable
- BUILD_PARAVIEW_PLUGIN
If the latter is on, then I
David,
Jerome's suggested structure is good. But if you are lazy like me and just
want to get the darn thing to work, simply adding
INCLUDE_DIRECTORIES(${CMAKE_CURRENT_SOURCE_DIR}/..)
to the MyFilter/plugin/CMakeLists.txt file should do the trick.
-Ken
On 11/28/09 1:14 AM, "Jérôme" wrote:
