----- Original Message ----- > On Thu, Dec 04, 2014 at 06:06:34AM -0500, Marc-André Lureau wrote: > > > Well, I'm not suggesting something that drastic ;) Not running > > > spice-protocol configure every time is an easy win without making huge > > > changes to what we have now. > > > > I am not sure, I don't know what you have in mind to remove autoconf subdir > > for the moment. > > So far in this subthread, I've been mostly talking about not having a > spice-protocol submodule, which would avoid running ./configure for > spice-protocol every time you run configure in the main module. > > You seem to be asking about my next steps (after this series) for > spice-common/configure.ac. I've tried to explain in the cover letter, > but here is a more detailed version. > My end goal is to take part of spice-common/configure.ac (the checks for > opus, celt, pixman, ... and the AC_CONFIG_FILES() call), and move that > to a SPICE_COMMON_SETUP() m4 macro. > Then spice-common/configure.ac can call that macro, which means > spice-common still has a working configure (ie things are unchanged from > the current situation). > But the main module configure.ac can also call that macro with the path > to the spice-common submodule: SPICE_COMMON_SETUP(spice-protocol/), > which means we don't need to run spice-common/configure with all kind of > redundant tests. Ok, that sounds reasonable, even though the benefit is low imho. I'd like to see the end results in spice-server or spice-gtk before though (and to not interfere with more controversial changes, and not mix it with other build-sys changes) thanks _______________________________________________ Spice-devel mailing list Spice-devel@xxxxxxxxxxxxxxxxxxxxx http://lists.freedesktop.org/mailman/listinfo/spice-devel