----- 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. > Having a tarball containing source files which are then > duplicated in spice-gtk/ and spice/ (potentially different versions of > these files) is not too appealing. If that's what you are worrying about that doesn't change much of what we have today or tomorrow as long as spice-common doesn't provide a shared library. Furthermore, we can tweak makefile to embedded only what is required (the way I did it for gnome with libgd) _______________________________________________ Spice-devel mailing list Spice-devel@xxxxxxxxxxxxxxxxxxxxx http://lists.freedesktop.org/mailman/listinfo/spice-devel