Ühel kenal päeval, N, 04.05.2017 kell 18:48, kirjutas William Hubbs:
> if tc-is-cross-compiler; then
> _meson_create_cross_file || die "unable to write
> meson cross file"
> mesonargs+=(
> --cross-file "${T}"/meson.crossfile
> )
> fi
I'm not sure we should bother with such code in the eclass when the
_meson_create_cross_file doesn't do anything useful yet.
Of course once that functionality is added, we can see in this draft
how it'd be hooked up, but I don't see a reason to put it into the tree
with this near no-op.
And until this is no-op and not really functional when put into the
tree, we shouldn't encourage porting non-9999 versions to use meson
instead of an old build system (if still present), if the old one does
support more seamless cross-compilation via e.g crossdev. This is
important for things like udev probably, but less so for end-user
applications in the GNOME stack for example and many of those could
probably start using meson.eclass without the cross-file functionality
hooked in yet (or design a new iteration of gnome2.eclass on top of
it).
Mart
