Bug#859177: meson is unuseable for package cross compilation

On Sun, Jul 30, 2017 at 8:20 AM, Helmut Grohne wrote: > When debcrossgen.py is shipped in a "known" location (e.g. $PATH), I > can simply run it myself, modify its output, and pass "--cross-file > myfile" to dh_auto_configure. The later --cross-file takes precedence as > far

Bug#859177: meson is unuseable for package cross compilation

On Sun, Jul 30, 2017 at 02:07:50AM +0200, Michael Biebl wrote: > You mean as part of the Debian package build process? How would it make > a difference if debhelper calls an external binary or generate the file > directly? Can you please elaborate When debcrossgen.py is shipped in a "known"

Bug#859177: meson is unuseable for package cross compilation

Am 29.07.2017 um 23:29 schrieb Helmut Grohne: > On Sat, Jul 29, 2017 at 09:12:56AM +0200, Michael Biebl wrote: >> dependency on Python. But the debcrossgen.py code looks straightforward >> enough to be ported to perl. > > If it ends up being shipped in debhelper, I have a few questions. What >

Bug#859177: meson is unuseable for package cross compilation

On Sat, Jul 29, 2017 at 09:12:56AM +0200, Michael Biebl wrote: > Am 28.07.2017 um 22:06 schrieb Helmut Grohne: > > > 2. The debcrossgen.py script needs some place to live. When debhelper > > and meson are installed together, it needs to be in the filesystem. > > An easy approach to do so

Bug#859177: meson is unuseable for package cross compilation

On Sat, Jul 29, 2017 at 10:19 AM, Michael Biebl wrote: > Jussi, would this be hard to implement? Is there a good reason why > cross-compilation uses a separate file? There are many reasons. The fils contains a lot of options and passing all those in command line arguments

Bug#859177: meson is unuseable for package cross compilation

Am 29.07.2017 um 09:12 schrieb Michael Biebl: > My gut feeling is, that this functionality should be shipped in > debhelper directly, specifically in the meson build system class [1]. > debhelper is written in perl, and I don't think we want to add a > dependency on Python. But the

Bug#859177: meson is unuseable for package cross compilation

Am 28.07.2017 um 22:06 schrieb Helmut Grohne: > 2. The debcrossgen.py script needs some place to live. When debhelper > and meson are installed together, it needs to be in the filesystem. > An easy approach to do so is to put it into the meson binary > package. We should probably

Bug#859177: meson is unuseable for package cross compilation

Hi, I took a while to reply for a number of reasons: * There wasn't anything left to disagree with. * Testing debcrossgen.py was difficult due to #859173. In the mean time: * ninja-build is marked M-A:foreign (i.e. #859173 is fixed). * systemd can be built with meson. * The Debian systemd

Bug#859177: meson is unuseable for package cross compilation

On Sat, Apr 1, 2017 at 7:45 AM, Helmut Grohne wrote: >> That being said generating them live is probably a good approach, it >> seems to be mostly a question of mangling the output of >> dpkg-architecture. > > Yes. That's also essentially how the command line parameters for

Bug#859177: meson is unuseable for package cross compilation

On Sat, Apr 01, 2017 at 02:01:07AM +0300, Jussi Pakkanen wrote: > On Fri, Mar 31, 2017 at 4:31 PM, Helmut Grohne wrote: > > > The `makefile` buildsystem in `debhelper` even just sets > > `CC=${DEB_HOST_GNU_TYPE}-gcc`. The convention is: prefix host tools with > > the host's

Bug#859177: meson is unuseable for package cross compilation

On Fri, Mar 31, 2017 at 4:31 PM, Helmut Grohne wrote: > The `makefile` buildsystem in `debhelper` even just sets > `CC=${DEB_HOST_GNU_TYPE}-gcc`. The convention is: prefix host tools with the > host's GNU triplet. This does not work. For Meson, CC always means "the native

Bug#859177: meson is unuseable for package cross compilation

On Fri, Mar 31, 2017 at 02:41:55PM +0300, Jussi Pakkanen wrote: > Meson requires access to the "native" and "cross" compilers at the > same time. This is because it natively supports the use case where you > compile a program that is then used to generate source code that is > built. Examples

Bug#859177: meson is unuseable for package cross compilation

On Fri, Mar 31, 2017 at 10:37 AM, Helmut Grohne wrote: > When running `meson` on a project without supplying a `--cross-file`, > `meson` will pick default system compilers. Those compilers will produce > architecture-dependent output, which `meson` inherits. Thus `meson`'s >

Bug#859177: meson is unuseable for package cross compilation

Package: meson Severity: wishlist Control: block -1 by 859173 Mchael Biebl (Cced) asked me to look into cross compilation with `meson`. I already filed a related bug #859173 for the underlying `ninja-build`, but `meson` itself also poses problems for cross compilation. For starters, any package