This is the mail archive of the
ecos-discuss@sources.redhat.com
mailing list for the eCos project.
Re: How best to create tags file for ecos source?
- To: jeff at datataker dot com dot au
- Subject: Re: [ECOS] How best to create tags file for ecos source?
- From: Bart Veer <bartv at redhat dot com>
- Date: Mon, 21 May 2001 13:54:10 +0100
- Cc: ecos-discuss at sources dot redhat dot com
- References: <004d01c0e192$9dc322a0$2901a8c0@JEFF>
- Reply-To: bartv at redhat dot com
>>>>> "Jeff" == Jeff Lasslett <jeff@datataker.com.au> writes:
Jeff> I'm a vim user and I would really like to know the
Jeff> best way to create ctags file(s) for the ecos source. The
Jeff> problem is that I don't want to create tags for the whole
Jeff> source tree because it contains code for other platforms and
Jeff> it contains packages that I may not build into my project.
Jeff> I have tried manually running ctags for each directory
Jeff> that I want tags for but I think the tags file gets too big
Jeff> and vim takes forever to jump to a tagged item.
Jeff> If anyone has any advice for regarding this I would
Jeff> appreciate it.
I don't think there is an easy way to automate this at present. The
current makefile generation code does not provide any support for tags
generation. The knowledge of which files get built for a specific
configuration (including automatically generated files) is only
available to C++ programs linked with libcdl, and there is no
documentation for the libcdl API at present (other than the comments
in the header files).
In the medium to long term, I hope to make this sort of information
available to Tcl scripts. However I do not know when this is going to
happen.
Bart