Hey Dave,
When building (and packaging) branded apps, is there any advantage to or
difference between building against the development tree that's generated
through this process vs a "non-installed" local ParaView build?
So far (on OS X 10.6.2) I've run into a couple problems building against the
installed development tree {Oh, caveat, this is the CVS from 2010-03-03 because
I had build errors when trying yesterday evening's code...}:
1. pq3DWidgetImplementation.cxx.in and pq3DWidgetImplementation.h.in are
missing from [installRoot]/include/paraview-3.7/Qt/Components/
2. The library paths in the applications installed in [installRoot]/bin/ aren't
correct, so when I try to build a branded app against this tree, the first
thing I run into is:
dyld: Library not loaded: libvtkCommon.pv3.7.dylib
Referenced from: /usr/local/ParaView/bin/kwProcessXML
Reason: image not found
If I run "otool -L" on kwProcessXML (or on any app in that directory), the
library paths don't point to the correct lib directories:
emo2:/usr/local/ParaView/bin> otool -L kwProcessXML
kwProcessXML:
libvtkCommon.pv3.7.dylib (compatibility version 0.0.0, current version
0.0.0)
libvtksys.pv3.7.dylib (compatibility version 0.0.0, current version
0.0.0)
/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current
version 123.0.0)
/usr/lib/libstdc++.6.dylib (compatibility version 7.0.0, current
version 7.9.0)
Thanks for all the good work,
-Eric
------------------------------------------------------
Eric E Monson
Duke Visualization Technology Group
On Mar 4, 2010, at 4:42 PM, Dave Partyka wrote:
> Greetings Everyone,
>
> I have recently commited a fair amount of changes to ParaView that lets a
> developer create a functional development tree that could be distributed. The
> development tree includes all the necessary headers, libraries, CMake files
> and executable tools one would need for developing ParaView branded
> applications and Plugins without building your own ParaView.
>
> In order to create this tree you simply need to enable
> PARAVIEW_INSTALL_DEVELOPMENT when configuring ParaView with CMake. Afterwards
> if you do a make install (linux/mac) or build the INSTALL target (windows), a
> development tree will be installed at CMAKE_INSTALL_PREFIX. If you wish to
> distribute a development package, running CPack with
> PARAVIEW_INSTALL_DEVELOPMENT turned on will also include the development tree.
>
> For Example:
>
> cpack -G NSIS --config
> C:\Kitware\ParaView3\bin\Applications\ParaView\CPackParaViewConfig.cmake -C
> Release
>
> Just about all of the bugs related to the development install feature have
> been fixed. If anyone has any issues with them please feel free to report a
> bug.
>
> Thanks!
> _______________________________________________
> Paraview-developers mailing list
> [email protected]
> http://public.kitware.com/mailman/listinfo/paraview-developers
_______________________________________________
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
