DPDK usage discussions
 help / color / mirror / Atom feed
From: Jinkun Geng <gjk1994@stanford.edu>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: "users@dpdk.org" <users@dpdk.org>, "ci@dpdk.org" <ci@dpdk.org>
Subject: Re: [dpdk-users] Integration of DPDK into Bazel
Date: Tue, 9 Mar 2021 04:11:13 +0000
Message-ID: <BYAPR02MB4613D6F787B266AE82C66270D4929@BYAPR02MB4613.namprd02.prod.outlook.com> (raw)
In-Reply-To: <20210308183117.627af0e8@hermes.local>

Too bad. :<
________________________________
From: Stephen Hemminger <stephen@networkplumber.org>
Sent: Monday, March 8, 2021 6:31 PM
To: Jinkun Geng <gjk1994@stanford.edu>
Cc: users@dpdk.org <users@dpdk.org>; ci@dpdk.org <ci@dpdk.org>
Subject: Re: [dpdk-users] Integration of DPDK into Bazel

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. 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.

  reply	other threads:[~2021-03-09  4:11 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-09  1:32 Jinkun Geng
2021-03-09  2:31 ` Stephen Hemminger
2021-03-09  4:11   ` Jinkun Geng [this message]
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
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:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

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

  git send-email \
    --in-reply-to=BYAPR02MB4613D6F787B266AE82C66270D4929@BYAPR02MB4613.namprd02.prod.outlook.com \
    --to=gjk1994@stanford.edu \
    --cc=ci@dpdk.org \
    --cc=stephen@networkplumber.org \
    --cc=users@dpdk.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* 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 \
		users@dpdk.org
	public-inbox-index users

Example config snippet for mirrors.
Newsgroup available over NNTP:
	nntp://inbox.dpdk.org/inbox.dpdk.users


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