DPDK patches and discussions
 help / color / mirror / Atom feed
From: Bruce Richardson <bruce.richardson@intel.com>
To: dev@dpdk.org
Cc: mb@smartsharesystems.com, Bruce Richardson <bruce.richardson@intel.com>
Subject: [PATCH v3 0/3] Improve optional lib support
Date: Wed, 20 Dec 2023 14:21:49 +0000	[thread overview]
Message-ID: <20231220142152.492556-1-bruce.richardson@intel.com> (raw)
In-Reply-To: <20231103162830.593702-1-bruce.richardson@intel.com>

This patchset builds on the previous v1 and v2, and the discussion
which followed about what libraries should be optional. While still
a long way to go from the position suggested in the v2 discussion,
this set moves us a bit further along the road.

The first patch is a direct v3 from previous versions, changing the
tracking from a list of optional libs to a list of mandatory ones.
The second patch then knocks off another 5 libs off the mandatory
list - all are libs which should have few dependencies in other
components, but which some common sample apps like l3fwd depend upon.
It should be possible to make other libs optional in future, but to
do so likely requires code-changes to #ifdef out support in places.

To that end, patch 3 is an RFC to add support for "optional libs" to
the build system. For now, nothing uses this, but it may be useful if
someone does want to take on the task of removing a hard dependency
from one component on another and making it optional.

Bruce Richardson (3):
  build: track mandatory rather than optional libs
  build: remove 5 libs from mandatory list
  build: RFC - add support for optional dependencies

 app/test/meson.build |  4 +--
 drivers/meson.build  |  7 +++++
 lib/meson.build      | 72 ++++++++++++++++----------------------------
 3 files changed, 35 insertions(+), 48 deletions(-)

--
2.40.1


  parent reply	other threads:[~2023-12-20 14:22 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-03 16:28 [PATCH 24.03] build: track mandatory rather than optional libs Bruce Richardson
2023-11-03 16:52 ` [PATCH 24.03 v2] " Bruce Richardson
2023-11-03 17:31   ` Morten Brørup
2023-11-03 18:08     ` Bruce Richardson
2023-11-03 20:19       ` Morten Brørup
2023-11-06 10:28         ` Bruce Richardson
2023-11-06 11:22           ` Morten Brørup
2023-11-06 11:27             ` Bruce Richardson
2023-11-06 11:37               ` Morten Brørup
2023-12-20 14:21 ` Bruce Richardson [this message]
2023-12-20 14:21   ` [PATCH v3 1/3] " Bruce Richardson
2023-12-20 14:21   ` [PATCH v3 2/3] build: remove 5 libs from mandatory list Bruce Richardson
2023-12-20 15:18     ` Morten Brørup
2023-12-20 16:05       ` Bruce Richardson
2023-12-20 14:21   ` [PATCH v3 3/3] build: RFC - add support for optional dependencies Bruce Richardson
2023-12-20 15:08     ` Morten Brørup
2023-12-20 15:43       ` Bruce Richardson
2024-10-04 20:59         ` Stephen Hemminger
2024-02-01  9:23   ` [PATCH v3 0/3] Improve optional lib support David Marchand
2024-02-01  9:25     ` 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=20231220142152.492556-1-bruce.richardson@intel.com \
    --to=bruce.richardson@intel.com \
    --cc=dev@dpdk.org \
    --cc=mb@smartsharesystems.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).