doxygen-users

[Doxygen-users] Links to another page, but not the top.

['Carlo W. <ca...@al...>]

Hi,

I'd like to link to some anchor that is defined on
another page, but that doesn't seem to be allowed.

In the documentation of one file I added:
\anchor preparation_step2

And in another file I would like to use:

/** \file macro_ForAllDebugChannels.h
 * Do not include this header file directly, instead include \link preparation_step2 "debug.h" \endlink.
 */

However, this results in:

/home/carlo/c++/libcw_branch-threading/src/libcwd/include/libcw/macro_ForAllDebugChannels.h:1 Warning: link to unknown entity `preparation_step2' in the documentation of this entity!

Can anyone tell me if it is doable to link to an anchor that is not on
the same page?  Or am I doing something wrong?

-- 
Carlo Wood <ca...@al...>

[Doxygen-users] BUG: Input FILE_PATTERNS fails with "c*.h" and "c*.cpp"

[Roland T. <rt...@wa...>]

         Input FILE_PATTERNS  seems to fail when a c*.h or c*.cpp pattern 
is specified.

         More info:
         Working on a big project, I try to use tags for compilation speed. 
So I made config files for subdirectories (work fine, at least for what 
matters here). But I have many .h and .cpp file in my project directory. I 
try to divide sources like this :

in A_L.cfg:
...
INPUT                  = .
FILE_PATTERNS          = a*.h a*.cpp \
                         c*.h c*.cpp \
                         b*.h b*.cpp \
                         d*.h d*.cpp \
                         e*.h e*.cpp \
                         f*.h f*.cpp \
                         g*.h g*.cpp \
                         h*.h h*.cpp \
                         i*.h i*.cpp \
                         j*.h j*.cpp \
                         k*.h k*.cpp \
                         l*.h l*.cpp
...

in M_Z.cfg

...
INPUT                  = .
FILE_PATTERNS          = m*.h m*.cpp \
                         n*.h n*.cpp \
                         o*.h o*.cpp \
                         p*.h p*.cpp \
                         q*.h q*.cpp \
                         r*.h r*.cpp \
                         s*.h s*.cpp \
                         t*.h t*.cpp \
                         u*.h u*.cpp \
                         v*.h v*.cpp \
                         w*.h w*.cpp \
                         x*.h x*.cpp \
                         y*.h y*.cpp \
                         z*.h z*.cpp
...

         Each config file is intended to produce a tag file from half the 
source files.
         When run, M_Z_cfg works fine, reading M to Z files, but A_L.cfg 
reads all .h and .cpp in the current directory. When I delete the c*.h and 
c*.cpp line, it works fine (except there is no c* file).
         As I use IGNORE_PREFIX = C in these files, same char wich fails in 
pattern, I tried (why not?) with empy IGNORE_PREFIX :same error.

         The only workaround I found is specifying ca*.h ca*.cpp cb*.h 
cb*.cpp ... to cz*.cpp in FILE_PATTERN. Simpler way needed

Thanks


Roland Touchain
rt...@wa...
  

Re: [Doxygen-users] BUG: Input FILE_PATTERNS fails with "c*.h" and "c*.cpp"

[Roland T. <rol...@li...>]

 >Is what you are saying that setting FILE_PATTERNS to c*.cpp c*.h will
 >include all files even those not starting with a "c"? I haven't been able
 >to reproduce that, with a simple set of empty files.
 >...

Here is a zip with a few files. Command 'doxygen A_L.cfg'  fails : doxygen 
parses p* and r* files which are NOT in the wildcards of FILE_PATTERNS. 
This fails with:
Win2k SP2 and doxygen 1.2.12
Win Me and doxygen 1.2.9.1
Win 98 SP2 and doxygen 1.2.9.1

	If I delete the line with 'c', it works fine.( only a* to l* files, but no 
c*).

 >...
 >By the way: you can also specify ranges like [a-l]*.cpp
 >...
Putting [a-l]*.h [a-l]*.cpp in FILE_PATTERNS doesn't work. In my sample, 
only a* and d* files are parsed.  (WinMe, dowygen 1.1.9.1).

Thinking that my cfg files were bad, I asked doxygen to make a brand new 
config file, and set
INPUT                  = .
FILE_PATTERNS          = [a-l]*.h [a-l]*.cpp
Same result: only a* and d* files are parsed (again WinMe, dowygen 
1.1.9.1).. Perhaps long names are not well parsed ? Or more probably I am 
missing something big ??

I was aware that one can use wildcards. But I don't know if widcards are 
sytem dependant, or are parsed as regular expressions by doxygen itself. A 
few words about wildcard would be nice in the doc.

But I am now thinking that the way I tried for cutting down processing time 
is not the right one. In fact, index.html files generated for each of the 
config files are written at the same place (will not work). Even I specify 
output directories to doxygen, final result will not be exactly the same as 
single config file (i.e. no-tagfile) doc.

I would like to get a full documentation, as one generated by a single 
config file doxygen process. But tag files (as I understand them) only 
provide links between documentations, each one having a mainpage, an index 
and so on. Is there a way to do this ?


Thank for the great tool !
Regards