From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id 6845EA056A for ; Thu, 11 Mar 2021 01:06:44 +0100 (CET) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 4718C22A63E; Thu, 11 Mar 2021 01:06:44 +0100 (CET) Received: from wout1-smtp.messagingengine.com (wout1-smtp.messagingengine.com [64.147.123.24]) by mails.dpdk.org (Postfix) with ESMTP id 3BCD3406A2; Thu, 11 Mar 2021 01:06:43 +0100 (CET) Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.west.internal (Postfix) with ESMTP id 0E6BE3109; Wed, 10 Mar 2021 19:06:41 -0500 (EST) Received: from mailfrontend1 ([10.202.2.162]) by compute4.internal (MEProxy); Wed, 10 Mar 2021 19:06:42 -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=fm3; bh= mbHca0j/2EWuZhlrsQFx+8BqDFohf6rkcreVkrz2R74=; b=G+I6PfJM4gFw5cxs HO/igRvXdVNoc7pKN/DTWVWwKxc28OHIbyVarK238gkjMKAfMYVxMBr44OrY7Bk5 bT2wuX9RJV/j+YV2fFcnHOYn4k4Snf7e12JNIHO+3vTfT0RVFc268sU/OXrTSsPO eWHOmq8MDZlWvcH/aihnx9y9iVpeFa3RL05DngZyXQOrO8U9Pndalhz3E2uCA3YR /8jMt46Ix3Bj2WljDVwNVr6OTlQuIFYMmJj6vzAWVhgU2h7L9mccQSfck6Kpk1/n ADVfmA0RjGCrAM5TWGbDV1PIwf/olY3bha1iMd7XJfwLCp6wZgYpm+gYLRa72uuy HONcyg== 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=fm2; bh=mbHca0j/2EWuZhlrsQFx+8BqDFohf6rkcreVkrz2R 74=; b=UsWnn1c7Pxd4xwmxPf2qCjfnFGe9BkTMzqP1yaFq/1Dobej6qKv6re5Bj 3397YMiz4ek1+n8k1ymOl+OacvMZpv5XxXP2cWWyV/XQLBBDrXrYPEgLNkDKcrvy KL7AWHpB5RGyatYKjRVqYsDweQGFrDcU+Q390ePbD4QG1xSMZ0eqNv9HNZcBqFql uIjCiCDgkYeHTH7LahJasgyHFo1NJBS0qeFDgqs7crT2cw+rUNMyoi/4PjljSDTd jL5Be/QaqmxfyV1vPxRYgX+NORzh4peVlEA2+SfWJU88a0Pgc9f/gkAgKvnn/ssw SQlcEAu3g5JT73zAY3zbgeorfiicw== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduledrudduledgudejucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhephffvufffkfgjfhgggfgtsehtufertddttddvnecuhfhrohhmpefvhhhomhgr shcuofhonhhjrghlohhnuceothhhohhmrghssehmohhnjhgrlhhonhdrnhgvtheqnecugg ftrfgrthhtvghrnhepgeejfffhhfeghfetveffgeffteelveekhffghfefgedvleeuveet fffgudelvefhnecuffhomhgrihhnpehgihhthhhusgdrtghomhenucfkphepjeejrddufe egrddvtdefrddukeegnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghi lhhfrhhomhepthhhohhmrghssehmohhnjhgrlhhonhdrnhgvth 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 8A443240057; Wed, 10 Mar 2021 19:06:40 -0500 (EST) From: Thomas Monjalon To: Jinkun Geng Cc: Stephen Hemminger , "ci@dpdk.org" , "users@dpdk.org" Date: Thu, 11 Mar 2021 01:06:38 +0100 Message-ID: <3003733.ML7hmrJNhH@thomas> In-Reply-To: References: <11457967.n7LkdMVPTe@thomas> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-ci] [dpdk-users] Integration of DPDK into Bazel X-BeenThere: ci@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK CI discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: ci-bounces@dpdk.org Sender: "ci" 11/03/2021 00:42, Jinkun Geng: > For any project using bazel, if we want to use DPDK, then we need to compile DPDK stuff into bazel by ourselves. It is not a trivial thing and the bazelment (https://github.com/bazelment/dpdk) guys have spent much effort extracting the core files in DPDK and write the BUILD files for DPDK. But now it seems they have stopped maintaining that repo since DPDK 16.04. Even in that version, it has some runtime failure when we use DPDK in our bazel project. Sorry I don't know bazel. Do you mean all components must be built inside bazel? You are not able to call meson/ninja commands from bazel? How do you do with other libraries? Does bazel usually reimplement what is packaged with autotools? > ________________________________ From: Thomas Monjalon > 09/03/2021 05:11, Jinkun Geng: > > Too bad. :< > > Why is it too bad? > How the choice of an internal build system > can affect other projects? > > > From: Stephen Hemminger > > On Tue, 9 Mar 2021 01:32:16 +0000 > > Jinkun Geng wrote: > > > > > Hi, all. > > > Since bazel building system is becoming more and more popular, sometimes we need to integrate DPDK library into a bazel project. However, it seems there is no much support for bazel from DPDK community. > > Why the DPDK community would support building with Bazel? > What is the benefit? > Bazel projects cannot just link with DPDK using pkg-config? > > > > > The only support at https://github.com/bazelment/dpdk has been outdated. Based on our experience, it can only compile successfully with dpdk-16.04 (i.e. the bazel-16.04 branch). Now DPDK has developed to DPDK 21.02, but the bazel support fails to catch up. > > > > > > It would be great if the experts in DPDK community can provide some portable BUILD files to facilitate the integration of the newest DPDK into bazel project (just like bazelment). After all, writing the bazel files can be really challenging, especially if we do not have a very deep understanding of the whole DPDK codes. > > > > > > Jinkun > > > > DPDK is on meson now. The core team is unlikely to change build systems again. > > DPDK supports library standards for compiling, installing and linking. > What else is needed?