[Paraview] zlib python module in paraview superbuild

2011-08-16 Thread Matthew Turk
Hi there, Has anyone successfully gotten the zlib module in the paraview superbuild to build and install? On my machine, it is failing on finding zlib.h; I am not sure how to interface with the Python setup.py patch to suggest additional directories (like ZLIB_INSTALL) to search for the necessary

Re: [Paraview] zlib python module in paraview superbuild

2011-08-30 Thread David Partyka
I have but of course I wrote it ;-). What platform/compiler are you using? Can you send the error messages? On Tue, Aug 16, 2011 at 6:17 PM, Matthew Turk wrote: > Hi there, > > Has anyone successfully gotten the zlib module in the paraview > superbuild to build and install? On my machine, it is

Re: [Paraview] zlib python module in paraview superbuild

2011-08-30 Thread Matthew Turk
Hi David, The error message reported by the Python build itself reports that it didn't find the necessary bits to build zlib: Python build finished, but the necessary bits to build these modules were not found: _bsddb _sqlite3 bsddb185 bz2dbmd

Re: [Paraview] zlib python module in paraview superbuild

2011-08-30 Thread David Partyka
Ah yes, The configure step of python has to be run from a script. See External_NUMPY.cmake for example where each of the steps (configure,make,install) are run as separate scripts that are configured with configure_file. The files for the most part just set environment variables for the build. On

Re: [Paraview] zlib python module in paraview superbuild

2011-08-30 Thread Matthew Turk
Hi David, Sorry, I should have mentioned, setting the environment variables in python_configure_step.cmake.in also had no effect -- but the pointer helped me figure out why! The External_Python.cmake file that I started from has the set(python_CONFIGURE_COMMAND ...) call commented out and specifi

Re: [Paraview] zlib python module in paraview superbuild

2011-08-30 Thread David Partyka
Cool, thank you! I will take a look. On Tue, Aug 30, 2011 at 11:58 AM, Matthew Turk wrote: > Hi David, > > Sorry, I should have mentioned, setting the environment variables in > python_configure_step.cmake.in also had no effect -- but the pointer > helped me figure out why! The External_Python.c