[Paraview] Packaging branded apps on Windows

Hello, I've recently been forced... no, no, encouraged to try to build and package my branded PV app under Windows 7 64-bit, and I'm not experienced with building in a Windows environment. (I'm using Visual Studio 2008 Pro.) I think I have CVS ParaView built just fine. But, when I run CMake

Re: [Paraview] Packaging branded apps on Windows

The problem is due to the fact that install_qt_libs() incorrectly uses internal ParaView variable : PV_INSTALL_BIN_DIR. I'll fix that shortly. Until then feel free to set PV_INSTALL_BIN_DIR to bin. SET(PV_INSTALL_BIN_DIR bin) Utkarsh On Thu, Apr 1, 2010 at 1:30 PM, Eric E. Monson

Re: [Paraview] Packaging branded apps on Windows

Thanks a lot for the explanation, eventual fix and current workaround! Now I need to figure out why not all of my plugins will build on Windows... :( Talk to you later, -Eric On Apr 1, 2010, at 1:52 PM, Utkarsh Ayachit wrote: The problem is due to the fact that install_qt_libs() incorrectly

[Paraview] Branded plugin libraries packaging

Hey folks, A more general branded app packaging question: Is there any automatic mechanism in place to package plugin libraries with our branded apps? Right now I have a list of EXTRA_DEPENDENCIES in my build_paraview_client() section, and I build my plugins into my MainWindow class using the

Re: [Paraview] Branded plugin libraries packaging

A quick workaround is as follows: * Set the PV_INSTALL_PLUGIN_DIR before your ADD_PARAVIEW_PLUGIN calls. That will add install rules to install the plugin with component Runtime. Utkarsh On Thu, Apr 1, 2010 at 2:37 PM, Eric E. Monson emon...@cs.duke.edu wrote: Hey folks, A more general

Re: [Paraview] Packaging branded apps on Windows

Hey Utkarsh, It's all getting packed fine on Windows now, except for one library. I built the ParaView I'm building my branded app against with Python turned ON, but python26.dll isn't getting packaged in my NSIS installer. (All of the Python stuff seems to get packaged just fine on Ubuntu.)

Re: [Paraview] Packaging branded apps on Windows

When I build ParaView releases I have to inject extra install rules like this. Note that this is from ParaView 3.6 so the variable names have changed. INSTALL(FILES C:/Python25/python25.dll DESTINATION ${PV_EXE_INSTALL} PERMISSIONS OWNER_WRITE OWNER_READ OWNER_EXECUTE GROUP_READ

Re: [Paraview] Packaging branded apps on Windows

Also note that merely putting the Python.dll won't include all the python modules. You'll have to add custom rules to package whole of python. Unless your custom app relies on python I'd recommend compiling ParaView without python or asking the user to install Python using the installables

Re: [Paraview] Packaging branded apps on Windows

Also, depending on which compiler you are using, you may have to package python's msvcr90.dll dependency (and manifest!) Pat On Thu, Apr 1, 2010 at 5:23 PM, Utkarsh Ayachit utkarsh.ayac...@kitware.com wrote: Also note that merely putting the Python.dll won't include all the python modules.

Re: [Paraview] Packaging branded apps on Windows

Thanks, Pat. You know, sometimes I start to feel like these learning new skills and becoming competent at your job things aren't all they're cracked up to be. :) I appreciate all the tips. Take care. -Eric On Apr 1, 2010, at 5:34 PM, pat marion wrote: Also, depending on which compiler you

[Paraview] Contour filter

Hello. A short question: what is the algorithm that the contour filter uses? Is it Marching Cubes or it's something very different? Thank you, Panagiotis ___ Powered by www.kitware.com Visit other Kitware open-source projects at