Hi David, On 6 April 2017 at 23:46, David Gibson <david@xxxxxxxxxxxxxxxxxxxxx> wrote: > On Wed, Apr 05, 2017 at 10:01:40AM -0600, Simon Glass wrote: >> 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@xxxxxxxxxxxx> > > I'm not sure quite how or why, but this patch has the side-effect of > stopping the Python tests from running with "make check". Yes I did see that at one point but unfortunately didn't go back and investigate. There's a dependency problem since tests don't currently build the module. Will send a new version. Regards, Simon -- To unsubscribe from this list: send the line "unsubscribe devicetree-compiler" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
