Replies: 1 comment 2 replies
-
This is a common issue that I think we need to find a solution. Typically a library project does: l = library()
dep = declare_dependency(link_with: l) Now if building with |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
My project uses a lot of internal libraries, and I use
declare_dependency
to express the transitive dependencies between those libraries. Normally, all the dependencies are shared libraries. However, my project have plugin libraries, that depend on the same common libraries, but I want to link statically, because I may update a plugin in an installation without updating the executable and all its shared libraries.How can I express the fact that a dependency can be either a static library depending on other static libraries, or a shared library, depending on shared libraries?
What I'd like could be, for example, to have a dependency on a
both_libraries
target, and to select the right version (static or shared) or the lib and of all its dependencies. Should we have adeclare_both_dependency
or something like that to achieve this? Or is there a simpler way? Because, actually, I need to duplicate a lot of code in my meson.build files...Beta Was this translation helpful? Give feedback.
All reactions