1. Tarek Ziadé
  2. distribute
Issue #185 new

setup.py develop command ignores the build_ext section of setup.cfg

jonozzz
created an issue

I'm passing the include-dirs param through setup.cfg. So I created a new setup.cfg file in the egg root directory: {{{

!python

$ cat setup.cfg [build_ext] include-dirs = /usr/include/openssl

[egg_info] tag_build = tag_date = 0 tag_svn_revision = 0

}}}

The special include directory is vital to build_ext part of the egg, and develop prevents build_ext from reading it from setup.cfg. Perhaps it changes the cwd prior to building the egg ? {{{

!python

$ PYTHONPATH=/home/user/sandbox/eggs/distribute-0.6.14-py2.6.egg python26 setup.py -v develop -mxN -d /tmp running develop install_dir /tmp Checking .pth file support in /tmp /usr/bin/python26 -E -c pass running egg_info writing M2Crypto.egg-info/PKG-INFO writing top-level names to M2Crypto.egg-info/top_level.txt writing dependency_links to M2Crypto.egg-info/dependency_links.txt reading manifest file 'M2Crypto.egg-info/SOURCES.txt' writing manifest file 'M2Crypto.egg-info/SOURCES.txt' running build_ext building 'M2Crypto.__m2crypto' extension swigging SWIG/_m2crypto.i to SWIG/_m2crypto_wrap.c swig -python -I/usr/include/python2.6 -I/usr/include -includeall -o SWIG/_m2crypto_wrap.c SWIG/_m2crypto.i /usr/include/openssl/opensslconf.h:13: Error: Unable to find 'opensslconf-i386.h' error: command 'swig' failed with exit status 1

}}}

If I run the build_ext command in the same directory everything is fine, as you can see the extra include dir is passed to swig as expected: {{{

!python

$ PYTHONPATH=/home/user/sandbox/eggs/distribute-0.6.14-py2.6.egg python26 setup.py -v build_ext running build_ext building 'M2Crypto.__m2crypto' extension swigging SWIG/_m2crypto.i to SWIG/_m2crypto_wrap.c swig -python -I/usr/include/openssl -I/usr/include/python2.6 -I/usr/include -includeall -o SWIG/_m2crypto_wrap.c SWIG/_m2crypto.i [..snip..] }}}

Comments (0)

  1. Log in to comment