Great. There should probably be some documentation updates to let developers
know that the variable needs to be turned on so that their plugins will get
copied. I still need to try this on windows.
-
Mike Jackson www.bluequartz.net
Principal Software Engineer mike.ja
Hi Mike,
I committed your patch to master and cherry picked it onto the release
branch.
On Mon, May 17, 2010 at 9:41 AM, Michael Jackson <
mike.jack...@bluequartz.net> wrote:
> 519:[mjack...@ferb:ParaView]$ git diff
> diff --git a/CMakeLists.txt b/CMakeLists.txt
> index 45eef61..6698fcc 100644
>
519:[mjack...@ferb:ParaView]$ git diff
diff --git a/CMakeLists.txt b/CMakeLists.txt
index 45eef61..6698fcc 100644
--- a/CMakeLists.txt
+++ b/CMakeLists.txt
@@ -26,6 +26,11 @@ GET_PROPERTY(PV_TARGET_SUPPORTS_SHARED_LIBS
SET(PARAVIEW_PLUGINLIST_TXT "${ParaView_BINARY_DIR}/PluginList.txt")
FILE(WRI
Cool okay! Can you make a proper git patch against Master and send it to the
list? I will apply it and cherry pick it into the list.
On Fri, May 14, 2010 at 7:40 PM, Michael Jackson <
mike.jack...@bluequartz.net> wrote:
> There is another cmake variable "BUILD_PARAVIEW_PLUGINLIST" which needs to
There is another cmake variable "BUILD_PARAVIEW_PLUGINLIST" which
needs to be enabled in the *ParaViewImport.cmake file. I added SET
(BUILD_PARAVIEW_PLUGINLIST ON) to my
PVMXADataModelParaViewImport.cmake file (and with the other
corrections) I now can do a "make install" and have ParaView.
Ok,
So here is the problem. The PARAVIEW_EXTRA_EXTERNAL_MODULES is
called in the top level ParaView CMakeLists.txt file. AFTER that call
the line:
SET(PARAVIEW_PLUGINLIST "" CACHE INTERNAL "List of configured plugins"
FORCE)
is called which wipes out any plugins that were added by Extern
I've never used PARAVIEW_EXTRA_EXTERNAL_MODULES before but what I have
figured out was to set it to PVMXADataModel and place your git repository
adjacent to my ParaView source directory. When I do this I get these
configure errors.
CMake Error at
C:/Kitware/ParaView/PVMXADataModel/PVMXADataModelPa
535:[mjack...@shepard:Build]$ cmake ../
-- The C compiler identification is GNU
-- The CXX compiler identification is GNU
-- Checking whether C compiler has -isysroot
-- Checking whether C compiler has -isysroot - yes
-- Checking whether C compiler supports OSX deployment target flag
-- Checking w
Hi Mike,
Do you mind trying to print some messages then? When you
call ADD_PARAVIEW_PLUGIN the plugin gets Appended to PARAVIEW_PLUGINLIST and
also install rules should be created. Can you add this line say in
Applications\ParaView\CMakeLists.txt and then configure and see if you're
plugins get pr
This is still NOT working on the latest pull of the "release" branch
of ParaView. I can NOT simply do a "make install" on OS X and have my
custom plugins copied into the Application Bundle along with any other
plugins that are included with ParaView.
_
Thanks, I'll give that a try. "Make install" does fixup the bundle
correctly. I just left out my plugins.
So I have to do a cpack run in order to get a working installation
on my local machine? ie, an "installation" that is NOT in my build
directory? Seems odd.
--
Mike Jackson
On Apr 2
I would recommend:
cpack --config /Applications/ParaView/CPackParaViewConfig.cmake
-G DragNDrop
As per: http://paraview.org/Wiki/ParaView:Build_And_Install
If you do make install I believe it just runs all install rules and I don't
believe any of the fixup bundle routines get called.
On Mon, Ap
Just tried a 'Make install' and after installation (to the wrong
directory**) my custom plugins that are built as part of ParaView
(using PARAVIEW_EXTRA_EXTERNAL_MODULE). Is this going to be fixed
before the full release comes out?
**I have a CMAKE_INSTALL_PREFIX of /Users/Shared/Toolkits/
13 matches
Mail list logo
