Fix bug #233253: the --define and --undef options didn't work, whether

specified on the command-line or in setup.cfg.  The option processing
   leaves them as strings, but they're supposed to be lists.
This commit is contained in:
Andrew M. Kuchling 2001-03-17 20:15:41 +00:00
parent 898f099dc6
commit 7620bbdcbf
1 changed files with 15 additions and 0 deletions

View File

@ -177,6 +177,21 @@ class build_ext (Command):
# building python standard extensions
self.library_dirs.append('.')
# The argument parsing will result in self.define being a string, but
# it has to be a list of 2-tuples. All the preprocessor symbols
# specified by the 'define' option will be set to '1'. Multiple
# symbols can be separated with commas.
if self.define:
defines = string.split(self.define, ',')
self.define = map(lambda symbol: (symbol, '1'), defines)
# The option for macros to undefine is also a string from the
# option parsing, but has to be a list. Multiple symbols can also
# be separated with commas here.
if self.undef:
self.undef = string.split(self.undef, ',')
# finalize_options ()