From: Bruce Richardson <bruce.richardson@intel.com>
To: Ferruh Yigit <ferruh.yigit@amd.com>
Cc: David Young <dave@youngcopy.com>, <dev@dpdk.org>
Subject: Re: [PATCH 2/6] Section 2: Install and Build DPDK
Date: Mon, 25 Sep 2023 13:20:24 +0100 [thread overview]
Message-ID: <ZRF7CJdjlxe95whh@bricha3-MOBL.ger.corp.intel.com> (raw)
In-Reply-To: <42a18fab-e4a3-4cf6-8892-1434e4727289@amd.com>
On Mon, Sep 25, 2023 at 12:30:35PM +0100, Ferruh Yigit wrote:
> On 9/20/2023 4:48 PM, David Young wrote:
> > ---
> > .../building_from_sources.rst | 108 ++++++++++++++++++
> > .../install_and_build/index.rst | 15 +++
> > .../installing_prebuilt_packages.rst | 54 +++++++++
> > .../windows_install_build.rst | 93 +++++++++++++++
> > 4 files changed, 270 insertions(+)
> > create mode 100644 doc/guides/getting_started_guide/install_and_build/building_from_sources.rst
> > create mode 100644 doc/guides/getting_started_guide/install_and_build/index.rst
> > create mode 100644 doc/guides/getting_started_guide/install_and_build/installing_prebuilt_packages.rst
> > create mode 100644 doc/guides/getting_started_guide/install_and_build/windows_install_build.rst
> >
> > diff --git a/doc/guides/getting_started_guide/install_and_build/building_from_sources.rst b/doc/guides/getting_started_guide/install_and_build/building_from_sources.rst
> > new file mode 100644
> > index 0000000000..e4ee8e436d
> > --- /dev/null
> > +++ b/doc/guides/getting_started_guide/install_and_build/building_from_sources.rst
> > @@ -0,0 +1,108 @@
> > +.. SPDX-License-Identifier: BSD-3-Clause
> > + Copyright(c) 2010-2025 Intel Corporation.
> > +
> > +.. _building_from_sources:
> > +
> > +Building and Installing DPDK from Sources
> > +=========================================
> > +
> > +This chapter provides a comprehensive guide for building DPDK from sources on both
> > +Linux and FreeBSD platforms. It covers the necessary steps, prerequisites,
> > +and considerations for different architectures and compilers.
> > +
> > +Required Tools
> > +--------------
> > +
> > +To build DPDK, you'll need the following tools:
> > +
> > +- A C compiler like ``gcc`` (version 5+) or ``clang`` (version 3.6+)
> > +- ``pkg-config`` or ``pkgconf``
> > +- Python 3.6 or later
> > +- ``meson`` (version 0.53.2+) and ``ninja``
> > +- ``pyelftools`` (version 0.22+)
> > +
> >
>
> Is 'libnuma' also a dependency?
>
> When I remove it in my platform and build DPDK again, getting following
> in meson stage:
>
> "
> config/meson.build:419:4: ERROR: Problem encountered:
> No NUMA library (development package) found, yet DPDK configured for
> multiple NUMA nodes.
> Please install libnuma, or set 'max_numa_nodes' option to '1' to build
> without NUMA support.
> "
>
Realistically, yes it is a dependency and we should include it here.
>
>
> > +Here's how to install them:
> > +
> > +Linux
> > +^^^^^
> > +
> > +Alpine
> > +
> > +.. code-block:: bash
> > +
> > + sudo apk add alpine-sdk bsd-compat-headers
> > + pip install meson ninja
> > +
> > +Debian and Ubuntu and derivatives
> > +
> > +.. code-block:: bash
> > +
> > + sudo apt install build-essential
> > + pip install meson ninja
> > +
> > +Fedora and RedHat Enterprise Linux RHEL
> > +
> > +.. code-block:: bash
> > +
> > + sudo dnf groupinstall "Development Tools"
> > + pip install meson ninja
> > +
>
> Above are missing some of the dependencies above, just to confirm if
> they are installed by default?
> And even if so, if we should provide explicit commands to install all,
> to be sure?
>
>
>
> > +openSUSE
> > +
> > +.. code-block:: bash
> > +
> > + sudo zypper install -t pattern devel_basis python3-pyelftools
> > + pip install meson ninja
> > +
> > +FreeBSD
> > +^^^^^^^
> > +
> > +FreeBSD (as root)
> > +
> > +.. code-block:: bash
> > +
> > + pkg install meson pkgconf py38-pyelftools
> > +
> > +Note: If you're using FreeBSD, you'll also need kernel sources. Make sure they're included during the FreeBSD installation.
> > +
> > +Getting the DPDK Source
> > +-----------------------
> > +
> > +Download the DPDK source code from the official repository
> > +``https://fast.dpdk.org/rel/``.
> > +
> > +Use ``wget`` to grab the DPDK version::
> > +
> > + wget https://fast.dpdk.org/rel/dpdk-<version>.tar.xz
> > +
> > +Extract the downloaded archive:
> > +
> > +.. code-block:: bash
> > +
> > + tar -xvf dpdk-<version>.tar.gz
> > +
> > +Navigate to the DPDK directory:
> > +
> > +.. code-block:: bash
> > +
> > + cd dpdk-<version>
> > +
> > +Building DPDK
> > +-------------
> > +
> > +Configure the build based on your needs, hardware, and environment.
> > +This might include setting specific flags or options. For example: “meson setup -Dbuildtype=debugoptimized build”. Then compile using “ninja” and install using “meson install”.
> > +
> > +.. code-block:: bash
> > +
> > + ninja -C build
> > + cd build
> > + sudo ninja install>
>
> Above mentions from "meson install", here using "ninja install", should
> we unify it to one?
>
Yes, we should standardize on meson install.
>
<snip for brevity>
next prev parent reply other threads:[~2023-09-25 12:20 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-20 15:48 [PATCH 0/6] docs: Unify Getting Started Guides David Young
2023-09-20 15:48 ` [PATCH 1/6] Section 1: Introduction David Young
2023-09-25 11:30 ` Ferruh Yigit
2023-10-11 18:26 ` Dave Young
2023-09-20 15:48 ` [PATCH 2/6] Section 2: Install and Build DPDK David Young
2023-09-25 11:30 ` Ferruh Yigit
2023-09-25 12:20 ` Bruce Richardson [this message]
2023-09-25 16:05 ` Tyler Retzlaff
2023-10-12 18:08 ` Dave Young
2023-10-17 13:37 ` Tyler Retzlaff
2023-09-20 15:48 ` [PATCH 3/6] Section 3: Setting up a System to Run DPDK Applications David Young
2023-09-25 11:31 ` Ferruh Yigit
2023-09-25 12:22 ` Bruce Richardson
2023-10-12 17:32 ` Dave Young
2023-09-20 15:48 ` [PATCH 4/6] Section 4: Running Applications David Young
2023-09-25 11:32 ` Ferruh Yigit
2023-09-20 15:48 ` [PATCH 5/6] Section 5: Appendix David Young
2023-09-25 11:33 ` Ferruh Yigit
2023-09-25 11:52 ` Ferruh Yigit
2023-09-25 12:24 ` Bruce Richardson
2023-09-20 15:48 ` [PATCH 6/6] Section 6: Glossary David Young
2023-09-25 11:43 ` Ferruh Yigit
2023-09-22 4:15 ` [PATCH 0/6] docs: Unify Getting Started Guides Tyler Retzlaff
2023-09-22 14:47 ` David Marchand
2023-09-22 15:54 ` Bruce Richardson
2023-09-25 11:54 ` Ferruh Yigit
2023-10-11 18:34 ` Dave Young
2023-10-13 16:28 ` 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=ZRF7CJdjlxe95whh@bricha3-MOBL.ger.corp.intel.com \
--to=bruce.richardson@intel.com \
--cc=dave@youngcopy.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@amd.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).