aboutsummaryrefslogtreecommitdiff
path: root/docs/markdown/Keyval-module.md
AgeCommit message (Collapse)AuthorFilesLines
2021-01-31Capitalize "Meson" consistently as it is a proper name. [skip ci]Jussi Pakkanen1-1/+1
2021-01-30Rewrap long text lines in docs. [skip ci]Jussi Pakkanen1-16/+19
2020-07-19Stabilize keyval moduleMarc-André Lureau1-2/+2
We have experimented with the module for about a year in a qemu branch (https://wiki.qemu.org/Features/Meson), and we would like to start moving the build system to meson. For that, keyval should have the stability guarantees. Cc: Paolo Bonzini <pbonzini@redhat.com>
2020-05-08rename unstable-kconfig to unstable-keyvalPaolo Bonzini1-0/+55
Discussions in #6524 have shown that there are various possible uses of the kconfig module and even disagreements in the exact file format between Python-based kconfiglib and the tools in Linux. Instead of trying to reconcile them, just rename the module to something less suggestive and leave any policy to meson.build files. In the future it may be possible to add some kind of parsing through keyword arguments such as bool_true, quoted_strings, etc. and possibly creation of key-value lists too. For now, configuration_data objects provide an easy way to access quoted strings. Note that Kconfig stores false as "absent" so it was already necessary to write "x.has_key('abc')" rather than the more compact "x['abc']". Therefore, having to use configuration_data does not make things much more verbose.