Markus Armbruster 1fb1d31a1f qapi/types qapi/visit: Generate built-in stuff into separate files ... Linking code from multiple separate QAPI schemata into the same program is possible, but involves some weirdness around built-in types: * We generate code for built-in types into .c only with option --builtins. The user is responsible for generating code for exactly one QAPI schema per program with --builtins. * We generate code for built-in types into .h regardless of --builtins, but guarded by #ifndef QAPI_VISIT_BUILTIN. Because all copies of this code are exactly the same, including any combination of these headers works. Replace this contraption by something more conventional: generate code for built-in types into their very own files: qapi-builtin-types.c, qapi-builtin-visit.c, qapi-builtin-types.h, qapi-builtin-visit.h, but only with --builtins. Obey --output-dir, but ignore --prefix for them. Make qapi-types.h include qapi-builtin-types.h. With multiple schemata you now have multiple qapi-types.[ch], but only one qapi-builtin-types.[ch]. Same for qapi-visit.[ch] and qapi-builtin-visit.[ch]. Bonus: if all you need is built-in stuff, you can include a much smaller header. To be exploited shortly. Backports commit cdb6610ae4283720037bae2af1f78bd40eb5fe71 from qemu		2018-03-09 09:25:59 -05:00
..
__init__.py	qapi-gen: New common driver for code and doc generators	2018-03-09 08:47:12 -05:00
common.py	qapi/types qapi/visit: Generate built-in stuff into separate files	2018-03-09 09:25:59 -05:00
events.py	qapi: Make code-generating visitors use QAPIGen more	2018-03-09 09:11:28 -05:00
types.py	qapi/types qapi/visit: Generate built-in stuff into separate files	2018-03-09 09:25:59 -05:00
visit.py	qapi/types qapi/visit: Generate built-in stuff into separate files	2018-03-09 09:25:59 -05:00