[Paraview] zlib python module in paraview superbuild

[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 specifies a configure command in ExternalProject_Add.

I was able to get it to compile by making the following changes:

 * Uncomment out the various python_*_COMMAND settings
 * Set the ExternalProject_Add call to use those commands
 * Move the include(External_zlib) to just above if(NOT APPLE) in
CMakeLists.txt in the SuperBuild
 * add these lines to python_configure_step.cmake.in

  set(ENV{LD_LIBRARY_PATH} "@CMAKE_CURRENT_BINARY_DIR@/python-build/lib")
  set(ENV{CXX} "@CMAKE_CXX_COMPILER@")
  set(ENV{CPPFLAGS} "-I at ZLIB_INCLUDE_DIR@")
  set(ENV{LDFLAGS} "-L at ZLIB_LIBRARY_DIR@")

Now I have a nice zlib module.  :)

I've committed these changes to my gitorious repo, if you're
interested -- it's a fork of the jpocom-paraview repo under Jorge's
account (jpocom).  It probably has a few mistakes or CMake idioms I
have done incorrectly, but I've also added several other modules
(including yt) to it.  I'm testing a full build at the moment, but it
will take a little while to see the results.

Thanks for all your help!

-Matt

On Tue, Aug 30, 2011 at 11:37 AM, David Partyka
<david.partyka at kitware.com> wrote:
> 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 Tue, Aug 30, 2011 at 11:25 AM, Matthew Turk <matthewturk at gmail.com>
> wrote:
>>
>> 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
>> bz2                dbm                dl
>> gdbm               imageop            readline
>> sunaudiodev        zlib
>> To find the necessary bits, look in setup.py in detect_modules() for
>> the module's name.
>>
>> After digging through detect_modules and the CMake files I think the
>> issue is that detect_modules looks at CPPFLAGS.  I've tried modifying
>> External_Python.cmake with
>>
>> set(ENV(CPPFLAGS) -I at ZLIB_INCLUDE_DIR@)
>>
>> but this did not seem to be propagated to the environment configure
>> read from, as config.log indicated that CPPFLAGS was set to the empty
>> string.
>>
>> Any suggestions how to correctly thread this through?
>>
>> Thanks,
>>
>> Matt
>>
>> On Tue, Aug 30, 2011 at 10:01 AM, David Partyka
>> <david.partyka at kitware.com> wrote:
>> > 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 <matthewturk at gmail.com>
>> > wrote:
>> >>
>> >> 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 components.
>> >>
>> >> Thanks for any ideas,
>> >>
>> >> Matt
>> >> _______________________________________________
>> >> 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
>> >
>> >
>
>