summaryrefslogtreecommitdiffstats
path: root/meta/classes/binconfig-disabled.bbclass
Commit message (Collapse)AuthorAgeFilesLines
* binconfig-disabled.bbclass: fix echo commandRobert Yang2015-02-081-1/+1
| | | | | | | | | | | | | | | The ">" should be ">>". We had got something like the following in pcap-config: echo '--should-not-have-used-/usr/bin/pcap-config' exit 1 (Lacks of #!/bin/sh) (From OE-Core rev: d4adf9ac1b8318d4eb3f1c8dd82bbf04c6908eb5) Signed-off-by: Robert Yang <liezhi.yang@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* binconfig-disabled: install config scripts in sysrootPatrick Ohly2015-01-291-0/+10
| | | | | | | | | | | | | | | | | | | | | | 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>
* binconfig-disabled: try harder to prevent usage of config scriptsPatrick Ohly2015-01-291-0/+3
| | | | | | | | | | | | | | | | | | | Returning a non-zero exit code is not enough to cause errors when configure scripts call the patched config scripts: for example, swig's configure script uses PCRE_LIBS=`$PCRE_CONFIG --libs` and does not abort on errors. Using empty output may then succeed, for example when the required library is available indirectly. Returning some nonsense command line arguments covers such cases, because using them will definitely lead to errors during compilation. The faked arguments were chosen such that these errors can be linked back to the root cause. (From OE-Core rev: d1ff61a16a3fcfdd7cf882bc89fb1d164cb1603a) 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>
* binconfig-disabled: add a default value and comment for BINCONFIGRoss Burton2014-07-081-0/+3
| | | | | | | | | | To avoid syntax errors when inheriting this class without setting BINCONFIG, add a default value and a comment. (From OE-Core rev: a7e808e9a0ff45f14235b2de3c53d89d98fde714) Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* binconfig-disabled: Add class and useRichard Purdie2014-06-161-0/+12
This adds a binconfig-disabled class which can be used by recipes where a -config file is installed but we wish to disable it and just rely on the .pc files instead. Rather than simply deleting it, we make the script "exit 1" so that it can be found in PATH and raise a build error rather than something silently falling back to the build system for example. Rather than randomly finding -config files, this adds in the specification of a list of binconfig scripts which is more deterministic and maintainable moving forward. This patch converts various users in OE-Core to use this, a world build of OE-Core tests out ok with this change. There will likely be issues in other layers however, hence this being a RFT. (From OE-Core rev: 5870bd272b0b077d0826fb900b251884c1c05061) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>