DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Juraj Linkeš" <juraj.linkes@pantheon.tech>
To: thomas@monjalon.net, david.marchand@redhat.com,
	Honnappa.Nagarahalli@arm.com, Ruifeng.Wang@arm.com,
	ferruh.yigit@intel.com, jerinjacobk@gmail.com
Cc: dev@dpdk.org, "Juraj Linkeš" <juraj.linkes@pantheon.tech>
Subject: [PATCH v3 4/4] doc: add an example arm64 cross file
Date: Tue, 25 Jan 2022 14:20:02 +0100	[thread overview]
Message-ID: <1643116802-26466-5-git-send-email-juraj.linkes@pantheon.tech> (raw)
In-Reply-To: <1643116802-26466-1-git-send-email-juraj.linkes@pantheon.tech>

The docs mention modifications and additions to the cross file, but
there is no demonstration of how those should look like.

Signed-off-by: Juraj Linkeš <juraj.linkes@pantheon.tech>
Acked-by: Ruifeng Wang <ruifeng.wang@arm.com>
---
 .../linux_gsg/cross_build_dpdk_for_arm64.rst  | 26 +++++++++++++++++++
 1 file changed, 26 insertions(+)

diff --git a/doc/guides/linux_gsg/cross_build_dpdk_for_arm64.rst b/doc/guides/linux_gsg/cross_build_dpdk_for_arm64.rst
index 045cc05c65..f491725948 100644
--- a/doc/guides/linux_gsg/cross_build_dpdk_for_arm64.rst
+++ b/doc/guides/linux_gsg/cross_build_dpdk_for_arm64.rst
@@ -137,6 +137,32 @@ Cross Compiling DPDK with GNU toolchain using Meson
    ones, which have an extra "-none-" in their name. Please modify the cross
    file binaries accordingly when using the downloaded cross compilers.
 
+   An example cross file with modified names and added numa paths would look
+   like this:
+
+   .. code-block:: console
+
+      [binaries]
+      c = 'aarch64-none-linux-gnu-gcc'
+      cpp = 'aarch64-none-linux-gnu-cpp'
+      ar = 'aarch64-none-linux-gnu-gcc-ar'
+      strip = 'aarch64-none-linux-gnu-strip'
+      pkgconfig = 'aarch64-linux-gnu-pkg-config' # the downloaded binaries
+         # don't contain a pkgconfig binary, so it's not modified
+      pcap-config = ''
+
+      [host_machine]
+      system = 'linux'
+      cpu_family = 'aarch64'
+      cpu = 'armv8-a'
+      endian = 'little'
+
+      [properties]
+      # Generate binaries that are portable across all Armv8 machines
+      platform = 'generic'
+      c_args = ['-I<numa_install_dir>/include']  # replace <numa_install_dir>
+      c_link_args = ['-L<numa_install_dir>/lib'] # with your path
+
 To cross-compile DPDK on a desired target machine we can use the following
 command::
 
-- 
2.20.1


  parent reply	other threads:[~2022-01-25 13:20 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-18 10:00 [PATCH v1] doc: arm64 cross docs improvements/fixes Juraj Linkeš
2021-11-26 13:53 ` Thomas Monjalon
2021-11-26 14:17   ` Juraj Linkeš
2021-12-07 11:05 ` [PATCH v2 0/4] " Juraj Linkeš
2021-12-07 11:05   ` [PATCH v2 1/4] doc: arm64 cross build CFLAGS/LDFLAGS alternatives Juraj Linkeš
2021-12-15  8:00     ` Ruifeng Wang
2021-12-07 11:05   ` [PATCH v2 2/4] doc: arm64 cross build binary names update Juraj Linkeš
2021-12-15  8:02     ` Ruifeng Wang
2021-12-07 11:05   ` [PATCH v2 3/4] doc: arm64 cross build numactl compilers Juraj Linkeš
2021-12-15  8:38     ` Ruifeng Wang
2021-12-07 11:05   ` [PATCH v2 4/4] docs: add an example arm64 cross file Juraj Linkeš
2021-12-15  8:59     ` Ruifeng Wang
2022-01-25 13:19   ` [PATCH v3 0/4] arm64 cross docs improvements/fixes Juraj Linkeš
2022-01-25 13:19     ` [PATCH v3 1/4] doc: arm64 cross build CFLAGS/LDFLAGS alternatives Juraj Linkeš
2022-01-25 13:20     ` [PATCH v3 2/4] doc: arm64 cross build binary names update Juraj Linkeš
2022-01-25 13:20     ` [PATCH v3 3/4] doc: arm64 cross build numactl compilers Juraj Linkeš
2022-01-25 13:20     ` Juraj Linkeš [this message]
2022-03-16 19:19     ` [PATCH v3 0/4] arm64 cross docs improvements/fixes Thomas Monjalon

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=1643116802-26466-5-git-send-email-juraj.linkes@pantheon.tech \
    --to=juraj.linkes@pantheon.tech \
    --cc=Honnappa.Nagarahalli@arm.com \
    --cc=Ruifeng.Wang@arm.com \
    --cc=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@intel.com \
    --cc=jerinjacobk@gmail.com \
    --cc=thomas@monjalon.net \
    /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).