There's more going on than just that.

The whole gst-devtools module setup is a bit weird, basically the validate tarball is made from a subdirectory in the git module, but the top-level meson.build is the one that includes the project().

So the meson support is not really shippable in a tarball as-is.

I think what's needed is probably something to tell Meson for subprojects that the actual subproject is in a sub-directory of the git checkout.

(The Meson subproject angle comes is because of gst-build.)

> I think what's needed is probably something to tell Meson for subprojects that the actual subproject is in a sub-directory of the git checkout.

I thought that gst-devtools should be a coeherent project in meson when I went that road, then you have gst-validate (which tbh I would rather move to -base at some point) and other devtools. In the current context where we still have autotools in the way, it looks messy, but I think in the long run it would be better, don't you think?

-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/gstreamer/gst-devtools/issues/28.