When using CMock as a Meson subproject in a project I work on, the following warnings appear when running meson setup ...:
cmock| subprojects/cmock/meson.build:14: WARNING: Project targets '>=0.53.0' but uses feature introduced in '0.54.0': fallback arg in dependency.
...
cmock| WARNING: Project specifies a minimum meson_version '>=0.53.0' but uses features which were added in newer versions:
cmock| * 0.54.0: {'fallback arg in dependency'}
For context, the whole subproject setup output is:
cmock| Project name: cmock
cmock| Project version: undefined
cmock| C compiler for the host machine: cc (gcc 15.2.0 "cc (Ubuntu 15.2.0-16ubuntu1) 15.2.0")
cmock| C linker for the host machine: cc ld.bfd 2.46
cmock| subprojects/cmock/meson.build:14: WARNING: Project targets '>=0.53.0' but uses feature introduced in '0.54.0': fallback arg in dependency.
cmock| Dependency unity from subproject subprojects/unity found: YES 2.6.1
cmock| Build targets in project: 3
cmock| WARNING: Project specifies a minimum meson_version '>=0.53.0' but uses features which were added in newer versions:
cmock| * 0.54.0: {'fallback arg in dependency'}
cmock| Subproject cmock finished.
Meson ends up reporting 2 warnings for the subproject at the very end of the output:
Subprojects
cmock: YES 2 warnings
...
So I guess the warnings are worth fixing — possibly by increasing meson_version in meson.build to '>=0.54.0'?
Meson version: 1.10.1
Platform: Ubuntu 26.04 on x86-64
When using CMock as a Meson subproject in a project I work on, the following warnings appear when running
meson setup ...:For context, the whole subproject setup output is:
Meson ends up reporting 2 warnings for the subproject at the very end of the output:
So I guess the warnings are worth fixing — possibly by increasing
meson_versioninmeson.buildto '>=0.54.0'?Meson version: 1.10.1
Platform: Ubuntu 26.04 on x86-64