You may need to rebase this on top of other patches that refactor the
qapi generators to track the input file, for improved error messages.
It seems qapi-visit.py and qapi-types.py remains the same as above in
upstream, which kind of change are your referring to?
Lluís' patch to use an
Wenchao Xia wenchaoq...@gmail.com writes:
于 2014/3/21 6:29, Eric Blake 写道:
On 03/18/2014 08:38 PM, Wenchao Xia wrote:
于 2014/3/7 2:49, Eric Blake 写道:
On 01/02/2014 04:10 PM, Wenchao Xia wrote:
qapi-event.py will parse the schema and generate qapi-event.c, then
the API in qapi-event.c can be
The Wednesday 26 Mar 2014 à 13:42:38 (+0100), Markus Armbruster wrote :
Wenchao Xia wenchaoq...@gmail.com writes:
于 2014/3/21 6:29, Eric Blake 写道:
On 03/18/2014 08:38 PM, Wenchao Xia wrote:
于 2014/3/7 2:49, Eric Blake 写道:
On 01/02/2014 04:10 PM, Wenchao Xia wrote:
qapi-event.py will
于 2014/3/21 6:29, Eric Blake 写道:
On 03/18/2014 08:38 PM, Wenchao Xia wrote:
于 2014/3/7 2:49, Eric Blake 写道:
On 01/02/2014 04:10 PM, Wenchao Xia wrote:
qapi-event.py will parse the schema and generate qapi-event.c, then
the API in qapi-event.c can be used to handle event in qemu code.
All API
On 03/18/2014 08:38 PM, Wenchao Xia wrote:
于 2014/3/7 2:49, Eric Blake 写道:
On 01/02/2014 04:10 PM, Wenchao Xia wrote:
qapi-event.py will parse the schema and generate qapi-event.c, then
the API in qapi-event.c can be used to handle event in qemu code.
All API have prefix qapi_event, all types
于 2014/3/7 2:49, Eric Blake 写道:
On 01/02/2014 04:10 PM, Wenchao Xia wrote:
qapi-event.py will parse the schema and generate qapi-event.c, then
the API in qapi-event.c can be used to handle event in qemu code.
All API have prefix qapi_event, all types have prefix QAPIEvent.
Examples can be found
On 01/02/2014 04:10 PM, Wenchao Xia wrote:
qapi-event.py will parse the schema and generate qapi-event.c, then
the API in qapi-event.c can be used to handle event in qemu code.
All API have prefix qapi_event, all types have prefix QAPIEvent.
Examples can be found in following patches.
The
于 2014/1/7 11:24, Wenchao Xia 写道:
+
+
+# Following are the functions that generate event behavior control
functions.
+# Those functions are put here in the qapi-event.c, since it need
to include
+# qapi-event.h for the event enum type declaration, put them in
other file
+# requiring other file
[Pressed enter too soon, forgot two things]
On Mon, 6 Jan 2014 18:10:04 -0500
Luiz Capitulino lcapitul...@redhat.com wrote:
On Fri, 3 Jan 2014 07:10:32 +0800
Wenchao Xia xiaw...@linux.vnet.ibm.com wrote:
qapi-event.py will parse the schema and generate qapi-event.c, then
the API in
On Fri, 3 Jan 2014 07:10:32 +0800
Wenchao Xia xiaw...@linux.vnet.ibm.com wrote:
qapi-event.py will parse the schema and generate qapi-event.c, then
the API in qapi-event.c can be used to handle event in qemu code.
All API have prefix qapi_event, all types have prefix QAPIEvent.
Examples can
diff --git a/scripts/qapi-event.py b/scripts/qapi-event.py
new file mode 100644
index 000..7526366
--- /dev/null
+++ b/scripts/qapi-event.py
@@ -0,0 +1,432 @@
+#
+# QAPI event generator
+#
+# Copyright IBM, Corp. 2014
+#
+# Authors:
+# Wenchao Xia xiaw...@linux.vnet.ibm.com
+#
+# This work
+
+
+# Following are the functions that generate event behavior control functions.
+# Those functions are put here in the qapi-event.c, since it need to include
+# qapi-event.h for the event enum type declaration, put them in other file
+# requiring other file include qapi-event.h, causing a
qapi-event.py will parse the schema and generate qapi-event.c, then
the API in qapi-event.c can be used to handle event in qemu code.
All API have prefix qapi_event, all types have prefix QAPIEvent.
Examples can be found in following patches.
The script mainly include three parts: generate API
13 matches
Mail list logo
