From: David Aldrich <david.aldrich.ntml@gmail.com>
To: users <users@dpdk.org>
Subject: Struggling with meson in dpdk 21.11
Date: Mon, 16 Sep 2024 18:42:52 +0100 [thread overview]
Message-ID: <CAJK_iejzH4A8izrFMKj7nzxh0L36ZjXvv34ek+UWjy5V+2DSkQ@mail.gmail.com> (raw)
Hi
I am upgrading from dpdk 19.11 to 21.11. With 19.11 I built dpdk with
usertools/dpdk-setup.sh option 44, which built dpdk for x64 on Linux
and installed it to:
/opt/intel/dpdk-stable-19.11.14/x86_64-native-linux-gcc/
I want to reproduce similar behaviour in 21.11 as I may have several
versions of dpdk installed.
My build procedure is:
$ cd /opt/intel/dpdk-stable-21.11.7
$ sudo meson -Dexamples=all -Dprefix="/"
-Ddisable_drivers=common/mvep,common/mlx5,net/mvneta,net/mvpp2,net/nfb,net/mlx4,net/mlx5,\
crypto/qat,crypto/aesni_gcm,crypto/aesni_mb,crypto/armv8,crypto/ccp,crypto/kasumi,crypto/mvsam,crypto/openssl,\
crypto/snow3g,crypto/zuc,compress/isal,regex/mlx5,vdpa/mlx5,net/pcap,net/szedata2,raw/ifpga,net/af_xdp,net/ipn3ke,\
crypto/ipsec_mb,crypto/ipsec_mb,crypto/mlx5,compress/mlx5,gpu/cuda build
$ cd build
$ sudo ninja
$ sudo meson install --destdir=../x86_64-native-linux-gcc
The result is:
$ ls /opt/intel/dpdk-stable-21.11.7/x86_64-native-linux-gcc/
bin include lib share
which is good, but the examples have not been built and the folders in
the build directory are empty:
$ ls /opt/intel/dpdk-stable-21.11.7/build/examples/l2fwd
$
Why are the examples not built?
Best regards
David
next reply other threads:[~2024-09-16 17:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-16 17:42 David Aldrich [this message]
2024-09-16 19:19 ` Stephen Hemminger
[not found] <mailman.3759.1726527514.951.users@dpdk.org>
2024-09-17 19:40 ` Aldrin
2024-09-17 20:21 ` Aldrin
2024-09-19 15:44 ` David Aldrich
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=CAJK_iejzH4A8izrFMKj7nzxh0L36ZjXvv34ek+UWjy5V+2DSkQ@mail.gmail.com \
--to=david.aldrich.ntml@gmail.com \
--cc=users@dpdk.org \
/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).