DPDK usage discussions
 help / color / mirror / Atom feed
From: Jinkun Geng <gjk1994@stanford.edu>
To: Thomas Monjalon <thomas@monjalon.net>
Cc: Stephen Hemminger <stephen@networkplumber.org>,
	"ci@dpdk.org" <ci@dpdk.org>, "users@dpdk.org" <users@dpdk.org>
Subject: Re: [dpdk-users] [dpdk-ci]  Integration of DPDK into Bazel
Date: Thu, 11 Mar 2021 00:17:23 +0000
Message-ID: <BYAPR02MB4613678609D6ED05586BAEE2D4909@BYAPR02MB4613.namprd02.prod.outlook.com> (raw)
In-Reply-To: <3003733.ML7hmrJNhH@thomas>

Do you mean all components must be built inside bazel?
>> Sort of. We have a project that is built on bazel. Now, we need to use the core functions of DPDK to replace the network primitives in our project, so that we can improve the performance of our project.

You are not able to call meson/ninja commands from bazel?
>> I have found any examples using meson inside bazel. According to my understanding, Bazel and meson are two parallel building systems and I haven't seen anyone could use them together.

How do you do with other libraries? Does bazel usually reimplement what is packaged with autotools?
>> That is the reason why https://github.com/bazelment exists. If some libraries are popular and do not support bazel, then these guys will help generate some modified version of these libraries, so that developers can integrate the library into bazel. It is not completely reimplementation, but it indeed needs much extraction to adapt the previous library so that it can be used in bazel.
Unfortunately, these guys stop supporting DPDK atop bazel now.

From: Thomas Monjalon <thomas@monjalon.net>
Sent: Wednesday, March 10, 2021 4:06 PM
To: Jinkun Geng <gjk1994@stanford.edu>
Cc: Stephen Hemminger <stephen@networkplumber.org>; ci@dpdk.org <ci@dpdk.org>; users@dpdk.org <users@dpdk.org>
Subject: Re: [dpdk-ci] [dpdk-users] Integration of DPDK into Bazel

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 <thomas@monjalon.net>
> 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 <stephen@networkplumber.org>
> > On Tue, 9 Mar 2021 01:32:16 +0000
> > Jinkun Geng <gjk1994@stanford.edu> 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?

  reply	other threads:[~2021-03-11  0:17 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-09  1:32 [dpdk-users] " Jinkun Geng
2021-03-09  2:31 ` Stephen Hemminger
2021-03-09  4:11   ` Jinkun Geng
2021-03-10 23:36     ` [dpdk-users] [dpdk-ci] " Thomas Monjalon
2021-03-10 23:42       ` Jinkun Geng
2021-03-11  0:06         ` Thomas Monjalon
2021-03-11  0:17           ` Jinkun Geng [this message]
2021-03-11  8:07             ` Thomas Monjalon

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=BYAPR02MB4613678609D6ED05586BAEE2D4909@BYAPR02MB4613.namprd02.prod.outlook.com \
    --to=gjk1994@stanford.edu \
    --cc=ci@dpdk.org \
    --cc=stephen@networkplumber.org \
    --cc=thomas@monjalon.net \
    --cc=users@dpdk.org \


* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

DPDK usage discussions

This inbox may be cloned and mirrored by anyone:

	git clone --mirror https://inbox.dpdk.org/users/0 users/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 users users/ https://inbox.dpdk.org/users \
	public-inbox-index users

Example config snippet for mirrors.
Newsgroup available over NNTP:

AGPL code for this site: git clone https://public-inbox.org/public-inbox.git