[Paraview] Packaging ParaView

[Reuter, Michael A.]

I tried the superbuild route and started simple by making only two
modifications: Changing the ParaView git tag to v3.98.1 and setting the
PARAVIEW_BUILD_QT_GUI to ON but not enabling Qt. OSX worked like charm and
the resulting package works. When I went to Windows, the package wouldn't
go through the install step. I chased my tail for a bit and finally found
the problem. We have to build PV without Python due an incompatibility
between PV and our software (haven't had time to debug yet). However, the
Windows install step was choking on pvbatch and pvpython not being
present. I found that the Projects/win32/paraview.bundle.cmake file wasn't
properly trapped for that. Once I fixed that, everything went smoothly and
the package works. I'm attaching the patch.

Cheers,
M


On 4/16/13 9:06 AM, "Utkarsh Ayachit" <utkarsh.ayachit at kitware.com> wrote:

>Michael,
>
>Superbuild can indeed be customized to suit your needs. However,
>you'll have to start with a new fork of the repo. As the wiki
>explains, http://paraview.org/Wiki/ParaView/Superbuild, the Superbuild
>simply builds all needed projects and then builds paraview (Look at
>paraview.cmake). It also include rules for each of OS to create a
>bundle/package (paraview.bundle.cmake). Create a new fork with just
>paraview.cmake, paraview.build.cmake, paraview.bundle.common.cmake
>(and the fixup scripts for OSX) and then customize these files as per
>your needs i.e. tell ParaView to use Qt/HDF from your build, adjust
>paraview.bundle.cmake to package extra dependencies, among others.
>
>You can edit the top-level CMakeLists.txt to remove the include(..)
>calls to dependencies you are no longer building as part of the
>superbuild (or add new ones).
>
>Hope that helps. Feel free to holler if you run into issues or need
>further explanations.
>
>Utkarsh
>
>
>On Mon, Apr 15, 2013 at 3:18 PM, Reuter, Michael A. <reuterma at ornl.gov>
>wrote:
>> Hi,
>>
>> I'm trying to package ParaView with our build options, but it looks
>>like the CPackParaViewConfig.cmake file is no longer available in
>>3.98.1, unless I missed a CMake variable. I've been looking at two ways
>>to handle this: superbuild and rebranding. I really don't need to
>>rebrand ParaView, as we aren't wrapping in any new functionality. So, I
>>was thinking of going with the superbuild. Can the superbuild be made to
>>only package ParaView provided libraries and plugins? Our analysis
>>package which uses ParaView functionality already provides many of the
>>same dependencies (Qt, HDF) and we build ParaView against these.
>>Therefore, we don't need to duplicate them in the installation package.
>>
>> Thanks,
>> M
>>
>> Dr. Michael Reuter
>> Data Analysis and Visualization Group
>> Neutron Data Analysis and Visualization Division
>> Oak Ridge National Laboratory
>>
>> Office: 1-865-241-7216
>> Fax: 1-865-574-6080
>> Email: reuterma at ornl.gov
>> _______________________________________________
>> 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

-------------- next part --------------
A non-text attachment was scrubbed...
Name: win32-pv-bundle.patch
Type: application/octet-stream
Size: 918 bytes
Desc: win32-pv-bundle.patch
URL: <http://www.paraview.org/pipermail/paraview/attachments/20130422/5ad6f77c/attachment.obj>