From: "Andreas Müller" <schnitzeltony@gmail.com>
To: "Andreas Müller" <schnitzeltony@gmail.com>
Cc: akuster <akuster808@gmail.com>,
Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>,
Joshua Watt <JPEWhacker@gmail.com>,
Richard Purdie <richard.purdie@linuxfoundation.org>
Subject: Re: [OE-core] [dunfell][PATCH 1/2] classes/waf: Add build and install arguments
Date: Sat, 16 Jan 2021 21:37:54 +0100 [thread overview]
Message-ID: <CALbNGRTtSYKQfoth3uySW3bofF-CfTTWeu9DUqVyDXDwW71Z2Q@mail.gmail.com> (raw)
In-Reply-To: <165AD0D36D4C4851.15753@lists.openembedded.org>
Aargh just read cover letter - sorry
On Sat, Jan 16, 2021 at 9:37 PM Andreas Müller via
lists.openembedded.org
<schnitzeltony=gmail.com@lists.openembedded.org> wrote:
>
> On Sat, Jan 16, 2021 at 6:44 PM akuster <akuster808@gmail.com> wrote:
> >
> > From: Joshua Watt <JPEWhacker@gmail.com>
> >
> > Adds variables that can be used to allow a recipe to pass extra
> > arguments to `waf build` and `waf install`. In most cases, you want to
> > pass the same arguments to `build` and `install` (since install is a
> > superset of `build`), so by default setting EXTRA_OEWAF_BUILD also
> > affects `waf install`, but this can be overridded.
> >
> Hi Armin,
>
> Have no problem with this - most of my layers are compatible from
> dunfell up to master but from meta-musicians (musicians seem to like
> waf) I know that this can cause breakages for packages shipping (very)
> old waf. Nothing unsolvable but...
> Just out of my curiosity: Why add this patch to dunfell?
> Cheers
>
> Andreas
>
>
>
next prev parent reply other threads:[~2021-01-16 20:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-16 17:44 [dunfell][PATCH 0/2] Fix build issue for meta-oe akuster
2021-01-16 17:44 ` [dunfell][PATCH 1/2] classes/waf: Add build and install arguments akuster
2021-01-16 20:36 ` [OE-core] " Andreas Müller
[not found] ` <165AD0D36D4C4851.15753@lists.openembedded.org>
2021-01-16 20:37 ` Andreas Müller [this message]
2021-01-16 17:44 ` [dunfell][PATCH 2/2] waf: don't assume the waf intepretter is good akuster
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CALbNGRTtSYKQfoth3uySW3bofF-CfTTWeu9DUqVyDXDwW71Z2Q@mail.gmail.com \
--to=schnitzeltony@gmail.com \
--cc=JPEWhacker@gmail.com \
--cc=akuster808@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=richard.purdie@linuxfoundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.