From: Thomas Monjalon <thomas@monjalon.net>
To: Bruce Richardson <bruce.richardson@intel.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] build: remove compatibility build defines
Date: Wed, 20 Jan 2021 01:44:47 +0100 [thread overview]
Message-ID: <44157759.JqZPiELuv3@thomas> (raw)
In-Reply-To: <20201209171420.356061-1-bruce.richardson@intel.com>
09/12/2020 18:14, Bruce Richardson:
> As announced in the deprecation note, remove all compatibility build
> defines from previous make/meson versions and use only the standardized
> ones - RTE_LIB_<name> for libraries, and RTE_<CLASS>_<NAME> for drivers.
>
> Signed-off-by: Bruce Richardson <bruce.richardson@intel.com>
Applied with a note in the API release notes:
* config: Removed the old macros, included in ``rte_config.h``,
to indicate which DPDK libraries and drivers are built.
The new macros are generated by meson in a standardized format:
``RTE_LIB_<NAME>`` and ``RTE_<CLASS>_<NAME>``, where ``NAME`` is
the upper-case component name, e.g. ``EAL``, ``ETHDEV``, ``VIRTIO``,
and ``CLASS`` is the upper-case driver class, e.g. ``NET``, ``CRYPTO``.
next prev parent reply other threads:[~2021-01-20 0:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-09 17:14 Bruce Richardson
2021-01-20 0:44 ` Thomas Monjalon [this message]
2021-01-20 10:11 ` Bruce Richardson
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=44157759.JqZPiELuv3@thomas \
--to=thomas@monjalon.net \
--cc=bruce.richardson@intel.com \
--cc=dev@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).