aboutsummaryrefslogtreecommitdiffstats
path: root/tools/python/install-wrap
Commit message (Collapse)AuthorAgeFilesLines
* tools: simplify PYTHON_PATH computation (and fixes for NetBSD)Keir Fraser2009-12-091-18/+34
| | | | | | | | Doesn't work when build-time python path differs from install-time. Do we care about this given tools should be packaged/built for the specific run-time distro? Signed-off-by: Christoph Egger <Christoph.Egger@amd.com>
* Have `make install' write the Python version number in the #!Keir Fraser2008-06-111-0/+44
The Xen tools contain a number of Python extensions written in C. The C API to Python, used by these extensions, is not stable from one version of Python to the next. Our build system uses whatever version of Python is the default on the build system at that time to build these extensions. However, the actual scripts such as `xm' use #!/usr/bin/env python which uses whichever version of Python is the default on the deployment system at the time of invocation. If for any reason these two versions of Python are not the same (eg, because the system is built on one computer and executed on another, or because the system's gains a more recent Python installation alongside the original which changes the previous default), warnings and failures occur. In this patch I arrange for Python scripts to be installed via a special wrapper around `install', which determines the build-time Python version and path and then writes that into the #! line at the point of `make install' (or `make dist'). (It can also be overridden by setting PYTHON_PATH.) Signed-off-by: Ian Jackson <ian.jackson@eu.citrix.com>