From mboxrd@z Thu Jan 1 00:00:00 1970 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) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:date:message-id:subject:from:to :content-type; bh=jL9DMkNU0wOBXJJPGuYhMP7/s++ypou6/Mc3GFGkNI4=; b=Ha7lFcnGszSte3C+62ZCnLugldGRWxdXSrrBxC8hr3UbaLPNBfWg4ckw43pCFO1y6x eeincz5ECTWqkZcLukeMQkUrNaydN3dF1fvijvmkCHoqSyEIwq7Xd8isJDmV7wEeA4cU OaW6jenvq5jNKD97jReXKAhO7dsVMnt3+qsEaelg5mRBvYcNvxMXocI9dbX1jXMcIbsn CuA9tVFrCcr7hYEPE/B0JUtYyA5KKjloGehb3lvNvypfH67Ax/37unpK93rdujpqeGcS H1gnyJhhZBJUFEfIKTCK63EIAj9TZKkNbsG0xjg5zd2GkZDTaOvET/AkiGymXQq3l/kO t6Jw== X-Gm-Message-State: ALoCoQn7rqoc3pKRxcIh7rhEVldPsDhJJNOZFvUNgvLOWJYFiAKfU8YEEzOTYUBJAXaB/1UR3/5Z MIME-Version: 1.0 X-Received: by 10.194.157.168 with SMTP id wn8mr12990688wjb.79.1432428807343; Sat, 23 May 2015 17:53:27 -0700 (PDT) Received: by 10.28.43.134 with HTTP; Sat, 23 May 2015 17:53:27 -0700 (PDT) Date: Sat, 23 May 2015 17:53:27 -0700 Message-ID: From: Ming Zhao To: dev@dpdk.org Content-Type: text/plain; charset=UTF-8 Subject: [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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 24 May 2015 00:53:27 -0000 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!