-
Notifications
You must be signed in to change notification settings - Fork 196
build: initialize meson build system #343
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
base: main
Are you sure you want to change the base?
Conversation
can this use only single-header one? I'm worried I will forget to add files to the meson file and will break someone, as I'm not using meson |
Probably a good idea to add a Meson build to CI here, since otherwise any future problems will only show up in WrapDB's CI, after a release is tagged. |
Since this is an interface-only library, the files list doesn't actually matter - it's just a hint for IDE file lists and compilers that don't support dependency tracking. |
It does matter because those headers are being installed, along with a pkg-config file that other software might use to build with those installed headers. |
I will add a CI task that installs the library with meson and manually compiles the demos. |
67feb42
to
36014f3
Compare
I'm adding this to meson's package registry: https://github.com/mesonbuild/wrapdb.