generating tag files for sources

[Pascal Z.]

Has there been any work done about automatically generating tag files
for sources via ctags/cscope or similar tools ?
This can be very useful for intellisense functionality e.g. as provided
by vim's omnicompletion or emacs.
I tried to set up a Jamfile so that using "bjam tags" will generate tags
for all used source files, but I didn't manage it. I'm not that familiar
with boost.Build. How could such a jam rule look?

Thanks
Pascal

_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost-build

[Vladimir Prus]

On Monday 28 September 2009 Pascal Z. wrote:

> Has there been any work done about automatically generating tag files
> for sources via ctags/cscope or similar tools ?
> This can be very useful for intellisense functionality e.g. as provided
> by vim's omnicompletion or emacs.
> I tried to set up a Jamfile so that using "bjam tags" will generate tags
> for all used source files, but I didn't manage it. I'm not that familiar
> with boost.Build. How could such a jam rule look?

Hi Pascal,

I would recommend this:

        make TAGS : : @make-tags : <location>. ;
        actions make-tags
        {
                ctags `find . -name *.c -or -name *.h`
        }

It was awhile since I've last used ctags, so the command
might be wrong.

- Volodya
_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost-build

[Pascal Z.]

Vladimir Prus schrieb:

> On Monday 28 September 2009 Pascal Z. wrote:
>
>> Has there been any work done about automatically generating tag files
>> for sources via ctags/cscope or similar tools ?
>> This can be very useful for intellisense functionality e.g. as provided
>> by vim's omnicompletion or emacs.
>> I tried to set up a Jamfile so that using "bjam tags" will generate tags
>> for all used source files, but I didn't manage it. I'm not that familiar
>> with boost.Build. How could such a jam rule look?
>
> Hi Pascal,
>
> I would recommend this:
>
> make TAGS : : @make-tags : <location>. ;
> actions make-tags
> {
> ctags `find . -name *.c -or -name *.h`
> }
>
> It was awhile since I've last used ctags, so the command
> might be wrong.
>
> - Volodya
> _______________________________________________
> Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost-build
>

Hello Vladimir

Thanks for your suggestion!
I now finally have a way to build my tagfiles together with the
invocation of bjam =). Didn't quite manage this myself.

I'm trying to build up some kind of tagfile-system for vim.
My dream would be to get a list of all included files (system headers,
my own headers, boost library etc.) for a boost.Build project's
project-root.jam.
Since I'm using bjam to set a few include paths just by making my
targets depend on /boost//thread or /boost//date_time it would be
necessary to have something like "bjam -get-project-inclues" and then
have ctags generate a project.tags in the project folder.
Vim can then be setup to use this file as tag-file for omni-completion.
I also read about the wave example "list_includes", but I'm also missing
the include paths from bjam here.
I couldn't find a way to get bjam to output the included files, is there
one?

Does anybody have a suggestion ? I'd love to have completion in vim
without manually generating tagfiles. I'm already using bjam as my
make-command, but tag files are missing :/.

Thanks
Pascal

_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost-build