1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
|
___________________________________
| | | | | _ | | |
| |___| | | | | _| | | | GNU GLOBAL source code tag system
| | | | | | | | | |
| ~~ | ~~| | ~ | | | ~~| for all hackers.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Copyright (c) 2000, 2003, 2004, 2005
Tama Communications Corporation
This file is free software; as a special exception the author gives
unlimited permission to copy and/or distribute it, with or without
modifications, as long as this notice is preserved.
This program is distributed in the hope that it will be useful, but
WITHOUT ANY WARRANTY, to the extent permitted by law; without even the
implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
----------------------------------
Frequentry Asked Questions about GLOBAL.
----------------------------------------------------------------------------
Q1. Does GLOBAL support DOS and Windows 32 environment?
A1. No, it doesn't. GNU GLOBAL supports only UNIX(POSIX) environment.
But some outsite projects develop DOS and Windows 32 version of it.
Please see:
http://www.gnu.org/software/global/download.html
----------------------------------------------------------------------------
Q2. GLOBAL skips some functions.
For example, GLOBAL skips the function 'func()' in this example.
#define M(a) static char *string = a;
M(a)
func() { <= GLOBAL skip func().
...
}
A2. GLOBAL cannot recognize 'func()', because M(a) seems to be a function
definition.
It should be follows:
#define M(a) static char *string = a
M(a); <= end with ';'
func() {
...
}
Otherwise, you can tell gtags(1) that 'M' is not a function by listing
the macros in '.notfunction' file in the current directory.
[.notfunction]
+---------------
|M
|...
----------------------------------------------------------------------------
Q3. I have set up 'gtags.conf' to use emacs's ctags command with GLOBAL
but I cannot use htags.
$ gtags
$ htags
htags: GTAGS and GRTAGS not found. Please make them.
$ ls G*
GPATH GTAGS
A3. Since Emacs's ctags cannot locate function referencies, gtags(1) cannot
make GRTAGS tag file with it. With the result that htags(1) doesn't
work because it requires both GTAGS and GRTAGS.
Besides, you cannot use the -r(--reference) option of global(1).
----------------------------------------------------------------------------
Q4. Deleted.
----------------------------------------------------------------------------
Q5. Deleted.
----------------------------------------------------------------------------
Q6. It seems that gtags(1) cannot treat files which include blanks in the path.
Why?
A6. Because it is hard for GLOBAL to treat them correctly with keeping
upper compatibility. Gtags(1) currently ignores files which include
blanks in the path. We put the improvement to our TODO list but
the priority is not high. The best way is no to use blanks in path name.
----------------------------------------------------------------------------
Q7. Gtags(1) and htags(1) work only for one directory tree. So, we cannot
refer library functions like strlen() from my project. Any solutions?
A7. For global(1), you can use GTAGSLIBPATH environment variable.
[library] /usr/src/lib
[your project] /usr/home/project
$ (cd /usr/src/lib; gtags)
$ export GTAGSLIBPATH=/usr/src/lib
$ global strlen
../../../usr/src/lib/libc/string/strlen.c
For htags(1), you can merge library directories into your source project
by copying them.
For example:
$ cd /usr/home/project
$ cp -r /usr/src/lib .
$ gtags
$ htags
----------------------------------------------------------------------------
Q8. Deleted.
----------------------------------------------------------------------------
Q9. Deleted.
----------------------------------------------------------------------------
Q10. Does GLOBAL support multi-byte code set?
Which character code set is supported?
A10. GLOBAL doesn't support multi-byte character code set yet.
----------------------------------------------------------------------------
Q11. Can GLOBAL running on a UNIX machine treat source files
which include DOS/Windows style new-line code? And vice versa?
A11. GLOBAL support only the native text format.
Besides, please go by the own responsibility.
----------------------------------------------------------------------------
End of FAQ.
|
