Markus Armbruster 5d75648b56 qapi: Generate QAPIEvent stuff into separate files ...

Having to include qapi-events.h just for QAPIEvent is suboptimal, but
quite tolerable now.  It'll become problematic when we have events
conditional on the target, because then qapi-events.h won't be usable
from target-independent code anymore.  Avoid that by generating it
into separate files.

Signed-off-by: Markus Armbruster <armbru@redhat.com>
Reviewed-by: Marc-André Lureau <marcandre.lureau@redhat.com>
Message-Id: <20190214152251.2073-6-armbru@redhat.com>

2019-02-18 14:44:04 +01:00

..

__init__.py

…

commands.py

qapi: Clean up modular built-in code generation a bit

2019-02-18 14:44:04 +01:00

common.py

qapi: Prepare for system modules other than 'builtin'

2019-02-18 14:44:04 +01:00

doc.py

qapi: add condition to variants documentation

2018-12-14 06:52:48 +01:00

events.py

qapi: Generate QAPIEvent stuff into separate files

2019-02-18 14:44:04 +01:00

introspect.py

qapi: Add #if conditions to generated code members

2018-12-14 06:52:48 +01:00

types.py

qapi: Prepare for system modules other than 'builtin'

2019-02-18 14:44:04 +01:00

visit.py

qapi: Prepare for system modules other than 'builtin'

2019-02-18 14:44:04 +01:00