Re: [RFC PATCH 15/18] qapi: Support empty modules

2019-11-12 Thread Markus Armbruster
Kevin Wolf writes: > If you added an include file that doesn't contain any definitions, no > source files would be generated for it. However, in other source files, > you would still get an #include for the header files of the empty > module. Bug. Cause: we generate #include module.h always,

[RFC PATCH 15/18] qapi: Support empty modules

2019-10-17 Thread Kevin Wolf
If you added an include file that doesn't contain any definitions, no source files would be generated for it. However, in other source files, you would still get an #include for the header files of the empty module. The intended behaviour is that empty source files are created for empty modules.