commit | ed7dbeffdc1d81444ef2639c65893ebd35db63b5 | [log] [tgz] |
---|---|---|
author | Patrick Williams <patrick@stwcx.xyz> | Fri Feb 07 10:54:37 2025 -0500 |
committer | Patrick Williams <patrick@stwcx.xyz> | Fri Feb 28 23:12:58 2025 +0000 |
tree | d80ba90edd9d9f4bb35eb81c716c69a3f6bdcf41 | |
parent | 26a386ff6265a31efd8010e1b7518780673de1c2 [diff] |
build: use allowed over enabled or not-disabled Meson feature options are typically in a tri-state of enabled, disabled, or auto. The enabled and disabled functions on an option (from `get_option`) no longer return true for auto features. Instead, the expectation is to use `allowed()` which is true for both enabled and auto. Switch all uses of `enabled` to `allowed`. Switch all uses of `not disabled` to `allowed`. Change-Id: Ib0b26af4bd0e8685c83b1b0181f70bfca59ab2bc Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
meson builddir ninja -C builddir
meson builddir -Dbuildtype=minsize -Db_lto=true -Dtests=disabled ninja -C builddir
If any of the dependencies are not found on the host system during configuration, meson automatically gets them via its wrap dependencies mentioned in ipmid/subprojects
.
meson builddir -Dwrap_mode=nofallback ninja -C builddir
meson builddir -Dbuildtype=debug ninja -C builddir
meson builddir -Db_coverage=true -Dtests=enabled ninja -C builddir test ninja -C builddir coverage