From: Peter Korsgaard <peter@korsgaard.com>
To: David GOUARIN <dgouarin@gmail.com>
Cc: David GOUARIN <david.gouarin@thalesgroup.com>,
"Yann E. MORIN" <yann.morin.1998@free.fr>,
buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/2] package/pkg-waf.mk: enable definiton of env. variables in every build steps
Date: Tue, 16 Aug 2022 21:59:07 +0200 [thread overview]
Message-ID: <87a684c644.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20220705134402.5914-1-david.gouarin@thalesgroup.com> (David GOUARIN's message of "Tue, 5 Jul 2022 15:44:00 +0200")
>>>>> "David" == David GOUARIN <dgouarin@gmail.com> writes:
> It might be necessary for some packages to define environment
> variables when calling waf build and waf install.
> This is done the same way as the others package types, by defining $(PKG)_MAKE_ENV in .mk.
> Signed-off-by: David GOUARIN <david.gouarin@thalesgroup.com>
Committed to 2022.05.x and 2022.02.x, thanks.
--
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2022-08-16 19:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-05 13:44 [Buildroot] [PATCH 1/2] package/pkg-waf.mk: enable definiton of env. variables in every build steps David GOUARIN
2022-07-05 13:44 ` [Buildroot] [PATCH 2/2] package/libtalloc: bump version to 2.3.4 David GOUARIN
2022-07-23 17:15 ` Romain Naour
2022-07-24 7:59 ` Yann E. MORIN
2022-07-24 8:19 ` Romain Naour
2022-07-24 8:46 ` Yann E. MORIN
2022-07-24 8:55 ` Romain Naour
2022-07-24 10:54 ` Yann E. MORIN
2022-07-23 22:26 ` [Buildroot] [PATCH 1/2] package/pkg-waf.mk: enable definiton of env. variables in every build steps Yann E. MORIN
2022-08-16 19:59 ` Peter Korsgaard [this message]
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=87a684c644.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.com \
--cc=buildroot@buildroot.org \
--cc=david.gouarin@thalesgroup.com \
--cc=dgouarin@gmail.com \
--cc=yann.morin.1998@free.fr \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox