From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ming Zhao Subject: Build DPDK with Google bazel Date: Sat, 23 May 2015 17:53:27 -0700 Message-ID: Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 To: dev@dpdk.org Return-path: Received: from mail-wg0-f46.google.com (mail-wg0-f46.google.com [74.125.82.46]) by dpdk.org (Postfix) with ESMTP id 7CDFE376E for ; Sun, 24 May 2015 02:53:27 +0200 (CEST) Received: by wgbgq6 with SMTP id gq6so46691283wgb.3 for ; Sat, 23 May 2015 17:53:27 -0700 (PDT) List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" 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!