From: Borislav Petkov <bp@amd64.org>
To: Ingo Molnar <mingo@kernel.org>
Cc: Ingo Molnar <mingo@elte.hu>,
Arnaldo Carvalho de Melo <acme@infradead.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 0/2] tools: Add a toplevel Makefile
Date: Mon, 26 Mar 2012 17:41:32 +0200 [thread overview]
Message-ID: <20120326154132.GJ32090@aftab> (raw)
In-Reply-To: <20120326151432.GA8527@gmail.com>
On Mon, Mar 26, 2012 at 05:14:32PM +0200, Ingo Molnar wrote:
>
> * Borislav Petkov <bp@amd64.org> wrote:
>
> > On Sat, Mar 24, 2012 at 08:44:12AM +0100, Ingo Molnar wrote:
> > > Could this also be accessible via 'make tools' in the toplevel
> > > Makefile?
> > >
> > > I'd love to be able to type:
> > >
> > > make -j tools perf install
> >
> > Well,
> >
> > you could do
> >
> > $ make -j -C tools perf
>
> Arguably I could also type:
>
> cd tools/perf; make -j install
>
> :-)
>
> So I just wanted to bring this up, that integrating it into the
> top level Makefile might make sense. Or not.
Right,
so from dealing with make in the last days, I can say that it's not a
fun walk in the park :). The problem is having multiple targets like the
following:
$ make -j tools perf install
I have to be able to differentiate in the Makefile which of the targets
is a directory ("tools"), which is the actual tool name to build
("perf") and which is a special target ("install") which relates to the
tool name coming before it on the command line and is not the "install"
target of the main Makefile.
And it becomes nasty very fast if you reorder them
$ make -j install perf tools
where all that sequential info doesn't mean anything anymore.
So, the question is, what we actually want?
$ make -j tools perf install
is pretty cryptic wrt to which target we're actually building and having
the -C switch makes stuff a bit clearer IMHO:
$ make -j -C tools perf install
Also, having "install" as the last target means IMO to build the tool
before it and then install it.
In the end of the day, probably the most important thing is what is
the use case for tools/ which makes most sense. I definitely think the
'help' target is a step in that direction. Being able to do
$ make -C tools
and it give you a short description is pretty helpful.
How about we have:
make tools-<toolname> install
or
make tools/perf install
from the toplevel kernel directory? Would that make more sense from a
usability perspective?
--
Regards/Gruss,
Boris.
Advanced Micro Devices GmbH
Einsteinring 24, 85609 Dornach
GM: Alberto Bozzo
Reg: Dornach, Landkreis Muenchen
HRB Nr. 43632 WEEE Registernr: 129 19551
next prev parent reply other threads:[~2012-03-26 15:41 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-23 14:43 [PATCH 0/2] tools: Add a toplevel Makefile Borislav Petkov
2012-03-23 14:43 ` [PATCH 1/3] tools: Add Makefile.include Borislav Petkov
2012-03-23 14:43 ` [PATCH 2/3] tools: Add a toplevel Makefile Borislav Petkov
2012-03-23 14:43 ` [PATCH 3/3] tools: Add a help target Borislav Petkov
2012-03-24 7:44 ` [PATCH 0/2] tools: Add a toplevel Makefile Ingo Molnar
2012-03-26 12:26 ` Borislav Petkov
2012-03-26 14:05 ` Borislav Petkov
2012-03-26 15:14 ` Ingo Molnar
2012-03-26 15:41 ` Borislav Petkov [this message]
2012-03-28 7:25 ` Ingo Molnar
2012-03-28 9:51 ` Borislav Petkov
2012-03-28 17:57 ` Borislav Petkov
2012-03-29 11:21 ` Borislav Petkov
-- strict thread matches above, loose matches on Subject: below --
2012-03-22 17:01 Borislav Petkov
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=20120326154132.GJ32090@aftab \
--to=bp@amd64.org \
--cc=acme@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=mingo@kernel.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