Add methods to BuildTargets for vala generated targets #14782
Conversation
TheEvilSkeleton
left a comment
TheEvilSkeleton
left a comment
There was a problem hiding this comment.
I'm no meson maintainer, but I provided the required steps in elementary/granite#873 (comment), as it depends on this PR to work. I can confirm that it builds successfully and works without any problems, so you have my approval on the testing side of things.
|
Can you also update https://github.com/mesonbuild/meson/blob/master/docs/markdown/Vala.md#gobject-introspection-and-language-bindings with the use of vala_gir()? |
dcbaker
force-pushed
the
submit/vala-header-method
branch
2 times, most recently
from
f7fd469 to
b8ff6cf
Compare
dcbaker
force-pushed
the
submit/vala-header-method
branch
from
b8ff6cf to
deb96df
Compare
dcbaker
force-pushed
the
submit/vala-header-method
branch
from
deb96df to
52912e3
Compare
|
I've also updated the gir docs in this version to have instructions for both the new and old methods. |
dcbaker
force-pushed
the
submit/vala-header-method
branch
from
52912e3 to
733ff08
Compare
|
And I updated the yaml part of the docs, which is used to generate the reference manual. |
docs/markdown/Vala.md
Outdated
| To then generate a typelib file use a custom target with the | ||
| `g-ir-compiler` program and a dependency on the library: | ||
|
|
||
| Since Meson 1.10, use the `.vala_gir()` method to get a handle to the generated `.gir` file: |
There was a problem hiding this comment.
I think this should use asterisks like *Since 1.10*
|
Looks good other than the nit in the documentation! |
This allows targets that don't link with a vala target to rely on the header generation.
Same as the previous, but for VAPI
dcbaker
force-pushed
the
submit/vala-header-method
branch
from
733ff08 to
a7a4843
Compare
dcbaker
force-pushed
the
submit/vala-header-method
branch
from
a7a4843 to
7d51e0c
Compare
|
|
5 participants
When compiling Vala we generating 2-3 files as side effects of the compilation. A C compatible header, a VAPI header, and possibly a GIR file. Currently, there is no good way to generate a dependency on those files.
With this PR that changes, as a build target has
vala_header()vala_vapi()andvala_gir()method, each returning a File object pointing to their respective generated target. Calling these methods on a target that doesn't use Vala, or that doesn't generate a GIR file, will result in an error.