mirror of
https://git.yoctoproject.org/poky
synced 2026-02-08 18:02:12 +01:00
b2b62c3608
The purpose of binconfig-disabled is to manipulate config scripts such that using them causes errors. But that only works when the modified config script really gets installed in the sysroot. That is not the case with the staging code in binconfig.bbclass. Only patched config files get staged. For that reason it seemed more appropriate to change binconfig-disabled instead of binconfig. The reason for the change was the observation that the swig recipe needs pcre-config installed on the host system. Staging pcre-config removes that host dependency. swig did not actually end up *using* the pcre-config from the host, because later during do_compile the patched configure.ac is used to re-generate configure. (From OE-Core rev: 822df6d23c9c24e131c38fda9f0012c47ad7af46) Signed-off-by: Patrick Ohly <patrick.ohly@intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
29 lines
756 B
Plaintext
29 lines
756 B
Plaintext
#
|
|
# Class to disable binconfig files instead of installing them
|
|
#
|
|
|
|
# The list of scripts which should be disabled.
|
|
BINCONFIG ?= ""
|
|
|
|
FILES_${PN}-dev += "${bindir}/*-config"
|
|
|
|
do_install_append () {
|
|
for x in ${BINCONFIG}; do
|
|
echo "#!/bin/sh" > ${D}$x
|
|
# Make the disabled script emit invalid parameters for those configure
|
|
# scripts which call it without checking the return code.
|
|
echo "echo '--should-not-have-used-$x'" > ${D}$x
|
|
echo "exit 1" >> ${D}$x
|
|
done
|
|
}
|
|
|
|
SYSROOT_PREPROCESS_FUNCS += "binconfig_disabled_sysroot_preprocess"
|
|
|
|
binconfig_disabled_sysroot_preprocess () {
|
|
for x in ${BINCONFIG}; do
|
|
configname=`basename $x`
|
|
install -d ${SYSROOT_DESTDIR}${bindir_crossscripts}
|
|
install ${D}$x ${SYSROOT_DESTDIR}${bindir_crossscripts}
|
|
done
|
|
}
|