-
Notifications
You must be signed in to change notification settings - Fork 38
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support for Meson Builds #1164
Comments
I have a first attempt at a meson package. For some reason the package gives me an error on build. |
With that minor change, it compiles and installs just fine. |
Of course, |
Building |
FYI I have updated our existing meson submission in #924 to 1.6.0 as well.
Awesome! I was able to build those with the meson-py310 from above, too, just needed a couple changes to build in maintainer mode:
Are you planning to open a PR for those? Note that libharfbuzz 2.6.8 has been fixed to build with Xcode 16 in 86b119c, but @nieder can probably comment if there is anything barring an update to the latest version. |
Thank! I am, obviously, rather clueless about the Fink Build System. Glad it wasn't too hard to turn my hacky efforts into something that works properly.
It would be better if someone who understands the Fink Build System a little better did that. There's presumably more cleaning up to do before submitting a PR. For instance, I assume the |
I notice that a number of packages are held back at ancient versions because the upstream switched to meson as a build system.
I ran into this problem when
libharfbuzz
failed to compile for me (Macos 14.7). It seemed hopeless to try to fix version 2.6.8. So I decided to grab the latest version (10.0.1) and see if I could modifylibharfbuzz0-shlibs.info
to build using meson.It involve commenting out a whole bunch of stuff (e.g., no patching required!). The
CompileScript
(without the docs, because building the docs gave me an error) wasand the
InstallScript
wasObviously, my attempt was rather hacky, but it seems that adding meson support is not so difficult (and would solve a lot of problems with other packages).
The text was updated successfully, but these errors were encountered: