DPDK patches and discussions
 help / color / mirror / Atom feed
From: Bruce Richardson <bruce.richardson@intel.com>
To: Hideyuki Yamashita <yamashita.hideyuki@ntt-tx.co.jp>
Cc: dpdk-dev <dev@dpdk.org>
Subject: Re: [dpdk-dev] Basic question about where to write config for optional feature
Date: Tue, 1 Dec 2020 09:37:55 +0000	[thread overview]
Message-ID: <20201201091653.GA1257@bricha3-MOBL.ger.corp.intel.com> (raw)
In-Reply-To: <20201201140126.EC13.17218CA3@ntt-tx.co.jp_1>

On Tue, Dec 01, 2020 at 02:01:26PM +0900, Hideyuki Yamashita wrote:
> Hello,
> 
> I am planning to propose patch for 
> optional feature.
> 
> Question:
> Where should I write compile switch for 
> optional features?
> 
> I was planning to add flag to enable 
> optional festures into config/common_base
> like following:
> 
> +#
> +# Compile the api statistics library
> +#
> +CONFIG_RTE_LIBRTE_APISTATS=n
> 
> But make build system was gone.
> I know that meson system is there instead of make.
> 
We are really trying to move away from build-time config. Instead, please
look to make this a runtime option.

Thanks,
/Bruce

      reply	other threads:[~2020-12-01  9:38 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-11  4:18 [dpdk-dev] Arm roadmap for 20.11 Honnappa Nagarahalli
2020-11-25  5:39 ` [dpdk-dev] NTT TechnoCross roadmap for 21.02 Hideyuki Yamashita
2020-11-25 11:01   ` Morten Brørup
2020-11-26  1:20     ` Hideyuki Yamashita
2020-11-29 14:43       ` Baruch Even
2020-12-01  0:40         ` Hideyuki Yamashita
2020-12-01  5:01           ` [dpdk-dev] Basic question about where to write config for optional feature Hideyuki Yamashita
2020-12-01  9:37             ` Bruce Richardson [this message]

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=20201201091653.GA1257@bricha3-MOBL.ger.corp.intel.com \
    --to=bruce.richardson@intel.com \
    --cc=dev@dpdk.org \
    --cc=yamashita.hideyuki@ntt-tx.co.jp \
    /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).