Replies: 1 comment 1 reply
-
Many subprojects have build options to determine whether their tests get built. And in general, tests should probably be annotated with Avoiding building library targets is tougher. Meson doesn't provide a built-in way to do this and while subprojects could automatically make all libraries static and |
Beta Was this translation helpful? Give feedback.
1 reply
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.
-
Hi,
I have a setup with multiple projects that are subprojects of one another. Let's say
A -> B -> C
.They all have a CI hooked up to test compilation and run unit tests.
To avoid wasting resources, in superproject A, I want to compile every target that is defined by
meson setup
, but I don't care for superfluous B or C targets that don't participate. I also don't care for their unit test targets.At the moment, the only solution I know is listing explicitely every target I want to build and pass it to
meson compile
but that's brittle and cumbersome.Is there a better way ?
One workaround I thought of was loading
intro-targets.json
and filter it to determine the list of targets I'm interested in. I'd like to avoid that if possible.Beta Was this translation helpful? Give feedback.
All reactions