On Thu, Jun 27, 2019 at 03:16:01PM +0200, Gerd Hoffmann wrote:
> Hi,
>
> > Ok, I can understand that. I've been thinking about how we can switch
> > libvirt to use meson too, and trying to decide between meson being the
> > owner, calling out to make vs keeping make as the owner and calling
> >
On 27/06/19 15:16, Gerd Hoffmann wrote:
> Hi,
>
>> Ok, I can understand that. I've been thinking about how we can switch
>> libvirt to use meson too, and trying to decide between meson being the
>> owner, calling out to make vs keeping make as the owner and calling
>> out to meson. Ultimately to
Hi,
> Ok, I can understand that. I've been thinking about how we can switch
> libvirt to use meson too, and trying to decide between meson being the
> owner, calling out to make vs keeping make as the owner and calling
> out to meson. Ultimately to entirely banish make, autoconf, automake,
> lib
On 27/06/19 14:23, Markus Armbruster wrote:
> Paolo Bonzini writes:
>> On 27/06/19 11:03, Daniel P. Berrangé wrote:
>> There are two parts of this. One is practical and has to do with
>> supporting a step-by-step transition. Using ninja2make makes it trivial
>> to have make build products that d
On Thu, Jun 27, 2019 at 12:16:05PM +0200, Paolo Bonzini wrote:
> On 27/06/19 11:03, Daniel P. Berrangé wrote:
> > On Mon, Jun 10, 2019 at 01:14:57PM +0200, Paolo Bonzini wrote:
> >> The Meson build system is integrated in the existing configure/make steps
> >> by invoking Meson from the configure s
On Thu, Jun 27, 2019 at 02:23:52PM +0200, Markus Armbruster wrote:
> Paolo Bonzini writes:
> > But for now, since rules are
> > written half in meson and half in make, ninja2make seems the most
> > transparent way to integrate the two.
> >
> >> Part of the d
Paolo Bonzini writes:
> On 27/06/19 11:03, Daniel P. Berrangé wrote:
>> On Mon, Jun 10, 2019 at 01:14:57PM +0200, Paolo Bonzini wrote:
>>> The Meson build system is integrated in the existing configure/make steps
>>> by invoking Meson from the configure script and converting Meson's
>>> build.ni
On 27/06/19 11:03, Daniel P. Berrangé wrote:
> On Mon, Jun 10, 2019 at 01:14:57PM +0200, Paolo Bonzini wrote:
>> The Meson build system is integrated in the existing configure/make steps
>> by invoking Meson from the configure script and converting Meson's
>> build.ninja
>> rules to an included Ma
Markus Armbruster writes:
> Paolo Bonzini writes:
>
>> The Meson build system is integrated in the existing configure/make steps
>> by invoking Meson from the configure script and converting Meson's
>> build.ninja
>> rules to an included Makefile.
>>
>> Signed-off-by: Paolo Bonzini
>> ---
>>
On Mon, Jun 10, 2019 at 01:14:57PM +0200, Paolo Bonzini wrote:
> The Meson build system is integrated in the existing configure/make steps
> by invoking Meson from the configure script and converting Meson's build.ninja
> rules to an included Makefile.
Why did you take the route of converting ninj
On 26/06/19 19:34, Markus Armbruster wrote:
> Paolo Bonzini writes:
>
>> The Meson build system is integrated in the existing configure/make steps
>> by invoking Meson from the configure script and converting Meson's
>> build.ninja
>> rules to an included Makefile.
>>
>> Signed-off-by: Paolo Bon
Paolo Bonzini writes:
> The Meson build system is integrated in the existing configure/make steps
> by invoking Meson from the configure script and converting Meson's build.ninja
> rules to an included Makefile.
>
> Signed-off-by: Paolo Bonzini
> ---
> Makefile | 9 +
> configure
The Meson build system is integrated in the existing configure/make steps
by invoking Meson from the configure script and converting Meson's build.ninja
rules to an included Makefile.
Signed-off-by: Paolo Bonzini
---
Makefile | 9 +
configure| 30 ++
meson.build
13 matches
Mail list logo
