From: "Juraj Linkeš" <juraj.linkes@pantheon.tech>
To: thomas@monjalon.net, david.marchand@redhat.com,
bruce.richardson@intel.com
Cc: dev@dpdk.org, "Juraj Linkeš" <juraj.linkes@pantheon.tech>
Subject: [dpdk-dev] [PATCH v1] doc: update machine meson option in prog guide
Date: Tue, 5 Oct 2021 09:44:07 +0200 [thread overview]
Message-ID: <1633419847-13109-1-git-send-email-juraj.linkes@pantheon.tech> (raw)
Update the docs to reflect the two new variables, cpu_instruction_set
for non-arm builds and platform for arm builds.
Fixes: bf66003b51ec ("build: use platform for generic and native builds")
Signed-off-by: Juraj Linkeš <juraj.linkes@pantheon.tech>
---
doc/guides/prog_guide/build-sdk-meson.rst | 14 +++++++++++---
1 file changed, 11 insertions(+), 3 deletions(-)
diff --git a/doc/guides/prog_guide/build-sdk-meson.rst b/doc/guides/prog_guide/build-sdk-meson.rst
index 877a64b061..0f5ce599be 100644
--- a/doc/guides/prog_guide/build-sdk-meson.rst
+++ b/doc/guides/prog_guide/build-sdk-meson.rst
@@ -91,7 +91,8 @@ Project-specific options are passed used -Doption=value::
meson -Denable_docs=true fullbuild # build and install docs
- meson -Dmachine=generic # use builder-independent baseline -march
+ meson -Dcpu_instruction_set=generic # use builder-independent
+ # baseline -march
meson -Ddisable_drivers=event/*,net/tap # disable tap driver and all
# eventdev PMDs for a smaller build
@@ -120,9 +121,16 @@ Examples of setting some of the same options using meson configure::
re-scan from meson.
.. note::
- machine=generic uses a config that works on all supported architectures
- regardless of the capabilities of the machine where the build is happening.
+ cpu_instruction_set=generic uses an instruction set that works on all
+ supported architectures regardless of the capabilities of the machine
+ where the build is happening.
+.. note::
+ cpu_instruction_set is not used in Arm builds, as setting the instruction
+ set without other parameters leads to inferior builds. The way to tailor
+ Arm builds is to build for a SoC using -Dplatform=<SoC>.
+
+]
As well as those settings taken from ``meson configure``, other options
such as the compiler to use can be passed via environment variables. For
example::
--
2.20.1
next reply other threads:[~2021-10-05 7:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-05 7:44 Juraj Linkeš [this message]
2021-10-11 13:42 ` [dpdk-dev] [PATCH v2] " Juraj Linkeš
2021-11-26 13:41 ` Thomas Monjalon
2021-11-26 14:16 ` Juraj Linkeš
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=1633419847-13109-1-git-send-email-juraj.linkes@pantheon.tech \
--to=juraj.linkes@pantheon.tech \
--cc=bruce.richardson@intel.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--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).