On Wed, Aug 23, 2023 at 11:38:17AM +0200, Erik Skultety wrote:
> On Mon, Aug 21, 2023 at 05:17:06AM -0700, Andrea Bolognani wrote:
> > On Mon, Feb 06, 2023 at 02:53:06PM +0100, Erik Skultety wrote:
> > > -meson setup build --werror -Dsystem=true $MESON_OPTS $MESON_ARGS || \
> > >
On Mon, Aug 21, 2023 at 05:17:06AM -0700, Andrea Bolognani wrote:
> Resurrecting this thread now what you've pushed some of the patches.
>
> On Mon, Feb 06, 2023 at 02:53:06PM +0100, Erik Skultety wrote:
> > +# $MESON_ARGS correspond to meson's setup args, i.e. configure args. It's
> > +#
Resurrecting this thread now what you've pushed some of the patches.
On Mon, Feb 06, 2023 at 02:53:06PM +0100, Erik Skultety wrote:
> +# $MESON_ARGS correspond to meson's setup args, i.e. configure args. It's
> +# populated either from a GitLab's job configuration or from command line as
> +# `$
On Mon, Feb 06, 2023 at 02:53:06PM +0100, Erik Skultety wrote:
> It is quite confusing seeing these two in a call like this one:
> $ meson build $MESON_OPTS $MESON_ARGS
>
> One has to ask 'how are they different' and 'shouldn't these be
> merged'. In fact, these variables hold very different
It is quite confusing seeing these two in a call like this one:
$ meson build $MESON_OPTS $MESON_ARGS
One has to ask 'how are they different' and 'shouldn't these be
merged'. In fact, these variables hold very different things and we
should make it more obvious. The problem is that renaming
