diff options
| author |   Ross Burton <ross.burton@intel.com> | 2019-03-13 00:37:33 +0000 |
|---|---|---|
| committer |   Richard Purdie <richard.purdie@linuxfoundation.org> | 2020-01-27 16:38:54 +0000 |
| commit | 91b74ee03ada5d4517a5d8ef3895cc60f87780aa (patch) | |
| tree | 54bf18104f55bb7b161c007e46188b34d700015b /meta/recipes-devtools/xmlto | |
| parent | ed223207e0b6e25c18ce90d8e6fb1e5713d4cd0a (diff) | |
| download | openembedded-core-contrib-91b74ee03ada5d4517a5d8ef3895cc60f87780aa.tar.gz | |
meson.bbclass: warn if cross property defaults are used
The Meson idiom for checks which require running code on the target
(which isn't possible in cross compilation) is to use a cross property,
which the user can set in the cross file:
if cc_can_run
rres = cc.run(test_foo_code)
have_foo = rres.compiled() and rres.returncode() == 0
else
have_foo = meson.get_cross_property('have_foo', false)
endif
The default value may be overly conservative so we should review every
property and explicitly set them as apppropriate. oe-core 669ddaf added
a log message when the default value is used, so look for this message
and emit a warning that the user will see.
Signed-off-by: Ross Burton <ross.burton@intel.com>
Diffstat (limited to 'meta/recipes-devtools/xmlto')
0 files changed, 0 insertions, 0 deletions