On 01/09/2018 11:50 AM, Nirbheek Chauhan wrote:
Recently, we got meson added to OE-core as part of Yocto (thanks Alexander
Kanavin!).
Great to hear that! Thanks for your work, Alexander :)
I've built on the meta-oe meson recipe created by other people (tried to
credit them in the commit). My contribution was mostly polish and
testing, so that the recipe is of sufficient quality to be included in
oe-core - particularly that it doesn't break anything on the autobuilder
across architectures and configurations, and switching recipes from
autotools to meson does not come with feature regressions (e.g.
gobject-introspection, which is notoriously tricky for us).
- When --cross-file is specified, make meson not assume that env vars like
CC and CXX and similar point to native tools. Instead, just ignore them and
look for native tools in the normal way that meson does when these vars are
unspecified. We still may wan to inject CFLAGS, LDFLAGS, etc into the build
because people may mess with them interactively during development.
Would it be possible to tell Yocto to not set those vars when building
a recipe that uses meson?
FWIW, I fully agree. Environment variables are an obsolete technique
from old Unices, and a notorious source of frustration - because it's
very easy for software to quietly modify them behind the human's back,
as opposed to setting things via config files and command line switches,
which are both a lot more controlled and disciplined. Ideally, I want to
reduce or eliminate the use of env vars altogether in Yocto (long way to
go there, I know).
Alex
--
_______________________________________________
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core
