-
Notifications
You must be signed in to change notification settings - Fork 976
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
[bug] Deprecate MesonDeps #13048
Comments
MesonDeps as a new generator to create an extra file with all the GNU flags from all the dependencies.
according to doc: MesonToolchain normally works together with PkgConfigDeps to manage all the dependencies, but sometimes we need to gather some flags coming from Autotools tool so that’s what MesonDeps is meant for. In other words, it is typically used when Meson cannot find a dependency using the already known detection mechanisms like: pkg-config, cmake, config-tool, etc. For instance, if we’d have these lines in your meson.build file, you might need MesonDeps to find that dependency and inject the correct flags to the compiler: |
It is used solely by 1 recipe in the whole ConanCenter, so this is not massive breakage, but would completely negligible. |
there are also forked recipes and private recipes in enterprise environments |
If there are forks, they will contain at most 1 package with it. This wouldn't be a massive breakage. And I am considering it for a reason: it doesn't work as it advertises. It cannot propagate link information by itself. When used together with PkgConfigDeps there will be most likely duplicated paths and flags. So the whole thing needs to be reconsidered. |
conan-io/conan-center-index#16014 works without MesonDeps, so no recipe in ConanCenter actually depends on MesonDeps |
Closed by #13134 |
Environment details
Latest 1.58, all OSs and versions
Steps to reproduce
MesonDeps cannot transmit transitive dependencies information, so it seems quite useless:
So it is not clear the value proposition of MesonDeps then, better remove it, at least from 2.0, until it becomes clear.
Logs
No response
The text was updated successfully, but these errors were encountered: