|
Original |
Translation |
|
177
|
python setup.py build --build-base=blib --force
|
|
|
178
|
except that including the :command:`build` command on the command-line means that command will be run. Including a particular command in config files has no such implication; it only means that if the command is run, the options in the config file will apply. (Or if other commands that derive values from it are run, they will use the values in the config file.)
|
|
|
179
|
You can find out the complete list of options for any command using the :option:`--help` option, e.g.::
|
|
|
180
|
python setup.py build --help
|
|
|
181
|
|
182
|
|
|
|
183
|
See also the "Reference" section of the "Distributing Python Modules" manual.
|
|
|
184
|
Building Extensions: Tips and Tricks
|
|
|
185
|
Whenever possible, the Distutils try to use the configuration information made available by the Python interpreter used to run the :file:`setup.py` script. For example, the same compiler and linker flags used to compile Python will also be used for compiling extensions. Usually this will work well, but in complicated situations this might be inappropriate. This section discusses how to override the usual Distutils behaviour.
|
|
|
186
|
Tweaking compiler/linker flags
|
|