diff options
author | Richard Purdie <richard.purdie@linuxfoundation.org> | 2022-07-21 14:47:36 +0100 |
---|---|---|
committer | Richard Purdie <richard.purdie@linuxfoundation.org> | 2022-07-23 12:10:32 +0100 |
commit | 10028104ff53ec7b338019e685f43ecd2c4625e0 (patch) | |
tree | ba4d55d216ac24c23e98232574eb150b2db0fa1e | |
parent | ec54a67cfc40eaf8b7ec208de6682ccc9a87a14a (diff) | |
download | openembedded-core-contrib-10028104ff53ec7b338019e685f43ecd2c4625e0.tar.gz |
autotools: Drop relative configure path workaround
Calling configure with a relative path to the build directory was a nice
workaround to remove hardcoded paths from files. We have proper prefix
remapping code now and these relative paths escape that modern code.
Drop the obsolete approach and allow the prefix remapping to handle things.
This ensures the contents of debug source directories is correct as the build
directory from the tarball name may not match the on target debug directory.
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
-rw-r--r-- | meta/classes/autotools.bbclass | 4 |
1 files changed, 1 insertions, 3 deletions
diff --git a/meta/classes/autotools.bbclass b/meta/classes/autotools.bbclass index 4ab2460990..d56d820f66 100644 --- a/meta/classes/autotools.bbclass +++ b/meta/classes/autotools.bbclass @@ -86,9 +86,7 @@ CONFIGURE_SCRIPT ?= "${AUTOTOOLS_SCRIPT_PATH}/configure" AUTOTOOLS_AUXDIR ?= "${AUTOTOOLS_SCRIPT_PATH}" oe_runconf () { - # Use relative path to avoid buildpaths in files - cfgscript_name="`basename ${CONFIGURE_SCRIPT}`" - cfgscript=`python3 -c "import os; print(os.path.relpath(os.path.dirname('${CONFIGURE_SCRIPT}'), '.'))"`/$cfgscript_name + cfgscript=${CONFIGURE_SCRIPT} if [ -x "$cfgscript" ] ; then bbnote "Running $cfgscript ${CONFIGUREOPTS} ${EXTRA_OECONF} $@" if ! CONFIG_SHELL=${CONFIG_SHELL-/bin/bash} ${CACHED_CONFIGUREVARS} $cfgscript ${CONFIGUREOPTS} ${EXTRA_OECONF} "$@"; then |