From: Thomas Monjalon <thomas@monjalon.net>
To: Jinkun Geng <gjk1994@stanford.edu>
Cc: Stephen Hemminger <stephen@networkplumber.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:36:29 +0100 [thread overview]
Message-ID: <11457967.n7LkdMVPTe@thomas> (raw)
In-Reply-To: <BYAPR02MB4613D6F787B266AE82C66270D4929@BYAPR02MB4613.namprd02.prod.outlook.com>
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?
next prev parent reply other threads:[~2021-03-10 23:36 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 ` Thomas Monjalon [this message]
2021-03-10 23:42 ` [dpdk-users] [dpdk-ci] " 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=11457967.n7LkdMVPTe@thomas \
--to=thomas@monjalon.net \
--cc=ci@dpdk.org \
--cc=gjk1994@stanford.edu \
--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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).