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 EC308A056A for ; Thu, 11 Mar 2021 00:36:36 +0100 (CET) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id C30FB406A2; Thu, 11 Mar 2021 00:36:36 +0100 (CET) Received: from wout1-smtp.messagingengine.com (wout1-smtp.messagingengine.com [64.147.123.24]) by mails.dpdk.org (Postfix) with ESMTP id 2106940689; Thu, 11 Mar 2021 00:36:35 +0100 (CET) Received: from compute2.internal (compute2.nyi.internal [10.202.2.42]) by mailout.west.internal (Postfix) with ESMTP id 905053185; Wed, 10 Mar 2021 18:36:33 -0500 (EST) Received: from mailfrontend2 ([10.202.2.163]) by compute2.internal (MEProxy); Wed, 10 Mar 2021 18:36:33 -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= TQkftV5CYKA9sQgpw29/WInjXCa8g5OK1z9SyN36gsQ=; b=bD6A2XlBwmc3xVAs zOKowiYdhCe1L7WPNJFVWKFmxn/MnYKFOM6amw4UN7CCj/6jdvUwq7ul7K8ovIPR KgPV+H+B2x52k8f+/PNjOxeub4CLzp4TQKM7z/luYooIrNTVLpfwIQfOZln8+ibv 9F6394uCI3SpqN44UA24BKib3M43YYvsYePksua3u2nvYlHhiIvDpF/5yk3XNPb5 Y14O0Scn99PU3S/4dPenWA83ZvbLaQ1/mVq/h6q1rUzV3jpea8+6SJ7fKTvyOnFU oevRr/nv+pZmVpaXh8MaqmckOd+RqNU0lrcbJAxgQFFQ3gTBuBsdEdQqrXeVvzXh BLK9kw== 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=TQkftV5CYKA9sQgpw29/WInjXCa8g5OK1z9SyN36g sQ=; b=vcH7SvQWkfRHACzQXisMG0M6Hlc2i9aFBITFrzjyQE24UF1RodDERgMMK XWtWwZiPbj1AwGEbaf2YKl2kYWvYDcPwdjHV826mvHU4zykyYPV9qHqRIP6625mI 9UImxKSEcsGwDoTf8h/qRJh9gb7UT5OigsiiBgn+HQ8e1wmOfB4e9KdIXNweXopu PBu6mvmRMqShsiHC4B55NpMtldjAEfZcIB/9WQ12VMJkDJXaI4AtsXkiSuiX7fHZ jpqYRtr3GYQ0B9eDHX1wtIR7T2bqu3FNovtyOyCJnF8DdNRiaNo/vvJnvHPciWzQ w29vLwrYDX4xQlMYU2NsOQpLqYztQ== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduledrudduledguddvucetufdoteggodetrfdotf 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 1D7BE1080054; Wed, 10 Mar 2021 18:36:32 -0500 (EST) From: Thomas Monjalon To: Jinkun Geng Cc: Stephen Hemminger , ci@dpdk.org, "users@dpdk.org" Date: Thu, 11 Mar 2021 00:36:29 +0100 Message-ID: <11457967.n7LkdMVPTe@thomas> In-Reply-To: References: <20210308183117.627af0e8@hermes.local> 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" 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?