On 4/28/25 12:54 PM, Stefan Hajnoczi wrote:
Sure.
Maybe there is a misunderstanding, but at this point, we are not trying
to invent anything new. We are just looking for a way to build QAPI
generated code only once, so it's possible to link together object files
coming from two different targets.
My mistake was to not mention introspection in the cover letter, but
thanks to Markus and Daniel, I understood the consequences of that, and
my position is to keep the current schema and serialization methods
*exactly* as they are, so consumers don't see any change. The only place
where we need to do changes are scripts/qapi and qapi/.
Okay, if this is just about QAPI for now then it's definitely too
early to discuss packaging.
I'm still curious which specific use cases you have in mind?
The (lenghty) cover letter tries to explain where we are going, and why
this change is needed for QAPI.
If it's not clear, feel free to tell, I'll update this for v2.
Stefan
