Skip to contentSkip to conversation

make ctags with separate build dirs

DISCUSSION Andi Kleen 2 participants 3 messages Mar 4, 2013 Kbuild

lore
Share & tools
lore

Andi Kleen

author
#0 lore 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

Signature · 1 line
[email protected] -- Speaking for myself only.
#1 lore raw
Quoted 7 lines · Andi Kleen

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.

Sam

author
#2 lore raw
Quoted 7 lines · Sam Ravnborg
Quoted 6 lines · Andi Kleen

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.

Quoted 7 lines
Quoted 1 line

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