[Paraview] Mac branded packaging

[Utkarsh Ayachit]

Eric,

You are correct, there's no way for pvpython/pvbatch to know about
your plugins currently, nor is there a way to create "custom pvbatch
or pvpython" executables. You will have to do an explicit LoadPlugin()
in your python scripts.

Utkarsh

On Tue, May 11, 2010 at 2:46 PM, Eric E. Monson <emonson at cs.duke.edu> wrote:
> Hey again,
>
> Okay, so I was able to solve #1: There was a cmake variable that wasn't set (i.e. wasn't carried over from the ParaView build) so the bundle-fixing script wasn't looking in the right spot for the Python libraries.
>
> If someone could still help me with the conceptual question in #2 I'd really appreciate it. I would like my users to be able to generate batch animations with pvpython. In my branded app I hard-code my custom plugins into my main window class, and the python shell within PV automatically "knows about" my custom filters, but I'm not clear on what it takes to get pvpython to know about those custom filters, too.
>
> So, sorry this sounds so ignorant, but is it possible to build a version of pvpython that will already have my custom filters built in? Or, will I always have to do an explicit LoadPlugin(), in which case I can just use the standard procedure for packaging the server executables, but also include my custom plugin libraries along with the standard PV ones.
>
> Thanks,
> -Eric
>
>
> On May 10, 2010, at 10:09 AM, Eric E. Monson wrote:
>
>> Hey all,
>>
>> Packaging of my branded app is working well on Windows and Linux, but I'm trying once again to see if I can get packaging to work on OS X. I'm getting closer (after making sure my scripts were almost a verbatim copy of the PV ones), but I'm confused about a few things -- maybe someone can help get me further and/or clarify. The main difficulty is that I'm trying to not only get my app to run, but give my users access to the PV Python functionality (python shell and "command line tools").
>>
>> 1. When I generate an executable app bundle (either with CPack or with "make install"), the app itself runs fine on a "clean" system, but the Python shell can't find some of the libraries. It looks like a lot of the python-required libraries are not being copied to .app/Contents/Libraries. How can I tell the system that I need all of that stuff bundled, too, when I build a DragNDrop?
>>
>> 2. If I want to distribute a version of the "command line tools" for making batch animations that will recognize all of the plugins I've hard-coded into my branded app, I've been assuming I need to package these binaries (pvpython, etc) based on my branded app build -- Is this true, or do I just need to somehow add my custom plugin libraries to a standard package of the paraview servers executables?
>>
>> The problem I have with (2) is that even when I build against a PV built with VTK_USE_RPATH: OFF and my branded app with CMAKE_SKIP_RPATH: ON, I end up with my executables and libraries depending on (the absolute path of) my local Qt installation, so they won't run on other machines. (And, I can't get my branded app to build against a version of PV which has PARAVIEW_BUILD_QT_GUI: OFF.)
>>
>> Any help would be greatly appreciated!
>>
>> Thanks,
>> -Eric
>>
>> ------------------------------------------------------
>> Eric E Monson
>> Duke Visualization Technology Group
>>
>>
>> _______________________________________________
>> 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
>
> _______________________________________________
> 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
>