[Paraview] Packaging branded apps on Windows

[Utkarsh Ayachit]

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 provided at python.org

Utkarsh

On Thu, Apr 1, 2010 at 5:20 PM, Dave Partyka <dave.partyka at kitware.com> wrote:
> 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
> GROUP_EXECUTE WORLD_READ
>     COMPONENT Runtime)
> On Thu, Apr 1, 2010 at 5:13 PM, Eric E. Monson <emonson at cs.duke.edu> wrote:
>>
>> 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.)
>>
>> Is there something I should add to my CMakeLists.txt file to make this
>> happen properly?
>>
>> Thanks a lot -- getting closer... :)
>> -Eric
>>
>> _______________________________________________
>> 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
>
>