Opened 21 months ago
Last modified 9 months ago
#65599 assigned enhancement
harfbuzz: migrate from autotools to meson, if possible
| Reported by: | mascguy (Christopher Nielsen) | Owned by: | mascguy (Christopher Nielsen) |
|---|---|---|---|
| Priority: | Normal | Milestone: | |
| Component: | ports | Version: | 2.7.2 |
| Keywords: | Cc: | ryandesign (Ryan Carsten Schmidt) | |
| Port: | harfbuzz |
Description
Upstream has switched from autotools to Meson, though the former is still supported for now.
configure: Autotools is no longer our supported build system for building the library for *nix distributions, please migrate to meson.
Now that upstream's Meson build is more mature, we should migrate if there aren't any technical barriers.
Note: See
TracTickets for help on using
tickets.
I won't be working on the autotools to meson migration since I have no love for meson. If you or someone else want to make the change that's fine. You can remove me as maintainer at that point as well.
Probably a good idea to start by making the change in harfbuzz-devel to verify it builds everywhere before switching harfbuzz. And before committing anything, make extra sure the library major and minor versions have not regressed due to the build system change; this is a common mistake projects make when switching away from autotools, especially on macOS where libtool version numbering is different from all other operating systems.
The harfbuzz port is currently at version 6.0.0, many versions behind harfbuzz-devel at 7.3.0, because versions newer than 6.0.0 don't build on all macOS versions right now. Probably best to iron out that problem and get harfbuzz updated to match harfbuzz-devel before migrating to meson. There is an upstream ticket about harfbuzz > 6.0.0 build failure that I have neglected. Blacklisting older compilers should be a viable workaround if upstream code changes don't pan out.