From: Thomas Monjalon <thomas@monjalon.net>
To: "jerinj@marvell.com" <jerinj@marvell.com>,
"dev@dpdk.org" <dev@dpdk.org>,
Jan Viktorin <viktorin@rehivetech.com>,
Bruce Richardson <bruce.richardson@intel.com>,
David Christensen <drc@linux.vnet.ibm.com>,
Stanislaw Kardach <kda@semihalf.com>,
Konstantin Ananyev <konstantin.v.ananyev@yandex.ru>
Cc: "david.marchand@redhat.com" <david.marchand@redhat.com>,
"juraj.linkes@pantheon.tech" <juraj.linkes@pantheon.tech>,
"fengchengwen@huawei.com" <fengchengwen@huawei.com>,
"jerinj@marvell.com" <jerinj@marvell.com>, nd <nd@arm.com>,
Ruifeng Wang <Ruifeng.Wang@arm.com>
Subject: Re: [dpdk-dev] [PATCH v2] build: ccache support for cross build
Date: Tue, 14 Jun 2022 18:09:34 +0200 [thread overview]
Message-ID: <5094542.6fTUFtlzNn@thomas> (raw)
In-Reply-To: <AS8PR08MB7080A865A372353F222BA6D79EA69@AS8PR08MB7080.eurprd08.prod.outlook.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.
> >
> > Also, updated devtools/test-meson-builds.sh script to find the correct
> > DPDK_TARGET due to change in cross file syntax.
> >
> > [1]
> > https://mesonbuild.com/Machine-files.html
> >
> > Signed-off-by: Jerin Jacob <jerinj@marvell.com>
> > ---
> >
>
> Verified that cross-build works fine with/without ccache.
> Acked-by: Ruifeng Wang <ruifeng.wang@arm.com>
Applied with minor change, thanks.
next prev parent reply other threads:[~2022-06-14 16:09 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-02 9:23 [dpdk-dev] [PATCH v1] " jerinj
2022-06-02 9:41 ` Bruce Richardson
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 [this message]
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=5094542.6fTUFtlzNn@thomas \
--to=thomas@monjalon.net \
--cc=Ruifeng.Wang@arm.com \
--cc=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=kda@semihalf.com \
--cc=konstantin.v.ananyev@yandex.ru \
--cc=nd@arm.com \
--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).