DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ming Zhao <mzhao@luminatewireless.com>
To: dev@dpdk.org
Subject: [dpdk-dev] Build DPDK with Google bazel
Date: Sat, 23 May 2015 17:53:27 -0700	[thread overview]
Message-ID: <CAN7Vozwt5XnqvbuXExAn6APxWTPDbn8BFDqx3nWhtwiMUF6c+w@mail.gmail.com> (raw)

bazel(http://bazel.io) is the open sourced version of Google build
tool, and it has proved itself is a nice solution for monolithic
server side development. In our company, we use both to build our
products and it greatly reduced the hurdle of rolling out any change
because we put the whole DPDK source code into tree and the build
process can easily produce final binaries at any point(i.e. we can put
a fix to DPDK code and the build process will always produce
up-to-date binary based on the change).

We pushed all our changes to github in "bazel"
branch(https://github.com/mzhaom/dpdk/tree/bazel) in case any one
wants to try it. At the moment, due to the complexity of setting up
bazel BUILD files to handle different compilation settings, we are not
actively pursuing to integrate these changes back to upstream. But
I'll be happy to answer any question and provide help in case anyone
wants to do so.

Thanks!

             reply	other threads:[~2015-05-24  0:53 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-24  0:53 Ming Zhao [this message]
2015-05-26 15:01 ` Stephen Hemminger

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=CAN7Vozwt5XnqvbuXExAn6APxWTPDbn8BFDqx3nWhtwiMUF6c+w@mail.gmail.com \
    --to=mzhao@luminatewireless.com \
    --cc=dev@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).