Hi,

I've been attempting to generate global tags files with the intent of being 
able to use them with geany to jump to declarations and definitions as 
necessary, as they would normally be used.

I'm pretty sure I'm doing everything correctly here but I can't seem to get the 
desired affect.

Here is an example command I used to generate glib tags:

CFLAGS=`pkg-config --cflags glib-2.0` geany -g glib_2_0.c.tags 
/usr/include/glib-2.0/*.h

it ran without issue. When I try and test it works by jumping to something 
integral to glib, like "gboolean", it does not work, upon inspection of the 
generated file it looks like this:

`
g_warn_messageÌ1024Í(const char *domain, const char *file, int line, const char
g_warningÌ131072Í(...)Ö0
g_weak_ref_clearÌ1024Í(GWeakRef *weak_ref)Ö0Ïvoid
g_weak_ref_getÌ1024Í(GWeakRef *weak_ref)Ö0Ïgpointer
g_weak_ref_initÌ1024Í(GWeakRef *weak_ref, gpointer object)Ö0Ïvoid
g_weak_ref_setÌ1024Í(GWeakRef *weak_ref, gpointer object)Ö0Ïvoid
gatomicrefcountÌ4096Ö0Ïvolatile gint 
**gbooleanÌ4096Ö0Ïgint**
gcharÌ4096Ö0Ïchar
gchararrayÌ4096Ö0Ïgchar *
gconstpointerÌ4096Ö0Ïconst void *
gdoubleÌ4096Ö0Ïdouble
getÌ1024Í(gpointer cb_data, GSource *source, GSourceFunc *func, gpointer *data)Î
get_propertyÌ1024Í(GObject *object, guint property_id, GValue *value, GParamSpec
getdateÌ1024Í(const char *__string)Ö0Ïtm
getdate_errÌ32768Ö0Ïint
`

I feel like something is going wrong here, looking at a pre-generated tags file 
there seems to be file paths in each line, presumably to be able to find the 
file the declaration/definition is in.

Thanks,

Lukas

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/issues/2354

Reply via email to