From: "Richardson, Bruce" <bruce.richardson@intel.com>
To: Chengchang Tang <tangchengchang@huawei.com>,
"users@dpdk.org" <users@dpdk.org>
Cc: "linuxarm@huawei.com" <linuxarm@huawei.com>,
"users@dpdk.org" <users@dpdk.org>
Subject: Re: [dpdk-users] meson: is there a mechanism for controlling compilation configuration
Date: Wed, 29 Jul 2020 10:53:04 +0000 [thread overview]
Message-ID: <59AF69C657FD0841A61C55336867B5B0976FF117@IRSMSX103.ger.corp.intel.com> (raw)
In-Reply-To: <db34d93e-8d21-b7fa-e9b3-3a7d0ac3dd69@huawei.com>
> -----Original Message-----
> From: Chengchang Tang <tangchengchang@huawei.com>
> Sent: Wednesday, July 29, 2020 9:36 AM
> To: users@dpdk.org
> Cc: linuxarm@huawei.com; users@dpdk.org; Richardson, Bruce
> <bruce.richardson@intel.com>
> Subject: Re: [dpdk-users] meson: is there a mechanism for controlling
> compilation configuration
>
> cc'ed bruce
>
> On 2020/7/29 15:20, Chengchang Tang wrote:
> > Hi,
> > DPDK with 'make' will be deprecated in a future release. I have some
> > questions about using meson to build DPDK.
> >
> > When using the make, we can change the macros in config/common_base to
> > control the compiling macros. For example, if i want to debug the
> > mbuf, i can set CONFIG_RTE_LIBRTE_MBUF_DEBUG=y in config/common_base
> > to change the compiling macros.
> >
> > According to my understanding. DPDK meson build dose not generate
> > rte_config.h based on common_base content during compilation. Is there
> > any convenient way to modify the compiling macro in meson build. If
> > all the compilation macros need to be modified using environment
> > variable, it is inconvenient.
> >
The number of build options for make was too large, so the meson build options are deliberately kept small. However, for the case of the debug build options that were previously present, this is currently a gap that is under discussion on the DPDK dev mailing list. The discussion thread can be viewed in the archives, e.g. http://inbox.dpdk.org/dev/20200709134823.9176-1-l.wojciechow@partner.samsung.com/ .
Regards,
/Bruce
next prev parent reply other threads:[~2020-07-29 10:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-29 7:20 Chengchang Tang
2020-07-29 8:35 ` Chengchang Tang
2020-07-29 10:53 ` Richardson, Bruce [this message]
2020-07-29 11:16 ` 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=59AF69C657FD0841A61C55336867B5B0976FF117@IRSMSX103.ger.corp.intel.com \
--to=bruce.richardson@intel.com \
--cc=linuxarm@huawei.com \
--cc=tangchengchang@huawei.com \
--cc=users@dpdk.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 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).