[Spice-devel] [PATCH spice-server 1/2] Add support for building with meson

Eduardo Lima (Etrunko) etrunko at redhat.com
Tue Mar 27 13:32:50 UTC 2018


On 27/03/18 10:16, Christophe Fergeau wrote:
> On Tue, Mar 27, 2018 at 09:57:35AM -0300, Eduardo Lima (Etrunko) wrote:
>> On 27/03/18 09:51, Christophe Fergeau wrote:
>>> On Tue, Mar 27, 2018 at 08:53:06AM -0300, Eduardo Lima (Etrunko) wrote:
>>>> No, I think it should work, but this .wrap file is useful the first time
>>>> user clones the repository, it will fetch spice-common automatically.
>>>
>>> Hmm, but is this 'subproject' command going to handle git submodule
>>> updates properly?
>>
>> Yes, this wrap thing is built-in with meson, we can push commits to the
>> spice-common repository at will, and when we feel it is ready to be
>> used, update the wrap file with the new hash. Note that I used the
>> branch meson, but it can be a fixed commit SHA1, just as it is done.
>>
>> http://mesonbuild.com/Wrap-dependency-system-manual.html
> 
> Ah good :) However, we'll probably want to keep the submodule during the
> transition period (while we have the 2 build systems), as the autotools
> are not going to be able to use this.

Sure thing, the submodule is being removed in the same patch that takes
care of autotools removal.


-- 
Eduardo de Barros Lima (Etrunko)
Software Engineer - RedHat
etrunko at redhat.com


More information about the Spice-devel mailing list