d/numam-dpdk
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

doc: update quick start guide for meson

Browse Source 
The build-sdk-meson.txt file is a little out of date, so update it with
information on the latest build requirements, and remove any content
no longer needed.

Since the cross-compilation file quoted in the document is now considerably
longer and more complex than previous, replace the contents of the file
with a summary of it instead. This is shorter and more maintainable, and
the original file is available as part of the repo anyway if the user wants
to view it.

Signed-off-by: Bruce Richardson <bruce.richardson@intel.com>
This commit is contained in:
Bruce Richardson 2019-05-29 17:19:32 +01:00 committed by Thomas Monjalon
parent 67dd4d77e0
commit 8f4ebd0c34
1 changed files with 5 additions and 22 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

27
doc/build-sdk-meson.txt
View File

@ -32,8 +32,8 @@ The ``meson`` tool is used to configure a DPDK build. On most Linux
distributions this can be got using the local package management system, distributions this can be got using the local package management system,
e.g. ``dnf install meson`` or ``apt-get install meson``. If meson is not e.g. ``dnf install meson`` or ``apt-get install meson``. If meson is not
available as a suitable package, it can also be installed using the Python available as a suitable package, it can also be installed using the Python
3 ``pip`` tool, e.g. ``pip3 install meson``. Version 0.42 of meson is 3 ``pip`` tool, e.g. ``pip3 install meson``. Version 0.47.1 of meson is
recommended - if the version packaged is too old, the latest version is required - if the version packaged is too old, the latest version is
generally available from "pip". generally available from "pip".
The other dependency for building is the ``ninja`` tool, which acts similar The other dependency for building is the ``ninja`` tool, which acts similar
@ -164,20 +164,9 @@ For example if the target machine is arm64 we can use the following
command:: command::
meson arm-build --cross-file config/arm/arm64_armv8_linux_gcc meson arm-build --cross-file config/arm/arm64_armv8_linux_gcc
where config/arm/arm64_armv8_linux_gcc contains the following where config/arm/arm64_armv8_linux_gcc contains settings for the compilers
parameters:: and other build tools to be used, as well as characteristics of the target
machine.
[binaries]
c = 'aarch64-linux-gnu-gcc'
cpp = 'aarch64-linux-gnu-cpp'
ar = 'aarch64-linux-gnu-ar'
[host_machine]
system = 'linux'
cpu_family = 'aarch64'
cpu = 'armv8-a'
endian = 'little'
Using the DPDK within an Application Using the DPDK within an Application
------------------------------------- -------------------------------------
@ -203,9 +192,3 @@ From examples/helloworld/Makefile::
build: build:
@mkdir -p $@ @mkdir -p $@
NOTE: for --static builds, DPDK needs to be built with Meson >= 0.46 in order to
fully generate the list of private dependencies. If DPDK is built with an older
version of Meson, it might be necessary to manually specify dependencies of DPDK
PMDs/libraries, for example -lmlx5 -lmnl for librte-pmd-mlx5, or the static link
step might fail.