From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga02.intel.com (mga02.intel.com [134.134.136.20]) by dpdk.org (Postfix) with ESMTP id 61DE52C17; Tue, 24 Apr 2018 16:36:48 +0200 (CEST) X-Amp-Result: UNSCANNABLE X-Amp-File-Uploaded: False Received: from orsmga003.jf.intel.com ([10.7.209.27]) by orsmga101.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 24 Apr 2018 07:36:46 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.49,323,1520924400"; d="scan'208";a="45673704" Received: from bricha3-mobl.ger.corp.intel.com ([10.237.221.51]) by orsmga003.jf.intel.com with SMTP; 24 Apr 2018 07:36:44 -0700 Received: by (sSMTP sendmail emulation); Tue, 24 Apr 2018 15:36:43 +0100 Date: Tue, 24 Apr 2018 15:36:42 +0100 From: Bruce Richardson To: dev@dpdk.org Cc: techboard@dpdk.org Message-ID: <20180424143642.GA17328@bricha3-MOBL.ger.corp.intel.com> References: <20180424123255.204330-1-bruce.richardson@intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20180424123255.204330-1-bruce.richardson@intel.com> Organization: Intel Research and Development Ireland Ltd. User-Agent: Mutt/1.9.4 (2018-02-28) Subject: Re: [dpdk-dev] [PATCH] devtools: add test script for meson builds X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 24 Apr 2018 14:36:51 -0000 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 > --- 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