doc: remove references to make from platforms guide
Make is no longer supported for compiling DPDK, references are now removed in the documentation. Signed-off-by: Ciara Power <ciara.power@intel.com> Signed-off-by: Harman Kalra <hkalra@marvell.com> Reviewed-by: Kevin Laatz <kevin.laatz@intel.com>
This commit is contained in:
parent
c2402fcaf9
commit
d2e65d43fe
@ -60,17 +60,6 @@ Native Compilation
|
||||
Refer to :doc:`../nics/mlx5` for prerequisites. Either Mellanox OFED/EN or
|
||||
rdma-core library with corresponding kernel drivers is required.
|
||||
|
||||
make build
|
||||
^^^^^^^^^^
|
||||
|
||||
.. code-block:: console
|
||||
|
||||
make config T=arm64-bluefield-linux-gcc
|
||||
make -j
|
||||
|
||||
meson build
|
||||
^^^^^^^^^^^
|
||||
|
||||
.. code-block:: console
|
||||
|
||||
meson build
|
||||
@ -126,17 +115,6 @@ Then, untar the tarball at the cross toolchain directory on the x86 host.
|
||||
cd $(dirname $(which aarch64-linux-gnu-gcc))/..
|
||||
tar xf aarch64-linux-gnu-mlx.tar
|
||||
|
||||
make build
|
||||
^^^^^^^^^^
|
||||
|
||||
.. code-block:: console
|
||||
|
||||
make config T=arm64-bluefield-linux-gcc
|
||||
make -j CROSS=aarch64-linux-gnu- CONFIG_RTE_KNI_KMOD=n CONFIG_RTE_EAL_IGB_UIO=n
|
||||
|
||||
meson build
|
||||
^^^^^^^^^^^
|
||||
|
||||
.. code-block:: console
|
||||
|
||||
meson build --cross-file config/arm/arm64_bluefield_linux_gcc
|
||||
|
@ -94,19 +94,15 @@ drivers can be compiled with the following steps,
|
||||
|
||||
.. code-block:: console
|
||||
|
||||
cd <dpdk directory>
|
||||
make config T=arm64-thunderx-linux-gcc
|
||||
make
|
||||
meson build -Dexamples=<application>
|
||||
ninja -C build
|
||||
|
||||
The example applications can be compiled using the following:
|
||||
|
||||
.. code-block:: console
|
||||
|
||||
cd <dpdk directory>
|
||||
export RTE_SDK=$PWD
|
||||
export RTE_TARGET=build
|
||||
cd examples/<application>
|
||||
make
|
||||
meson build -Dexamples=<application>
|
||||
ninja -C build
|
||||
|
||||
Cross Compilation
|
||||
~~~~~~~~~~~~~~~~~
|
||||
@ -115,10 +111,7 @@ The DPDK applications can be cross-compiled on any x86 based platform. The
|
||||
OCTEON TX SDK need to be installed on the build system. The SDK package will
|
||||
provide the required toolchain etc.
|
||||
|
||||
Refer to :doc:`../linux_gsg/cross_build_dpdk_for_arm64` for further steps on
|
||||
compilation. The 'host' & 'CC' to be used in the commands would change,
|
||||
in addition to the paths to which libnuma related files have to be
|
||||
copied.
|
||||
Refer to :doc:`../linux_gsg/cross_build_dpdk_for_arm64` for generic arm64 details.
|
||||
|
||||
The following steps can be used to perform cross-compilation with OCTEON TX
|
||||
SDK 6.2.0 patch 3:
|
||||
@ -128,34 +121,28 @@ SDK 6.2.0 patch 3:
|
||||
cd <sdk_install_dir>
|
||||
source env-setup
|
||||
|
||||
git clone https://github.com/numactl/numactl.git
|
||||
cd numactl
|
||||
git checkout v2.0.11 -b v2.0.11
|
||||
./autogen.sh
|
||||
autoconf -i
|
||||
./configure --host=aarch64-thunderx-linux CC=aarch64-thunderx-linux-gnu-gcc --prefix=<numa install dir>
|
||||
make install
|
||||
|
||||
The above steps will prepare build system with numa additions. Now this build system can be used
|
||||
to build applications for **OCTEON TX** :sup:`®` platforms.
|
||||
The above steps will prepare build system with required toolchain.
|
||||
Now this build system can be used to build applications for **OCTEON TX** :sup:`®` platforms.
|
||||
|
||||
.. code-block:: console
|
||||
|
||||
cd <dpdk directory>
|
||||
export RTE_SDK=$PWD
|
||||
export RTE_KERNELDIR=$THUNDER_ROOT/linux/kernel/linux
|
||||
make config T=arm64-thunderx-linux-gcc
|
||||
make -j CROSS=aarch64-thunderx-linux-gnu- CONFIG_RTE_KNI_KMOD=n CONFIG_RTE_EAL_IGB_UIO=n EXTRA_CFLAGS="-isystem <numa_install_dir>/include" EXTRA_LDFLAGS="-L<numa_install_dir>/lib -lnuma"
|
||||
meson build --cross-file config/arm/arm64_thunderx_linux_gcc
|
||||
ninja -C build
|
||||
|
||||
If NUMA support is not required, it can be disabled as explained in
|
||||
:doc:`../linux_gsg/cross_build_dpdk_for_arm64`.
|
||||
|
||||
Following steps could be used in that case.
|
||||
The example applications can be compiled using the following:
|
||||
|
||||
.. code-block:: console
|
||||
|
||||
make config T=arm64-thunderx-linux-gcc
|
||||
make CROSS=aarch64-thunderx-linux-gnu-
|
||||
cd <dpdk directory>
|
||||
meson build --cross-file config/arm/arm64_thunderx_linux_gcc -Dexamples=<application>
|
||||
ninja -C build
|
||||
|
||||
.. note::
|
||||
|
||||
By default, meson cross compilation uses ``aarch64-linux-gnu-gcc`` toolchain,
|
||||
if OCTEON TX SDK 6.2.0 patch 3 is available then it can be used by
|
||||
overriding the c, cpp, ar, strip ``binaries`` attributes to respective thunderx
|
||||
toolchain binaries in ``config/arm/arm64_thunderx_linux_gcc`` file.
|
||||
|
||||
SDK and related information can be obtained from: `Cavium support site <https://support.cavium.com/>`_.
|
||||
|
@ -503,27 +503,6 @@ an x86 based platform.
|
||||
Native Compilation
|
||||
~~~~~~~~~~~~~~~~~~
|
||||
|
||||
make build
|
||||
^^^^^^^^^^
|
||||
|
||||
.. code-block:: console
|
||||
|
||||
make config T=arm64-octeontx2-linux-gcc
|
||||
make -j
|
||||
|
||||
The example applications can be compiled using the following:
|
||||
|
||||
.. code-block:: console
|
||||
|
||||
cd <dpdk directory>
|
||||
export RTE_SDK=$PWD
|
||||
export RTE_TARGET=build
|
||||
cd examples/<application>
|
||||
make -j
|
||||
|
||||
meson build
|
||||
^^^^^^^^^^^
|
||||
|
||||
.. code-block:: console
|
||||
|
||||
meson build
|
||||
@ -534,17 +513,6 @@ Cross Compilation
|
||||
|
||||
Refer to :doc:`../linux_gsg/cross_build_dpdk_for_arm64` for generic arm64 details.
|
||||
|
||||
make build
|
||||
^^^^^^^^^^
|
||||
|
||||
.. code-block:: console
|
||||
|
||||
make config T=arm64-octeontx2-linux-gcc
|
||||
make -j CROSS=aarch64-marvell-linux-gnu- CONFIG_RTE_KNI_KMOD=n
|
||||
|
||||
meson build
|
||||
^^^^^^^^^^^
|
||||
|
||||
.. code-block:: console
|
||||
|
||||
meson build --cross-file config/arm/arm64_octeontx2_linux_gcc
|
||||
|
Loading…
Reference in New Issue
Block a user