diff options
author | Eli Schwartz <eschwartz@archlinux.org> | 2022-02-27 21:28:31 -0500 |
---|---|---|
committer | Eli Schwartz <eschwartz@archlinux.org> | 2022-04-13 17:27:09 -0400 |
commit | b55349c2e9ac6f9e37e2fd6e7a8333f6893fbaa9 (patch) | |
tree | 96c13c307755d882c82e86836c0abf16755be52a /test cases/unit/69 cross | |
parent | c649a2b8c59c9f49affca9bd89c126bfa0f54449 (diff) | |
download | meson-b55349c2e9ac6f9e37e2fd6e7a8333f6893fbaa9.zip meson-b55349c2e9ac6f9e37e2fd6e7a8333f6893fbaa9.tar.gz meson-b55349c2e9ac6f9e37e2fd6e7a8333f6893fbaa9.tar.bz2 |
dependencies: tighten type checking and fix cmake API violation for get_variable
dep.get_variable() only supports string values for pkg-config and
config-tool, because those interfaces use text communication, and
internal variables (from declare_dependency) operate the same way.
CMake had an oddity, where get_variable doesn't document that it allows
list values but apparently it miiiiiight work? Actually getting that
kind of result would be dangerously inconsistent though. Also, CMake
does not support lists so it's a lie. Strings that are *treated* as
lists with `;` splitting don't count...
We could do two things here:
- raise an error
- treat it as a string and return a string
It's not clear what the use case of get_variable() on a maybe-list is,
and should probably be a hard error. But that's controversial, so
instead we just return the original `;`-delimited string. It is probably
the wrong thing, but users are welcome to cope with that somehow on
their own.
Diffstat (limited to 'test cases/unit/69 cross')
0 files changed, 0 insertions, 0 deletions