Package: debhelper Version: 12.5.4 Severity: important Hi,
I think it is time for a reboot of #919117, comment #20 if we want this for bullseye: """ 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 """ AFAICT, it would just be a question of doing: """ /usr/share/meson/debcrossgen -a"$DEB_BUILD_ARCH" -o"$DIR/meson-native-file.conf" /usr/share/meson/debcrossgen -a"$DEB_HOST_ARCH" -o"$DIR/meson-cross-file.conf" meson --native-file "$DIR/meson-native-file.conf" --cross-file "$DIR/meson-cross-file.conf" ... """ OR does it need a special case for cross-building vs. native? """ /usr/share/meson/debcrossgen -a"$DEB_BUILD_ARCH" -o"$DIR/meson-native-file.conf" if (is_cross_compiling()) { /usr/share/meson/debcrossgen -a"$DEB_HOST_ARCH" -o"$DIR/meson-cross-file.conf" meson --native-file "$DIR/meson-native-file.conf" --cross-file "$DIR/meson-cross-file.conf" ... } else { meson --native-file "$DIR/meson-native-file.conf" ... } """ @Helmut, @Jussi: * Do we agree on the above approach? * Do you see any issues with this approach? AFAIUI, the advantage is that we will use the same code path for native and cross-building plus the meson upstream prefer this approach over status-quo. Thanks, ~Niels
