|
Original |
Translation |
|
107
|
The installation base is defined by the :option:`--prefix` option; the :option:`--exec-prefix` option is not supported under Windows. Files are installed as follows:
|
|
|
108
|
:file:`{prefix}\\Scripts`
|
|
|
109
|
|
|
|
110
|
|
|
|
111
|
|
112
|
You probably noticed the column of "override options" in the tables describing the alternate installation schemes above. Those options are how you define a custom installation scheme. These override options can be relative, absolute, or explicitly defined in terms of one of the installation base directories. (There are two installation base directories, and they are normally the same--- they only differ when you use the Unix "prefix scheme" and supply different :option:`--prefix` and :option:`--exec-prefix` options.)
|
|
|
113
|
For example, say you're installing a module distribution to your home directory under Unix---but you want scripts to go in :file:`~/scripts` rather than :file:`~/bin`. As you might expect, you can override this directory with the :option:`--install-scripts` option; in this case, it makes most sense to supply a relative path, which will be interpreted relative to the installation base directory (your home directory, in this case)::
|
|
|
114
|
python setup.py install --home=~ --install-scripts=scripts
|
|
|
115
|
Another Unix example: suppose your Python installation was built and installed with a prefix of :file:`/usr/local/python`, so under a standard installation scripts will wind up in :file:`/usr/local/python/bin`. If you want them in :file:`/usr/local/bin` instead, you would supply this absolute directory for the :option:`--install-scripts` option::
|
|
|
116
|
python setup.py install --install-scripts=/usr/local/bin
|
|