-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
Dependency name method producing unexpected results #12967
Comments
dcbaker
added a commit
to dcbaker/meson
that referenced
this issue
Mar 13, 2024
Otherwise internal dependencies have auto-generated names that are not human readable. Instead, use the name that the dependency overrides. For example: ```meson meson.override_dependency('zlib', declare_dependency()) dep_zlib = dependency('zlib') assert(dep_zlib.name() == 'zlib') ``` Fixes: mesonbuild#12967
dcbaker
added a commit
to dcbaker/meson
that referenced
this issue
Mar 13, 2024
Otherwise internal dependencies have auto-generated names that are not human readable. Instead, use the name that the dependency overrides. For example: ```meson meson.override_dependency('zlib', declare_dependency()) dep_zlib = dependency('zlib') assert(dep_zlib.name() == 'zlib') ``` Fixes: mesonbuild#12967
dcbaker
added a commit
to dcbaker/meson
that referenced
this issue
Mar 13, 2024
Otherwise internal dependencies have auto-generated names that are not human readable. Instead, use the name that the dependency overrides. For example: ```meson meson.override_dependency('zlib', declare_dependency()) dep_zlib = dependency('zlib') assert(dep_zlib.name() == 'zlib') ``` Fixes: mesonbuild#12967
dcbaker
added a commit
that referenced
this issue
Mar 15, 2024
Otherwise internal dependencies have auto-generated names that are not human readable. Instead, use the name that the dependency overrides. For example: ```meson meson.override_dependency('zlib', declare_dependency()) dep_zlib = dependency('zlib') assert(dep_zlib.name() == 'zlib') ``` Fixes: #12967
soumyaDghosh
pushed a commit
to soumyaDghosh/meson
that referenced
this issue
Jun 4, 2024
Otherwise internal dependencies have auto-generated names that are not human readable. Instead, use the name that the dependency overrides. For example: ```meson meson.override_dependency('zlib', declare_dependency()) dep_zlib = dependency('zlib') assert(dep_zlib.name() == 'zlib') ``` Fixes: mesonbuild#12967
dcbaker
added a commit
to dcbaker/meson
that referenced
this issue
Sep 12, 2024
Otherwise internal dependencies have auto-generated names that are not human readable. Instead, use the name that the dependency overrides. For example: ```meson meson.override_dependency('zlib', declare_dependency()) dep_zlib = dependency('zlib') assert(dep_zlib.name() == 'zlib') ``` Fixes: mesonbuild#12967
Reopened by #13387 |
dcbaker
added a commit
to dcbaker/meson
that referenced
this issue
Sep 12, 2024
Otherwise internal dependencies have auto-generated names that are not human readable. Instead, use the name that the dependency overrides. For example: ```meson meson.override_dependency('zlib', declare_dependency()) dep_zlib = dependency('zlib') assert(dep_zlib.name() == 'zlib') ``` Fixes: mesonbuild#12967
eli-schwartz
pushed a commit
that referenced
this issue
Sep 23, 2024
Otherwise internal dependencies have auto-generated names that are not human readable. Instead, use the name that the dependency overrides. For example: ```meson meson.override_dependency('zlib', declare_dependency()) dep_zlib = dependency('zlib') assert(dep_zlib.name() == 'zlib') ``` Fixes: #12967
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
When using the
dep.name()
method, I get different results depending on whether the dependency was resolved via pkg-config, or through using the fallback subproject wrap.For example: Running
atk_dep.name()
results indep124727815663152
whenatk_dep
is coming from a subproject wrap file. Running the same method results inatk
whenatk_dep
is resolved frompkg-config
. In this case, I would expectatk_dep.name()
to always returnatk
- is that a correct assumption to make? I don't think this is just anatk
issue, so I thought it best to post it here.To reproduce
This is a basic case using the
atk
lib:meson.build
:atk
, and put it on thePKG_CONFIG_PATH
meson setup build
, and you'll see the message "atk"atk
from thePKG_CONFIG_PATH
subprojects/atk.wrap
:meson setup build
, and you'll see a message like "dep124727815663152"System parameters
python --version
: 3.10.12meson --version
: 1.3.2The text was updated successfully, but these errors were encountered: