From: Anatoly Burakov <anatoly.burakov@intel.com>
To: dev@dpdk.org
Subject: [PATCH v3 0/1] Add DPDK build directory configuration script
Date: Wed, 27 Nov 2024 15:01:36 +0000 [thread overview]
Message-ID: <cover.1732719618.git.anatoly.burakov@intel.com> (raw)
In-Reply-To: <cover.1725462615.git.anatoly.burakov@intel.com>
Note: this patch depends upon Bruce's v5 patchset:
https://patches.dpdk.org/project/dpdk/list/?series=34055
This patch is based on initial script for VSCode configuration:
https://patches.dpdk.org/project/dpdk/patch/6a6b20c037cffcc5f68a341c4b4e4f21990ae991.1721997016.git.anatoly.burakov@intel.com/
This is a TUI frontend for Meson. It is by no means meant to be used as a
replacement for using Meson proper, it is merely a shortcut for those who
constantly deal with creating new Meson build directories but don't want to type
out all components each time.
It relies on dependency graphs from the above Bruce's patchset (v3 introduced
support for optional dependencies, which this script requires) to work. It'll
create a Meson build directory in the background, enabling all options, and then
use both dependency graph and meson introspection to figure out what can be
built, and what dependencies it has.
With this script it is possible to produce very minimal builds - the script is
not only able to track dependencies between components to enable them, but it
can also (with a command line switch) specify which libraries we want to enable
(omitting those not required by currently selected components). This can be
useful for users who frequently reconfigure their tree with e.g. debug/release,
shared/static etc. builds while keeping the reconfiguration time fairly small.
We used to have a "setup.sh" script to "set up" DPDK. This is not that, but it's
a good start.
Anatoly Burakov (1):
devtools: add DPDK build directory setup script
devtools/dpdk-setup.py | 784 ++++++++++++++++++++++++++++
doc/guides/linux_gsg/build_dpdk.rst | 26 +
2 files changed, 810 insertions(+)
create mode 100755 devtools/dpdk-setup.py
--
2.43.5
next prev parent reply other threads:[~2024-11-27 15:01 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-04 15:17 [PATCH v1 " Anatoly Burakov
2024-09-04 15:17 ` [PATCH v1 1/1] usertools: add DPDK build directory setup script Anatoly Burakov
2024-09-05 6:05 ` Morten Brørup
2024-09-05 7:29 ` David Marchand
2024-09-05 9:47 ` Burakov, Anatoly
2024-09-06 7:41 ` fengchengwen
2024-09-06 8:28 ` Morten Brørup
2024-09-06 8:55 ` Burakov, Anatoly
2024-11-26 14:43 ` [PATCH v2 0/1] Add DPDK build directory configuration script Anatoly Burakov
2024-11-26 14:43 ` [PATCH v2 1/1] devtools: add DPDK build directory setup script Anatoly Burakov
2024-11-27 15:01 ` Anatoly Burakov [this message]
2024-11-27 15:01 ` [PATCH v3 " Anatoly Burakov
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=cover.1732719618.git.anatoly.burakov@intel.com \
--to=anatoly.burakov@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).