-
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
Support compile-only dependencies #7516
Comments
You want: executable(
'foo',
'foo.c',
dependencies : dep.partial_dependency(includes : true),
) https://mesonbuild.com/Reference-manual.html#dependency-object |
Thank you! |
Hmm. It doesn't seem to work:
gives me:
If I change this to:
then it works:
(this includes the Am I missing something? |
The problem is the same with Meson 0.55.0 (the reference manual says something about this not working right until v 0.50.1). |
This looks like it might be a bug. is your project available somewhere that I could test it? |
Here is a minimal example:
Repro:
|
...and:
|
libfuse also uses meson: https://github.com/libfuse/libfuse/blob/master/meson.build |
Not a regression, but a legitimate bug. The In the short term using sigh for bugs. |
I'm removing this from the milestone. This is probably going to be a pretty invasive fix. |
Without this, the examples can't find a libdrm include: ./SRMTypes.h:10:10: fatal error: drm_fourcc.h: No such file or directory Also note that it seems 'compile_args' contains the gcc include paths, not 'includes'. Some discussion here at mesonbuild/meson#7516
Without this, the examples can't find a libdrm include: ./SRMTypes.h:10:10: fatal error: drm_fourcc.h: No such file or directory Note that when using meson partial_dependency(), 'compile_args' contains the gcc include paths, not 'includes'. Some discussion here at mesonbuild/meson#7516
I have a pkgconfig dependency for which I only need the headers - I do not want to link against the shared library. I tried to accomplish this with:
Unfortunately that did not work, the compile command did not include the include directory.
Bug or feature? I suspect that
include_directories
is not intended for absolute paths - but is there another solution?The text was updated successfully, but these errors were encountered: