DPDK usage discussions
 help / color / mirror / Atom feed
From: Chengchang Tang <tangchengchang@huawei.com>
To: <users@dpdk.org>
Cc: <linuxarm@huawei.com>, <users@dpdk.org>, <bruce.richardson@intel.com>
Subject: Re: [dpdk-users] meson: is there a mechanism for controlling compilation configuration
Date: Wed, 29 Jul 2020 16:35:37 +0800	[thread overview]
Message-ID: <db34d93e-8d21-b7fa-e9b3-3a7d0ac3dd69@huawei.com> (raw)
In-Reply-To: <7f4b1e45-2e82-6be9-689d-1dca24b66bff@huawei.com>

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.
> 
> Thanks,
> Chengchang
> .
> 
> _______________________________________________
> Linuxarm mailing list
> Linuxarm@huawei.com
> http://hulk.huawei.com/mailman/listinfo/linuxarm
> 
> .
> 


  reply	other threads:[~2020-07-29  8:36 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 [this message]
2020-07-29 10:53   ` Richardson, Bruce
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=db34d93e-8d21-b7fa-e9b3-3a7d0ac3dd69@huawei.com \
    --to=tangchengchang@huawei.com \
    --cc=bruce.richardson@intel.com \
    --cc=linuxarm@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).