From: "Richardson, Bruce" <bruce.richardson@intel.com>
To: "Marchand, David" <david.marchand@redhat.com>,
David Aldrich <david.aldrich.ntml@gmail.com>
Cc: users <users@dpdk.org>
Subject: RE: How to build DPDK without usertools/dpdk-setup.sh?
Date: Wed, 11 Sep 2024 16:11:50 +0000 [thread overview]
Message-ID: <DS0PR11MB7309A6181F53AFB0787EC0A3979B2@DS0PR11MB7309.namprd11.prod.outlook.com> (raw)
In-Reply-To: <CAJFAV8w9w_-EtkY4B3ACfCR1vOXOY2HiJ4_HgaYCQK7F8rCkFg@mail.gmail.com>
> -----Original Message-----
> From: David Marchand <david.marchand@redhat.com>
> Sent: Wednesday, September 11, 2024 4:52 PM
> To: David Aldrich <david.aldrich.ntml@gmail.com>
> Cc: users <users@dpdk.org>; Richardson, Bruce
> <bruce.richardson@intel.com>
> Subject: Re: How to build DPDK without usertools/dpdk-setup.sh?
>
> Hello,
>
> On Wed, Sep 11, 2024 at 3:39 PM David Aldrich
> <david.aldrich.ntml@gmail.com> wrote:
> >
> > I don't want to 'install' because I am experimenting with different
> > dpdk versions.
>
> Well, I live with many different versions of DPDK.
> The only trick is to pass a -Dprefix=$(pwd)/install and make your
> application use this directory.
>
You can also build and link against an uninstalled DPDK by using the pkg-config files in the "meson-uninstalled" directory of your build.
For example, to get linker line use:
"PKG_CONFIG_PATH=./build/meson-uninstalled/ pkg-config --libs libdpdk"
> >
> > Is it possible to produce a target directory in v.20.11.10 similar to
> > that of dpdk-stable-19.11.14/x86_64-native-linux-gcc?
>
> An installed dpdk should be quite similar.
>
Agreed.
next prev parent reply other threads:[~2024-09-11 16:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-11 13:39 David Aldrich
2024-09-11 15:52 ` David Marchand
2024-09-11 15:59 ` David Aldrich
2024-09-11 16:11 ` Richardson, Bruce [this message]
2024-09-11 17:01 ` 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=DS0PR11MB7309A6181F53AFB0787EC0A3979B2@DS0PR11MB7309.namprd11.prod.outlook.com \
--to=bruce.richardson@intel.com \
--cc=david.aldrich.ntml@gmail.com \
--cc=david.marchand@redhat.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).