From mboxrd@z Thu Jan 1 00:00:00 1970 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) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id B2514220A5; Tue, 8 Jan 2019 05:44:06 -0500 (EST) Received: from mailfrontend2 ([10.202.2.163]) by compute1.internal (MEProxy); Tue, 08 Jan 2019 05:44:06 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= from:to:cc:subject:date:message-id:in-reply-to:references :mime-version:content-transfer-encoding:content-type; s=mesmtp; bh=FWlgCLNuWXmA8KV/VYHYsJVPjcye9wLqpW/hxUEpz4Y=; b=LkceE/YBKzvI EaXLylaoj6XpAAdhvgDQ6BRFeHADla/+vzf9LFbegB77+sTJD0FjQ2CPIXAhvHxb ZmDIOaztmiVFfwhnLREvALbl+B006f8J2sOgFGHwrM0QHU7jfgeydZWB0GBjNDIT FVIJAZi+CE/hmXsiPd0Dljp7Y+y7Mwo= DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm1; bh=FWlgCLNuWXmA8KV/VYHYsJVPjcye9wLqpW/hxUEpz 4Y=; b=qMOY5m5j7RS+zbbFnO8gDK5nzpa5yuT+PUHLRYbo6qOXV2NfxRBZDCY9r Ytt4PMDToQMSCq5G6wRcEQLq+tayu9k8tOGVO6sWlFhj/IA+x8z9WdvBBDYJoXwu S64xmEwLHvusRzUEMqiwyXHyIoLNJ+6v4AB4eToLjwM28+OULd/oCvlPBNdiIuK8 qWrhtFgcQhKSr4P6Otkk5KS0SxBHoYBszR8jevMfiCKP/Q8so7UwyfiRzUUi6ogI Da4L1zFgUkmnO3ttTKvPk+PNaevTMBkz5HhSDeYeZC23BPyhQH7rWnHK6dppxK+3 MR0VWVe3K6m60vOVOZEM5tDVitKcA== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedtledrvdelgddujeculddtuddrgedtkedrtddtmd cutefuodetggdotefrodftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpqfhuthen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhephffvufffkfgjfhgggfgtsehtufertddttddvnecuhfhrohhmpefvhhhomhgr shcuofhonhhjrghlohhnuceothhhohhmrghssehmohhnjhgrlhhonhdrnhgvtheqnecukf hppeejjedrudefgedrvddtfedrudekgeenucfrrghrrghmpehmrghilhhfrhhomhepthhh ohhmrghssehmohhnjhgrlhhonhdrnhgvthenucevlhhushhtvghrufhiiigvpedt X-ME-Proxy: Received: from xps.localnet (184.203.134.77.rev.sfr.net [77.134.203.184]) by mail.messagingengine.com (Postfix) with ESMTPA id 0AA91100E5; Tue, 8 Jan 2019 05:44:04 -0500 (EST) From: Thomas Monjalon To: Stephen Hemminger Cc: dev@dpdk.org, Bruce Richardson Date: Tue, 08 Jan 2019 11:44:03 +0100 Message-ID: <3581820.WYqOYd8h7C@xps> In-Reply-To: <20190107102118.037f141a@hermes.lan> References: <20190107102118.037f141a@hermes.lan> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" 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:44:07 -0000 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.