From: Bruce Richardson <bruce.richardson@intel.com>
To: Luca Boccassi <luca.boccassi@gmail.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [RFCv2 00/40] Building DPDK with meson and ninja
Date: Tue, 15 Aug 2017 12:31:35 +0100 [thread overview]
Message-ID: <20170815113134.GA16284@bricha3-MOBL3.ger.corp.intel.com> (raw)
In-Reply-To: <1502794598.17570.4.camel@gmail.com>
On Tue, Aug 15, 2017 at 11:56:38AM +0100, Luca Boccassi wrote:
> On Mon, 2017-08-14 at 10:51 +0100, Bruce Richardson wrote:
> > Following on from previous RFC [http://dpdk.org/dev/patchwork/patch/2
> > 5104/]
> > here is a second draft implementation for building DPDK with meson
> > and
> > ninja. While still not building all of DPDK, and needing patch
> > cleanup so
> > that patches don't overwrite previous work, it is more complete in
> > many
> > ways than the previous version and includes:
> >
> > * dynamic build configuration e.g. building pcap driver only if pcap
> > is
> > found, only build af_packet if the target is linux, and only
> > building QAT
> > and openssl crypto drivers if libcrypto is found
> > * support for pmdinfo inside the PMDs(for shared builds) and binaries
> > (for
> > static builds)
> > * generalized/standardized way of building libs and drivers, though
> > the
> > drivers code still needs generalization at the driver, rather than
> > driver-class level.
> > * support for having a pkgconfig file for DPDK on install, and
> > helloworld
> > and l2fwd can be built using the pkgconfig info (via make, not
> > ninja)
> > * support for library versions
> > * an implementation for FreeBSD as well as Linux
> > * all libraries are included in the build, as well as a number of
> > NIC,
> > crypto, and mempool drivers
> > * the igb_uio kernel module is build via the kernel Kbuild system as
> > part
> > of a meson/ninja DPDK build
> >
> > there is still plenty to do on this, but please review and test it
> > out.
> > I've kept the patches split so that the evolution of the work is a
> > bit
> > clearer than having it all send in a monolithic patch. All feedback
> > welcome. I recommend one uses the latest meson release for this,
> > though the
> > minimum version supported should be v0.4.
> >
> > I've tested static and dynamic builds with clang and gcc on Fedora
> > 26, and
> > done test builds on FreeBSD 11 with clang too. Build with other
> > compilers
> > and on other OS's may have issues, so YMMV.
> >
> > To do a basic build, using gcc and with shared libs, in a folder
> > called "gcc-build":
> >
> > user@host:dpdk$ meson gcc-build
> > ....
> > user@host:dpdk$ cd gcc-build
> > user@host:gcc-build$ ninja
> > user@host:gcc-build$ sudo ninja install
> >
> > To do a build with clang, using static libs:
> >
> > user@host:dpdk$ CC=clang meson --default_library=static clang-
> > build
> > ....
> > user@host:dpdk$ cd clang-build
> > user@host:clang-build$ ninja
> > user@host:clang-build$ sudo ninja install
> >
> > Other options can be adjusted by running "mesonconf" in the build
> > directory, i.e. gcc-build or clang-build in the examples above.
>
> Hi Bruce,
>
> This is great, thank you!
>
> I'll try to give this set a run in the Debian context as soon as I have
> time.
>
Please do, thanks. Let me know any issues you hit, or further
suggestions for improvement. Please also check the reproducible build
aspects, as I may have let some absolute paths sneek in some places
inadvertently, while getting the more awkward stuff (like pmdinfo)
ported over.
> It's also great to see a pkg-config file!
>
I'm not sure what others think, but I believe we need to move away from
any requirement for external apps, or even our examples, to have a
particular way of being built. Instead, everything should be done
through the pkg-config, where possible.
> I haven't gone through the diff yet, but do you think it would be
> possible, now or later on, to add the option to install architecture-
> specific headers in a different directory than the arch-independent
> ones?
>
I'm sure it's possible, it's just a matter of how awkward it would be.
:-)
> This is in the context of multi-arch: on Debian and Ubuntu there's a
> lot of effort to make sure libraries built on different architectures
> are co-installable. Which means either the files must be identical, or
> in arch-specific paths (eg: /usr/include/x86_64-linux-gnu/ and
> /usr/lib/x86_64-linux-gnu/).
>
> --
> Kind regards,
> Luca Boccassi
next prev parent reply other threads:[~2017-08-15 11:31 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-14 9:51 Bruce Richardson
2017-08-14 9:51 ` [dpdk-dev] [RFCv2 01/40] build: initial hooks for using meson with DPDK Bruce Richardson
2017-08-14 9:51 ` [dpdk-dev] [RFCv2 02/40] build: create pkg-config file for DPDK Bruce Richardson
2017-08-14 9:51 ` [dpdk-dev] [RFCv2 03/40] build: build linuxapp EAL with meson and ninja Bruce Richardson
2017-08-14 9:51 ` [dpdk-dev] [RFCv2 04/40] build: add EAL support under BSD Bruce Richardson
2017-08-14 9:51 ` [dpdk-dev] [RFCv2 05/40] build: add core libraries to meson build system Bruce Richardson
2017-08-14 9:51 ` [dpdk-dev] [RFCv2 06/40] build: add i40e driver to meson build Bruce Richardson
2017-08-14 9:51 ` [dpdk-dev] [RFCv2 07/40] build: add pmdinfogen to build Bruce Richardson
2017-08-14 9:51 ` [dpdk-dev] [RFCv2 08/40] build: generate list of sources for pmdinfogen Bruce Richardson
2017-08-14 9:51 ` [dpdk-dev] [RFCv2 09/40] build: build i40e driver, including pmdinfo Bruce Richardson
2017-08-14 9:51 ` [dpdk-dev] [RFCv2 10/40] build: install usertools scripts Bruce Richardson
2017-08-14 9:51 ` [dpdk-dev] [RFCv2 11/40] build: simplify generation of pmd.c files Bruce Richardson
2017-08-14 9:51 ` [dpdk-dev] [RFCv2 12/40] build: generalize net driver build to higher level Bruce Richardson
2017-08-14 9:51 ` [dpdk-dev] [RFCv2 13/40] build: remove hard-coded enablement of vector driver Bruce Richardson
2017-08-14 9:51 ` [dpdk-dev] [RFCv2 14/40] build: add ixgbe driver to build Bruce Richardson
2017-08-14 9:51 ` [dpdk-dev] [RFCv2 15/40] build: set up standard deps for drivers Bruce Richardson
2017-08-14 9:51 ` [dpdk-dev] [RFCv2 16/40] build: add af_packet driver to build Bruce Richardson
2017-08-14 9:51 ` [dpdk-dev] [RFCv2 17/40] build: add pcap PMD support Bruce Richardson
2017-08-14 9:51 ` [dpdk-dev] [RFCv2 18/40] build: add symbol version map file support to libs Bruce Richardson
2017-08-14 9:51 ` [dpdk-dev] [RFCv2 19/40] build: build libraries in a loop for brevity Bruce Richardson
2017-08-14 9:51 ` [dpdk-dev] [RFCv2 20/40] build: version library .so files Bruce Richardson
2017-08-14 9:51 ` [dpdk-dev] [RFCv2 21/40] eal: add version information to meson build Bruce Richardson
2017-08-14 9:51 ` [dpdk-dev] [RFCv2 22/40] build: add mempool drivers to build Bruce Richardson
2017-08-14 9:51 ` [dpdk-dev] [RFCv2 23/40] build: add gro library to meson build Bruce Richardson
2017-08-14 9:51 ` [dpdk-dev] [RFCv2 24/40] build: tweak naming of pmd dependencies Bruce Richardson
2017-08-14 9:51 ` [dpdk-dev] [RFCv2 25/40] build: track driver include directories properly Bruce Richardson
2017-08-14 9:51 ` [dpdk-dev] [RFCv2 26/40] metrics: add metrics lib to meson build Bruce Richardson
2017-08-14 9:51 ` [dpdk-dev] [RFCv2 27/40] build: track dependencies recursively Bruce Richardson
2017-08-14 9:51 ` [dpdk-dev] [RFCv2 28/40] testpmd: compile testpmd with meson and ninja Bruce Richardson
2017-08-14 9:51 ` [dpdk-dev] [RFCv2 29/40] crypto/null: rename the version file to standard Bruce Richardson
2017-08-14 9:51 ` [dpdk-dev] [RFCv2 30/40] crypto/qat: remove dependency on ether library Bruce Richardson
2017-08-14 9:51 ` [dpdk-dev] [RFCv2 31/40] build: add cryptodev and some crypto drivers to build Bruce Richardson
2017-08-14 9:52 ` [dpdk-dev] [RFCv2 32/40] igb_uio: add igb_uio to meson build Bruce Richardson
2017-08-14 9:52 ` [dpdk-dev] [RFCv2 33/40] ip_frag: rename version file to standard name Bruce Richardson
2017-08-14 9:52 ` [dpdk-dev] [RFCv2 34/40] build: add most remaining libraries to meson build Bruce Richardson
2017-08-14 9:52 ` [dpdk-dev] [RFCv2 35/40] build: add packet framework libs " Bruce Richardson
2017-08-14 9:52 ` [dpdk-dev] [RFCv2 36/40] acl: add acl library " Bruce Richardson
2017-08-14 9:52 ` [dpdk-dev] [RFCv2 37/40] build: add ark and avp PMDs to build Bruce Richardson
2017-08-14 9:52 ` [dpdk-dev] [RFCv2 38/40] build: fix static library builds with base code Bruce Richardson
2017-08-14 9:52 ` [dpdk-dev] [RFCv2 39/40] build: fix driver dependencies for static builds Bruce Richardson
2017-08-14 9:52 ` [dpdk-dev] [RFCv2 40/40] examples: allow basic sample app build using pkg-config Bruce Richardson
2017-08-15 10:56 ` [dpdk-dev] [RFCv2 00/40] Building DPDK with meson and ninja Luca Boccassi
2017-08-15 11:31 ` Bruce Richardson [this message]
2017-08-17 14:10 ` Marco Varlese
2017-08-17 15:25 ` Luca Boccassi
2017-08-18 8:35 ` Bruce Richardson
2017-08-18 8:52 ` Marco Varlese
2017-08-18 9:17 ` Marco Varlese
2017-08-18 9:33 ` Luca Boccassi
[not found] ` <1502983469.31476.3.camel@gmail.com>
2017-08-18 8:00 ` Marco Varlese
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=20170815113134.GA16284@bricha3-MOBL3.ger.corp.intel.com \
--to=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=luca.boccassi@gmail.com \
/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).