From: Andi Kleen <andi@firstfloor.org>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: Andi Kleen <andi@firstfloor.org>, linux-kbuild@vger.kernel.org
Subject: Re: make ctags with separate build dirs
Date: Mon, 4 Mar 2013 20:08:05 +0100 [thread overview]
Message-ID: <20130304190805.GK3401@two.firstfloor.org> (raw)
In-Reply-To: <20130304183529.GA10627@merkur.ravnborg.org>
On Mon, Mar 04, 2013 at 07:35:29PM +0100, Sam Ravnborg wrote:
> On Mon, Mar 04, 2013 at 07:02:16PM +0100, Andi Kleen wrote:
> >
> > I usually use separate build dirs. For make ctags in the main source
> > directory the dependecies always want to create all kinds of
> > infrastructure and set up up the config, polluting the source dir.
> > For make cscope it doesn't do that.
> >
> > Could make ctags be fixed to not do that?
>
> Confused:
> $ make ctags
> make: *** No rule to make target `ctags'. Stop.
>
> I have no support for make ctags in the kernel.
Ah, it's "make tags" and works as expected. Never mind.
Thanks Sam.
-Andi
prev parent reply other threads:[~2013-03-04 19:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-04 18:02 make ctags with separate build dirs Andi Kleen
2013-03-04 18:35 ` Sam Ravnborg
2013-03-04 19:08 ` Andi Kleen [this message]
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=20130304190805.GK3401@two.firstfloor.org \
--to=andi@firstfloor.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=sam@ravnborg.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