On Sun, 13 Jan 2019 01:13:18 +0200 Jussi Pakkanen <jpakk...@gmail.com> wrote: > 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? > [...]
Hi, I am happy to work with you to update debhelper in bullseye to use a --native-file instead of passing ENV variables to meson provided we use the same script for generating the cross file and the native file. >From my perspective, it would give a standardized interface for supporting native vs. cross builds that is well-tested. Plus we would notice many regressions already on native builds rather than cross-builds. To ensure the latter, I am also very happy to reset the ENV to ensure only particular variables are passed on to meson (compare PATH, LC_ALL vs. CC, CFLAGS, etc.). The only caveat here I have is that debcrossgen should be updated to support the necessary bits for native builds in buster (#919065 might be relevant here beyond this bug). Otherwise, debhelper cannot rely on its for backports. What do you think of this idea? :) Thanks, ~Niels
