From: Bruce Richardson <bruce.richardson@intel.com>
To: jerinj@marvell.com
Cc: dev@dpdk.org, Ruifeng Wang <ruifeng.wang@arm.com>,
Jan Viktorin <viktorin@rehivetech.com>,
David Christensen <drc@linux.vnet.ibm.com>,
Konstantin Ananyev <konstantin.v.ananyev@yandex.ru>,
thomas@monjalon.net, david.marchand@redhat.com,
juraj.linkes@pantheon.tech, fengchengwen@huawei.com
Subject: Re: [dpdk-dev] [PATCH v1] build: ccache support for cross build
Date: Thu, 2 Jun 2022 10:41:13 +0100 [thread overview]
Message-ID: <YpiFudOnPLJLp4Ol@bricha3-MOBL.ger.corp.intel.com> (raw)
In-Reply-To: <20220602092356.2788089-1-jerinj@marvell.com>
On Thu, Jun 02, 2022 at 02:53:55PM +0530, jerinj@marvell.com wrote:
> From: Jerin Jacob <jerinj@marvell.com>
>
> By default, ccache is not used for cross build[1].
> Update all cross files to use ccache if it is available
> in build machine.
>
> [1]
> https://mesonbuild.com/Machine-files.html
>
> Signed-off-by: Jerin Jacob <jerinj@marvell.com>
Does this still work even if ccache is not available? That's not fully
clear from the docs, but it seems to be that if an array is passed the
whole array is used as the command, rather than just one element of the
array. That would imply that cross-builds now require ccache. Is that
acceptable?
/Bruce
next prev parent reply other threads:[~2022-06-02 9:41 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-02 9:23 jerinj
2022-06-02 9:41 ` Bruce Richardson [this message]
2022-06-02 9:43 ` Jerin Jacob
2022-06-02 10:55 ` Thomas Monjalon
2022-06-02 12:00 ` Jerin Jacob
2022-06-02 13:33 ` Bruce Richardson
2022-06-08 8:22 ` Jerin Jacob
2022-06-08 8:30 ` Thomas Monjalon
2022-06-08 17:16 ` Jerin Jacob
2022-06-08 18:30 ` Stanisław Kardach
2022-06-08 17:13 ` [dpdk-dev] [PATCH v2] " jerinj
2022-06-09 1:44 ` fengchengwen
2022-06-10 7:30 ` Ruifeng Wang
2022-06-14 16:09 ` Thomas Monjalon
2022-06-14 16:01 ` Thomas Monjalon
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=YpiFudOnPLJLp4Ol@bricha3-MOBL.ger.corp.intel.com \
--to=bruce.richardson@intel.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=drc@linux.vnet.ibm.com \
--cc=fengchengwen@huawei.com \
--cc=jerinj@marvell.com \
--cc=juraj.linkes@pantheon.tech \
--cc=konstantin.v.ananyev@yandex.ru \
--cc=ruifeng.wang@arm.com \
--cc=thomas@monjalon.net \
--cc=viktorin@rehivetech.com \
/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;
as well as URLs for NNTP newsgroup(s).