DPDK patches and discussions
 help / color / mirror / Atom feed
From: Bruce Richardson <bruce.richardson@intel.com>
To: dev@dpdk.org
Cc: techboard@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] devtools: add test script for meson builds
Date: Tue, 24 Apr 2018 15:36:42 +0100	[thread overview]
Message-ID: <20180424143642.GA17328@bricha3-MOBL.ger.corp.intel.com> (raw)
In-Reply-To: <20180424123255.204330-1-bruce.richardson@intel.com>

On Tue, Apr 24, 2018 at 01:32:55PM +0100, Bruce Richardson wrote:
> To simplify testing with the meson and ninja builds, we can add a script
> to set up and do multiple builds. Currently this script sets up:
> 
> * clang and gcc builds
> * builds using static and shared linkage for binaries (libs are always
>    built as both)
> * a build using the lowest instruction-set level for x86 (-march=nehalem)
> * cross-builds for each cross-file listed in config/arm
> 
> Each build is configured in a directory ending in *-build, and then for
> the build stage, we just call ninja in each directory in turn. [i.e. we
> assume every directory ending in "-build" is a meson build, which is
> probably an ok assumption].
> 
> Signed-off-by: Bruce Richardson <bruce.richardson@intel.com>
> ---

By way of update, below is the list I have of open items for the meson
build of DPDK. While it may seems quite a list, it also shows the amount of
material we have in DPDK itself!

While I plan do a number of these, e.g. doing up the documentation on
meson, it would be great if people, particularly driver maintainers, could
look to add support for the missing items in the next release of DPDK. The
biggest gap to close is getting more of the NIC drivers supported.

Please send me on any corrections, too.

Regards,
/Bruce

Gaps for meson build:

- Build of html/pdf docs
- Documentation updates
	- Programmers guide update about the build system itself and
	    it's way of working
	- GSG updates on using meson
- Improved support for unit tests (e.g. benchmark vs regular tests)
- Vector driver support on ARM for ixgbe and i40e
- Map file checking for experimental tags.
- ICC support
- 32-bit compilation

- Library compilation completeness:
	- app - Done
	- drivers/baseband
		 null
		 turbo_sw
	- drivers/bus - Done
	- drivers/crypto
		- aesni_gcm
		- aesni_mb
		- armv8
		- kasumi
		- mrvl
		- scheduler
		- snow3g
		- zuc
	- drivers/event
		- opdl
	- drivers/mempool - Done
	- drivers/net
		- ark
		- avf
		- avp
		- bnx2x
		- bnxt
		- cxgbe
		- ena
		- failsafe
		- kni
		- liquidio
		- mlx4
		- mlx5
		- mvpp2
		- nfp
		- qede
		- softnic
		- szedata2
		- tap
		- vdev_netvsc
		- vhost
		- vmxnet3
	- drivers/raw - [some patches submitted]
	- examples/
		- multi_process
		- netmap_compat
		- performance-thread
		- quota_watermark
		- server_node_efd
		- vm_power_manager
	- kernel/
		 kni
	- lib/ - Done
	- test/
		- cmdline_test
		- test-acl
		- test-pipeline

  reply	other threads:[~2018-04-24 14:36 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-24 12:32 Bruce Richardson
2018-04-24 14:36 ` Bruce Richardson [this message]
2018-04-24 14:38 ` Bruce Richardson
2018-05-25 14:51 ` [dpdk-dev] [PATCH v2] " Thomas Monjalon
2018-05-25 15:18   ` Bruce Richardson
2018-05-26  9:32     ` Thomas Monjalon
2018-05-28  9:33       ` Bruce Richardson
2018-05-28 10:26         ` Thomas Monjalon
2018-05-28 13:20           ` Bruce Richardson
2018-05-29 10:38             ` Thomas Monjalon
2018-05-29 10:59               ` Bruce Richardson
2018-05-26  9:54 ` [dpdk-dev] [PATCH v3] " Thomas Monjalon
2018-05-26 11:21 ` [dpdk-dev] [PATCH v4] " Thomas Monjalon
2018-05-28  9:39   ` Bruce Richardson
2018-05-29 14:42 ` [dpdk-dev] [PATCH v5] " Thomas Monjalon
2018-05-29 14:58   ` Richardson, Bruce
2018-05-29 15:37     ` 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=20180424143642.GA17328@bricha3-MOBL.ger.corp.intel.com \
    --to=bruce.richardson@intel.com \
    --cc=dev@dpdk.org \
    --cc=techboard@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).