From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga12.intel.com (mga12.intel.com [192.55.52.136]) by dpdk.org (Postfix) with ESMTP id B82FF1B3A5 for ; Tue, 8 Jan 2019 11:55:43 +0100 (CET) X-Amp-Result: UNKNOWN X-Amp-Original-Verdict: FILE UNKNOWN X-Amp-File-Uploaded: False Received: from orsmga006.jf.intel.com ([10.7.209.51]) by fmsmga106.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 08 Jan 2019 02:55:42 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.56,453,1539673200"; d="scan'208";a="106550630" Received: from bricha3-mobl.ger.corp.intel.com ([10.237.221.54]) by orsmga006.jf.intel.com with SMTP; 08 Jan 2019 02:55:40 -0800 Received: by (sSMTP sendmail emulation); Tue, 08 Jan 2019 10:55:37 +0000 Date: Tue, 8 Jan 2019 10:55:36 +0000 From: Bruce Richardson To: Thomas Monjalon Cc: Stephen Hemminger , dev@dpdk.org Message-ID: <20190108105535.GA17732@bricha3-MOBL.ger.corp.intel.com> References: <20190107102118.037f141a@hermes.lan> <3581820.WYqOYd8h7C@xps> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3581820.WYqOYd8h7C@xps> Organization: Intel Research and Development Ireland Ltd. User-Agent: Mutt/1.10.1 (2018-07-13) Subject: Re: [dpdk-dev] Projects depending on make (versus meson) 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, 08 Jan 2019 10:55:44 -0000 On Tue, Jan 08, 2019 at 11:44:03AM +0100, Thomas Monjalon wrote: > 07/01/2019 19:21, Stephen Hemminger: > > I recently bumped into NFF-go which probably will have problems with meson build. > > It puts dpdk and pktgen-dpdk in as git submodules and then builds it all together > > with Go environment. > > You mean they must switch to meson and use DPDK discovery with pkg-config? > Do you see any blocker? > > > The current model is a nuisance because can't get Mellanox drivers for Azure by > > default. > > In the make build system, some libraries (like Mellanox drivers) must be > explicitly enabled by modifying the .config file before running make. > There should be a hook in the app build system to allow some tuning. One thing I've been considering for our meson build system, is possibly adding in a config option to explicitly request specific drivers to be built and error out if they cannot be. Right now, it's all based on what is available - there is no way to tell meson to error out the config if the dependencies for the Mellanox drivers, or the QAT crypto drivers are missing. Thoughts (and patches :-)) welcome. /Bruce