Hey, On Thu, Dec 04, 2014 at 05:51:08AM -0500, Marc-André Lureau wrote: > > > ----- Original Message ----- > > On Thu, Dec 04, 2014 at 05:22:34AM -0500, Marc-André Lureau wrote: > > > > > > hi > > > > > > ----- Original Message ----- > > > > On Thu, Dec 04, 2014 at 05:12:53AM -0500, Marc-André Lureau wrote: > > > > > I mean that spice-protocol headers could be part of spice-common > > > > > repository, and released with spice-common. > > > > > > > > Released with spice-common? We are not there yet, are we? > > > > > > > > > > It's a fairly straightforward move, spice-common would just install spice > > > protocol headers as a start. > > > > Hmm, if your concern is about the generated > > spice-protocol/protocol/enums.h in spice-common, I'd tend (to try) to > > move spice.proto* + spice-codegen.py and python_modules/ to > > spice-protocol. > > It's an option, but I think it would just be easier to merge common and protocol. Hmm thinking a bit more about this would work, I assume this would mean having a --enable-spice-common-build configure argument which would check for the additional dependencies that spice-common needs (opus, celt, ...), and which would enable the build of the spice-common source files? I must say I'm not a big fan of that.. Christophe
Attachment:
pgprShsNSomlO.pgp
Description: PGP signature
_______________________________________________ Spice-devel mailing list Spice-devel@xxxxxxxxxxxxxxxxxxxxx http://lists.freedesktop.org/mailman/listinfo/spice-devel