When using Unity as a Meson subproject in a project I work on, the following notice appears when running meson setup ...:
unity| NOTICE: Future-deprecated features used:
unity| * 1.1.0: {'"boolean option" keyword argument "value" of type str'}
For context, the whole subproject setup output is:
unity| Project name: unity
unity| Project version: 2.6.1
unity| C compiler for the host machine: cc (gcc 15.2.0 "cc (Ubuntu 15.2.0-16ubuntu1) 15.2.0")
unity| C linker for the host machine: cc ld.bfd 2.46
unity| Program auto/generate_test_runner.rb found: YES (/home/dmajda/Code/aocs-core/lib/ad7291/subprojects/unity/auto/generate_test_runner.rb)
unity| Build targets in project: 2
unity| NOTICE: Future-deprecated features used:
unity| * 1.1.0: {'"boolean option" keyword argument "value" of type str'}
unity| Subproject unity finished.
I'm not sure what option does the notice refer to, but Meson ends up reporting a warning for the subproject at the very end of the output:
Subprojects
...
unity: YES 1 warnings
So I guess the notice is worth fixing.
Meson version: 1.10.1
Platform: Ubuntu 26.04 on x86-64
When using Unity as a Meson subproject in a project I work on, the following notice appears when running
meson setup ...:For context, the whole subproject setup output is:
I'm not sure what option does the notice refer to, but Meson ends up reporting a warning for the subproject at the very end of the output:
So I guess the notice is worth fixing.
Meson version: 1.10.1
Platform: Ubuntu 26.04 on x86-64