Hi, This might be a heratic idea (in this context): But how "bad" is it really, to just build all components, put them in one place, and distribute them as a zip/tar-archive ? PYTHONPATH would need to be adjusted as needed - either in a place like .bashrc or in 3-line script that would then substitute the "python"-call. This is of course least feancy, but might be most effective - especially if it is only for a releatively small group of people. Cheers, Sebastian Haase On Nov 12, 2007 9:26 PM, Michael Hearne <mhearne@usgs.gov> wrote:
I'm creating a Python application that is internal to my organization, but will be installed on both Linux and Mac OS X machines. The application depends heavily on a number of "non-pure" modules (those that have C/C++/FORTRAN components), like numpy, scipy, gdal, etc.
What is the most "pythonic" way to bundle these types of modules inside my application?
I've investigated dist_utils and setuptools, and I don't see an easy way with those tools to include build instructions for packages built with autconf tools.
Is my only recourse to write a custom install script that calls the "configure;make;make install" from a shell?
--Mike
------------------------------------------------------ Michael Hearne mhearne@usgs.gov (303) 273-8620 USGS National Earthquake Information Center 1711 Illinois St. Golden CO 80401 Senior Software Engineer Synergetics, Inc. ------------------------------------------------------
_______________________________________________ SciPy-user mailing list SciPy-user@scipy.org http://projects.scipy.org/mailman/listinfo/scipy-user