From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 11/11] qt: use $(TARGET_MAKE_ENV) when calling $(MAKE)
Date: Sat, 29 Oct 2016 15:57:46 +0200 [thread overview]
Message-ID: <20161029155746.1de6931c@free-electrons.com> (raw)
In-Reply-To: <1477660709-5935-11-git-send-email-gustavo.zacarias@free-electrons.com>
Hello,
On Fri, 28 Oct 2016 10:18:29 -0300, gustavo.zacarias at free-electrons.com
wrote:
> - $(QT_CONFIGURE_ENV) \
> + $(TARGET_MAKE_ENV) \
It would have been good to indicate in the commit log why you're
dropping QT_CONFIGURE_ENV here. After checking that it's indeed never
defined, I've amended the commit log accordingly.
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2016-10-29 13:57 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-28 13:18 [Buildroot] [PATCH 01/11] cryptopp: use $(HOST_MAKE_ENV) when calling $(MAKE) gustavo.zacarias at free-electrons.com
2016-10-28 13:18 ` [Buildroot] [PATCH 02/11] lzip: " gustavo.zacarias at free-electrons.com
2016-10-28 13:18 ` [Buildroot] [PATCH 03/11] lzip: use $(TARGET_MAKE_ENV) for configure as well gustavo.zacarias at free-electrons.com
2016-10-28 13:18 ` [Buildroot] [PATCH 04/11] libselinux: use $(TARGET_MAKE_ENV) when calling $(MAKE) gustavo.zacarias at free-electrons.com
2016-10-28 13:18 ` [Buildroot] [PATCH 05/11] libselinux: use $(HOST_MAKE_ENV) " gustavo.zacarias at free-electrons.com
2016-10-28 13:18 ` [Buildroot] [PATCH 06/11] perl: use $(TARGET_MAKE_ENV) " gustavo.zacarias at free-electrons.com
2016-10-29 13:57 ` Thomas Petazzoni
2016-10-28 13:18 ` [Buildroot] [PATCH 07/11] perl: use $(HOST_MAKE_ENV) " gustavo.zacarias at free-electrons.com
2016-10-28 13:18 ` [Buildroot] [PATCH 08/11] dtc: use $(TARGET_CONFIGURE_OPTS) " gustavo.zacarias at free-electrons.com
2016-10-28 13:18 ` [Buildroot] [PATCH 09/11] ezxml: use $(TARGET_MAKE_ENV) " gustavo.zacarias at free-electrons.com
2016-10-28 13:18 ` [Buildroot] [PATCH 10/11] fmlib: " gustavo.zacarias at free-electrons.com
2016-10-28 13:18 ` [Buildroot] [PATCH 11/11] qt: " gustavo.zacarias at free-electrons.com
2016-10-29 13:57 ` Thomas Petazzoni [this message]
2016-10-29 13:56 ` [Buildroot] [PATCH 01/11] cryptopp: use $(HOST_MAKE_ENV) " Thomas Petazzoni
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=20161029155746.1de6931c@free-electrons.com \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/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