one of the things I like most about distutils is the compositional
approach to the build system, i.e. commands such as 'bdist' being
defined independently of 'build', so as soon as I have a working 'build'
command, 'bdist' (and its variants) will work out-of-the-box most
of the time.
However, I'v now run into an issue with this very approach, and I
wonder how to deal with that:
As the 'build_ext' command shipped with distutils isn't powerful
enough for my extensions, I'v written one myself. It's basically
a wrapper around a call to 'make -C ...'. That is accompagnied
by a 'config' command, doing, what else, a 'configure' call...
I'v added various options to the config command to be able to
enable/disable the various extensions that can be supported.
But there doesn't seem to be a way to call 'python setup.py bdist_rpm'
(say) and somehow pass options that are really meant for the config
command, or is there ?
That means I have to write my 'config' command such that the default
is the desired configuration for the rpm. Right ?
Any tips are highly appreciated,