From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752766AbbADPvE (ORCPT ); Sun, 4 Jan 2015 10:51:04 -0500 Received: from mx1.redhat.com ([209.132.183.28]:42405 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752630AbbADPvB (ORCPT ); Sun, 4 Jan 2015 10:51:01 -0500 Date: Sun, 4 Jan 2015 16:49:43 +0100 From: Jiri Olsa To: Ingo Molnar Cc: Jiri Olsa , linux-kernel@vger.kernel.org, Adrian Hunter , Alexis Berlemont , Andi Kleen , Anton Blanchard , Arnaldo Carvalho de Melo , Borislav Petkov , Borislav Petkov , Cody P Schafer , Corey Ashford , David Ahern , Florian Fainelli , Frederic Weisbecker , Jean Pihet , Mark Salter , Namhyung Kim , Paul Mackerras , Peter Zijlstra , Sam Ravnborg , Stephane Eranian , Sukadev Bhattiprolu , Will Deacon Subject: Re: [RFC/PATCHSET 00/30] perf tools: New build framework Message-ID: <20150104154943.GA22707@krava.brq.redhat.com> References: <1420212972-21595-1-git-send-email-jolsa@kernel.org> <20150102173612.GA5941@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20150102173612.GA5941@gmail.com> User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, Jan 02, 2015 at 06:36:12PM +0100, Ingo Molnar wrote: > > * Jiri Olsa wrote: > > > [...] The basic idea is the same as in kbuild system, with some > > minor changes to allow for multiple binaries build definitions. > > > tools/perf/Build | 48 ++ > > tools/perf/Build.include | 75 ++++ > > tools/perf/Documentation/Build | 123 +++++ > > tools/perf/Makefile.build | 122 +++++ > > tools/perf/Makefile.perf | 566 +++--------------------- > > > 47 files changed, 827 insertions(+), 541 deletions(-) > > Even the diffstat looks pretty good: only a modest line count > increase. > > It would be useful to put this (and other build features - such > as features/parallelisation support) into tools/kbuild/ though, > so that other tooling can make easy use of it as well. For > example tools/kvm/ (an external project) started off with an > earlier version of the perf build system. right, I'll put it in tools/build.. looks like the tools/lib/* could use it, probably others as well thanks, jirka > > Sharing that would make quite a bit of sense, as tooling (and > most user-space project) build systems are usually have pretty > poor quality. > > Thanks, > > Ingo