FS#62962 - Meson package should include the provided cross files

Attached to Project: Arch Linux
Opened by Eric Engestrom (1ace) - Friday, 21 June 2019, 11:52 GMT
Last edited by Eli Schwartz (eschwartz) - Friday, 21 June 2019, 12:20 GMT
Task Type Feature Request
Category Packages: Extra
Status Closed
Assigned To No-one
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Meson provides a number of cross files in the `cross/` folder, which should be part of the package so that users can use them.

The recommended location for them is in `/usr/share/meson/cross/`, as that will allow them to be selected by filename instead of having to always provide the full path.

See also: https://mesonbuild.com/Cross-compilation.html
This task depends upon

Closed by  Eli Schwartz (eschwartz)
Friday, 21 June 2019, 12:20 GMT
Reason for closing:  Not a bug
Additional comments about closing:  Apparently upstream doesn't consider this wise to install by default, and I completely understand where they are coming from, because they don't make sense to install manually either.
Comment by Eric Engestrom (1ace) - Friday, 21 June 2019, 11:55 GMT
To be clear, this means adding the following line to the PKGBUILD:

install -Dt "${pkgdir}/usr/share/meson/cross" -m644 cross/*
Comment by Eli Schwartz (eschwartz) - Friday, 21 June 2019, 12:19 GMT
Cross files suck. These ones are split between things that are only useful or applicable to users compiling *from* macOS *to* other Apple products, or they assume Ubuntu and are only applicable to compiling *to* mips, or they integrate with toolchains that Arch does not and has never packaged.

The one remotely applicable set of cross files for Arch Linux is the mingw ones, simply because there is actually a mingw toolchain which exists conceptually as a thing that could be conceived to be used on Arch, but not only is the relevant compiler in the AUR, the cross files don't actually match the paths used in the AUR package. Even if we wanted to support an AUR package, we couldn't, which just goes to show how foolish it is to try supporting an AUR package totally not under our control.

Loading...