28 |
http://www.gnu.org/software/global/download.html |
http://www.gnu.org/software/global/download.html |
29 |
|
|
30 |
---------------------------------------------------------------------------- |
---------------------------------------------------------------------------- |
31 |
Q2. GLOBAL skip some functions. |
Q2. GLOBAL skips some functions. |
32 |
For example, GLOBAL skip the function 'func' in this example. |
For example, GLOBAL skips the function 'func()' in this example. |
33 |
|
|
34 |
#define M(a) static char *string = a; |
#define M(a) static char *string = a; |
35 |
|
|
39 |
... |
... |
40 |
} |
} |
41 |
|
|
42 |
A2. GLOBAL cannot recognize that pattern, because M(a) seems to be |
A2. GLOBAL cannot recognize 'func()', because M(a) seems to be a function |
43 |
a function definition. |
definition. |
44 |
|
|
45 |
It should be follows. |
It should be follows: |
46 |
|
|
47 |
#define M(a) static char *string = a |
#define M(a) static char *string = a |
48 |
|
|
52 |
... |
... |
53 |
} |
} |
54 |
|
|
55 |
Otherwise, you can tell gtags(1) that by listing the macros in |
Otherwise, you can tell gtags(1) that 'M' is not a function by listing |
56 |
'.notfunction' file in current directory. |
the macros in '.notfunction' file in the current directory. |
57 |
|
|
58 |
[.notfunction] |
[.notfunction] |
59 |
+--------------- |
+--------------- |
70 |
$ ls G* |
$ ls G* |
71 |
GPATH GTAGS |
GPATH GTAGS |
72 |
|
|
73 |
A3. Emacs's ctags cannot locate function referencies. So, gtags cannot make |
A3. Since Emacs's ctags cannot locate function referencies, gtags(1) cannot |
74 |
GRTAGS tag file with it. With the result that you cannot use htags and |
make GRTAGS tag file with it. With the result that htags(1) doesn't |
75 |
global's -r option. |
work because it requires both GTAGS and GRTAGS. |
76 |
|
Besides, you cannot use the -r(--reference) option of global(1). |
77 |
|
|
78 |
---------------------------------------------------------------------------- |
---------------------------------------------------------------------------- |
79 |
Q4. Deleted. |
Q4. Deleted. |
80 |
---------------------------------------------------------------------------- |
---------------------------------------------------------------------------- |
81 |
Q5. Deleted. |
Q5. Deleted. |
82 |
---------------------------------------------------------------------------- |
---------------------------------------------------------------------------- |
83 |
Q6. It seems that gtags cannot treat files which include blanks in the path. |
Q6. It seems that gtags(1) cannot treat files which include blanks in the path. |
84 |
Why? |
Why? |
85 |
|
|
86 |
A6. Because it is hard for GLOBAL to treat them correctly with keeping |
A6. Because it is hard for GLOBAL to treat them correctly with keeping |
89 |
the priority is not high. The best way is no to use blanks in path name. |
the priority is not high. The best way is no to use blanks in path name. |
90 |
|
|
91 |
---------------------------------------------------------------------------- |
---------------------------------------------------------------------------- |
92 |
Q7. Gtags(1) and htags(1) works only on one directory. So, we cannot refer |
Q7. Gtags(1) and htags(1) work only for one directory tree. So, we cannot |
93 |
library functions like strlen from my project. Any solutions? |
refer library functions like strlen() from my project. Any solutions? |
94 |
|
|
95 |
A7. In global(1), you can use GTAGSLIBPATH environment variable. |
A7. For global(1), you can use GTAGSLIBPATH environment variable. |
96 |
|
|
97 |
[library] /usr/src/lib |
[library] /usr/src/lib |
98 |
[your project] /usr/home/project |
[your project] /usr/home/project |
102 |
$ global strlen |
$ global strlen |
103 |
../../../usr/src/lib/libc/string/strlen.c |
../../../usr/src/lib/libc/string/strlen.c |
104 |
|
|
105 |
In htags(1), you can do it by copying them into your source project. |
For htags(1), you can merge library directories into your source project |
106 |
|
by copying them. |
107 |
For example: |
For example: |
108 |
|
|
109 |
$ cd /usr/home/project |
$ cd /usr/home/project |
116 |
---------------------------------------------------------------------------- |
---------------------------------------------------------------------------- |
117 |
Q9. Deleted. |
Q9. Deleted. |
118 |
---------------------------------------------------------------------------- |
---------------------------------------------------------------------------- |
119 |
Q10. Does GLOBAL support multi-bytes code set? |
Q10. Does GLOBAL support multi-byte code set? |
120 |
Which character code set is supported? |
Which character code set is supported? |
121 |
|
|
122 |
A10. GLOBAL doesn't support multi-byte character code set yet. |
A10. GLOBAL doesn't support multi-byte character code set yet. |