From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <stephen@networkplumber.org>
Received: from mail-pd0-f175.google.com (mail-pd0-f175.google.com
 [209.85.192.175]) by dpdk.org (Postfix) with ESMTP id BF1A29A9E
 for <dev@dpdk.org>; Tue, 26 May 2015 17:01:30 +0200 (CEST)
Received: by pdbqa5 with SMTP id qa5so92709688pdb.0
 for <dev@dpdk.org>; Tue, 26 May 2015 08:01:30 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=1e100.net; s=20130820;
 h=x-gm-message-state:date:from:to:cc:subject:message-id:in-reply-to
 :references:mime-version:content-type:content-transfer-encoding;
 bh=3i2sJnrk3MIb8X0P1dz34rKiWoWW8GrmjmmqzdIrtTE=;
 b=mvbBlh0TDfCW0y5NuspE84neDLXa18DO/vVG7M8fO06sqR4PLH5+X47m4fSgYUohDd
 E5i3aFchGAYf5izaTkR7qgbU2v4JYNfiAlRqi0tGbRiFjqteBsvfB/4sjlB5591K93DR
 H9Rv6+XEEbND+BYygNVR5hcInq+f2HMg3K46e7PTzrAis8W+vaTnZOQ1wK5mQhRu4Sjv
 3xTdYMajAbGRX39wkCQytBRQUO1XwXZOmU0Ml5K85FGKGnE1SInEYId2X+zr+z/U7uL1
 IGIgtyjb4E08ot6SHf1tyodNimRWjMaM8MNZaGIr/qh4lHl1FRJBXEE3rdTPpR93FaSk
 7R9w==
X-Gm-Message-State: ALoCoQkmqMShXTV0+MbtMoAzisG7xkKWsfE8lwjWdATuz2ds+Csz2SGsPckEBYNSNx4kh8T0ld7g
X-Received: by 10.68.57.170 with SMTP id j10mr50106306pbq.150.1432652490128;
 Tue, 26 May 2015 08:01:30 -0700 (PDT)
Received: from urahara (static-50-53-82-155.bvtn.or.frontiernet.net.
 [50.53.82.155])
 by mx.google.com with ESMTPSA id ym6sm13433085pac.32.2015.05.26.08.01.29
 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128);
 Tue, 26 May 2015 08:01:29 -0700 (PDT)
Date: Tue, 26 May 2015 08:01:33 -0700
From: Stephen Hemminger <stephen@networkplumber.org>
To: Ming Zhao <mzhao@luminatewireless.com>
Message-ID: <20150526080133.7be30c9d@urahara>
In-Reply-To: <CAN7Vozwt5XnqvbuXExAn6APxWTPDbn8BFDqx3nWhtwiMUF6c+w@mail.gmail.com>
References: <CAN7Vozwt5XnqvbuXExAn6APxWTPDbn8BFDqx3nWhtwiMUF6c+w@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] Build DPDK with Google bazel
X-BeenThere: dev@dpdk.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: patches and discussions about DPDK <dev.dpdk.org>
List-Unsubscribe: <http://dpdk.org/ml/options/dev>,
 <mailto:dev-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://dpdk.org/ml/archives/dev/>
List-Post: <mailto:dev@dpdk.org>
List-Help: <mailto:dev-request@dpdk.org?subject=help>
List-Subscribe: <http://dpdk.org/ml/listinfo/dev>,
 <mailto:dev-request@dpdk.org?subject=subscribe>
X-List-Received-Date: Tue, 26 May 2015 15:01:31 -0000

On Sat, 23 May 2015 17:53:27 -0700
Ming Zhao <mzhao@luminatewireless.com> wrote:

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

Thanks for doing this, but please don't try and convert us.

As an experience Unix/Linux person, new glitzy build systems are kind
of a sore point. If you can make it work for you great, but let's keep
the DPDK as simple as possible.