diff options
author | Jack Mitchell <ml@embed.me.uk> | 2020-12-08 16:03:14 +0000 |
---|---|---|
committer | Richard Purdie <richard.purdie@linuxfoundation.org> | 2021-02-03 14:13:53 +0000 |
commit | df29f54c265ff6da757abb4463e82c447889dfe8 (patch) | |
tree | 451d3dd45dd8a7100b3ffa95043cf7be4248e964 /meta/classes/module-base.bbclass | |
parent | e837c1790be6af1ec9bcab49de7b3be78da8a1b4 (diff) | |
download | poky-df29f54c265ff6da757abb4463e82c447889dfe8.tar.gz |
distutils3: allow setup.py to be run from a different directory to ${S}
Sometimes setup.py can be buried deep in a source tree. This has
traditionally been solved with setting S to the subdirectory in
the source. However with the new pseudo changes, some python modules
make changes to files beneath ${S}, for example:
S = "${WORKDIR}/git/python/pythonmodule"
then in setup.py it works with source code in a relative fashion, such
as:
../../src
This causes pseudo to abort as it isn't tracking the paths. Therefore
implement the variable DISTUTILS_SETUP_PATH so that recipes can use:
S = "${WORKDIR}/git"
DISTUTILS_SETUP_PATH = "${S}/python/pythonmodule"
inherit distutils3
This allows the full source tree to be monitored, while distutils
can run setup.py from a location other than ${S}.
(From OE-Core rev: ab15ec860a936c527484435f141ced300b9cb9dc)
Signed-off-by: Jack Mitchell <ml@embed.me.uk>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
(cherry picked from commit ddcc349cede0c4fe1909df1ded7b0a7c509cd758)
Signed-off-by: Steve Sakoman <steve@sakoman.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'meta/classes/module-base.bbclass')
0 files changed, 0 insertions, 0 deletions