From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Monjalon Subject: Re: Projects depending on make (versus meson) Date: Tue, 08 Jan 2019 11:44:03 +0100 Message-ID: <3581820.WYqOYd8h7C@xps> References: <20190107102118.037f141a@hermes.lan> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7Bit Cc: dev@dpdk.org, Bruce Richardson To: Stephen Hemminger Return-path: Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) by dpdk.org (Postfix) with ESMTP id 560531B4A1 for ; Tue, 8 Jan 2019 11:44:07 +0100 (CET) In-Reply-To: <20190107102118.037f141a@hermes.lan> List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" 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. Anyway, as you mentioned above, better to switch to meson.