From: Andi Kleen <andi@firstfloor.org>
To: linux-kbuild@vger.kernel.org
Subject: make ctags with separate build dirs
Date: Mon, 4 Mar 2013 19:02:16 +0100 [thread overview]
Message-ID: <20130304180216.GI3401@two.firstfloor.org> (raw)
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?
Thanks,
-Andi
--
ak@linux.intel.com -- Speaking for myself only.
next reply other threads:[~2013-03-04 18:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-04 18:02 Andi Kleen [this message]
2013-03-04 18:35 ` make ctags with separate build dirs Sam Ravnborg
2013-03-04 19:08 ` Andi Kleen
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=20130304180216.GI3401@two.firstfloor.org \
--to=andi@firstfloor.org \
--cc=linux-kbuild@vger.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