David Gibson dd695d6afb pylibfdt: Correctly set build output directory ... Our Makefile currently passes PYLIBFDT_objdir into setup.py in an attempt to set the correct place to put the Python extension module output. But that gets passed in the 'package_dir' map in distutils. But that's basically not what package_dir controls. What actually makes us find the module in the right place is the --inplace passed to setup.py (causing the module to go into the current directory), and the following 'mv' in the Makefile to move it into the right final location. We can simplify setup.py by dropping the useless objdir stuff, and get the module put in the right place straight way by instead using the --build-lib setup.py option. Signed-off-by: David Gibson <david@gibson.dropbear.id.au> Reviewed-by: Simon Glass <sjg@chromium.org>		2018-09-25 10:29:35 +10:00
..
.gitignore	Add an initial Python library for libfdt	2017-03-21 16:21:58 +11:00
libfdt.i	pylibfdt: Add a means to add and delete notes	2018-09-13 10:16:34 +10:00
Makefile.pylibfdt	pylibfdt: Correctly set build output directory	2018-09-25 10:29:35 +10:00
setup.py	pylibfdt: Correctly set build output directory	2018-09-25 10:29:35 +10:00