From: Paul S. <ps...@ne...> - 2007-03-19 02:14:47
|
On Sun, 2007-03-18 at 17:04 +0100, Jan-Benedict Glaw wrote: > > I've also found a few other issues, like not all my header files are > > getting hyperlinked properly. > > Only found the issue or also a fix? Only the issue. I spent about 30 minutes staring at the code and scratching my head trying to figure out where the #include files are linked for C/C++ and couldn't find it. I found the generic.conf file, etc. but I guess I just don't quite understand how it's all used and there's not much in the way of documentation :-/. What I see is that #include'd files are linked if they are in the same directory as the source, but not otherwise. Apparently the system doesn't know how to find non-local headers. To me it seems like a good way to resolve this would be to use the file list generated by swish to locate headers. If we wanted to be fancy we could say that if more than one header of a given name was found, the #include could link to a search for that header name so the user could decide (since we don't have the compiler line to figure it out for real). I don't know much about Glimpse, because it's not free software. If it doesn't have anything like swish's filenames file we could have genxref create one for us. |