diff options
| author | Simon Glass <sjg@chromium.org> | 2017-04-07 15:51:32 -0600 |
|---|---|---|
| committer | David Gibson <david@gibson.dropbear.id.au> | 2017-04-08 11:54:07 +1000 |
| commit | 90db6d9989ca09ed3c32fbdc646d284ebf9fe1cf (patch) | |
| tree | 2cc5adc4e3d607d2561ca46991ec9f8ca6b471ae /Makefile | |
| parent | e20d9658cd8f1cf2c03e843678cc9e89107e87ad (diff) | |
| download | dtc-90db6d9989ca09ed3c32fbdc646d284ebf9fe1cf.zip dtc-90db6d9989ca09ed3c32fbdc646d284ebf9fe1cf.tar.gz dtc-90db6d9989ca09ed3c32fbdc646d284ebf9fe1cf.tar.bz2 | |
pylibfdt: Allow setup.py to operate stand-alone
At present we require that setup.py is executed from the Makefile, which
sets up various important things like the list of files to build and the
version number.
However many installation systems expect to be able to change to the
directory containing setup.py and run it. This allows them to support (for
example) building/installing for multiple Python versions, varying
installation paths, particular C flags, etc.
The problem in implementing this is that we don't want to duplicate the
information in the Makefile. A common solution (so I am told) is to parse
the Makefile to obtain the required information.
Update the setup.py script to read a few Makefiles when it does not see
the required information in its environment. This allows installation
using:
./pylibfdt/setup.py install
Signed-off-by: Simon Glass <sjg@chromium.org>
Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
Diffstat (limited to 'Makefile')
| -rw-r--r-- | Makefile | 1 |
1 files changed, 1 insertions, 0 deletions
@@ -267,6 +267,7 @@ TESTS_BIN += convert-dtsv0 TESTS_BIN += fdtput TESTS_BIN += fdtget TESTS_BIN += fdtdump +TESTS_PYLIBFDT += maybe_pylibfdt include tests/Makefile.tests |