Skip to content
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

Please consider migrating to meson #44

Open
agx opened this issue Nov 5, 2023 · 3 comments
Open

Please consider migrating to meson #44

agx opened this issue Nov 5, 2023 · 3 comments
Assignees

Comments

@agx
Copy link
Contributor

agx commented Nov 5, 2023

We're jumping through a lot of hoops to have install.sh and Makefile generic enough for

  • in tree builds
  • Linux distro builds
  • builds for other platforms

Using meson would make this way simpler (it e.g. has the notion of in tree package config files and package config files for the installed system), DESTDIR, changing the installation patch, etc. Things we'd otherwise have to redo ourself.

If meson is an option I could look into adding this (and once it's working we can drop the Makefile and sed invocations).

Note that there's no official go support mesonbuild/meson#123 but since we're not doing much a custom target should be just fine.

Meson is usable on Windows and MacOS too (it's used by e.g. glib and gtk which also need to be buildable on those platforms).

@subins2000
Copy link
Member

I liked using meson in Phoc, Phosh, so yes +1 to meson.

@agx
Copy link
Contributor Author

agx commented Nov 8, 2023

Awesme. I'll add that to my todo list.

@subins2000
Copy link
Member

I'm experimenting with meson for making an fcitx5 engine for Varnam. I'll take this up after

@subins2000 subins2000 self-assigned this Jan 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants