-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
Using a custom VAPI does not generate a -pkg foo flag #2103
Comments
The example assumes that there's a pkg-config file named Could you provide a failing sample? |
The follow is my meson.build file:
The vapi directory contains the gl.vapi and sdl2.vapi files. The following is the output of meson build:
The following is the output of ninja:
As you can see, the valac line does not contain the --pkg=gl --pkg=sdl2 flags.
|
It's definately a bug, both |
I'm also affected by this bug, hitting this while trying to port Dino to Windows. Workaround for vapi files shipped with Vala:
General workaround:
|
This is probably caused by meson/mesonbuild/backend/backends.py Lines 1057 to 1067 in 39ecfc2
Line 1058 probably should be replaced with Edit: an extra check in form of |
I agree. |
The current 'Using a custom VAPI' (with pkg-config file) example on the wiki does not work for me.
I need to explicitly add a --pkg=foo to the executable line. I can only assume that this is a bug?
e.g.
change
to
BTW, on the 'Using a custom VAPI' (with no pkg-config file) example, the foo_vapi line is missing a closing parentheses.
The text was updated successfully, but these errors were encountered: