On Sun, Jan 13, 2019 at 12:42 AM Helmut Grohne <hel...@subdivi.de> wrote:

> I think this discrepancy is a design bug in Meson. Meson should either
> use environment variables or not. For native compilation, you can simply
> use a native file. Artificially handling things differently just makes
> cross compilation unnecessarily hard.

Using only native and cross files is exactly the thing that we want to
do and are working towards. Sadly it is likely that we will never be
able to get rid of the envvar support. For all the gory details see
for example:

https://github.com/mesonbuild/meson/issues/4664

> That's how debhelper runs it. Yes, your updated debcrossgen fully
> resolves the issue at hand. While the behaviour change persists,
> practically all Debian packages run meson through debhelper and will
> therefore work. Can we get that into unstable soon?

I updated the packaging to have the new debcrossgen script.
Unfortunately the repository is currently broken and pbuilder can not
install all the dependency packages needed to run the test suite so
binary packages can not be built. I have uploaded the packaging to
mentors, feel free to upload it to unstable as you see fit:

https://mentors.debian.net/package/meson

Reply via email to