doc/Doxyfile.in
changeset 1456 5289afbdb720
parent 1400 d12508c2a007
child 1465 60c2961c75ca
equal deleted inserted replaced
5:c991649f658e 6:a1ee3fd5768e
   113 # only done if one of the specified strings matches the left-hand part of 
   113 # only done if one of the specified strings matches the left-hand part of 
   114 # the path. The tag can be used to show relative paths in the file list. 
   114 # the path. The tag can be used to show relative paths in the file list. 
   115 # If left blank the directory from which doxygen is run is used as the 
   115 # If left blank the directory from which doxygen is run is used as the 
   116 # path to strip.
   116 # path to strip.
   117 
   117 
   118 STRIP_FROM_PATH        = @abs_top_srcdir@/src
   118 STRIP_FROM_PATH        = @abs_top_srcdir@
   119 
   119 
   120 # The STRIP_FROM_INC_PATH tag can be used to strip a user-defined part of 
   120 # The STRIP_FROM_INC_PATH tag can be used to strip a user-defined part of 
   121 # the path mentioned in the documentation of a class, which tells 
   121 # the path mentioned in the documentation of a class, which tells 
   122 # the reader which header file to include in order to use a class. 
   122 # the reader which header file to include in order to use a class. 
   123 # If left blank only the name of the header file containing the class 
   123 # If left blank only the name of the header file containing the class 
   124 # definition is used. Otherwise one should specify the include paths that 
   124 # definition is used. Otherwise one should specify the include paths that 
   125 # are normally passed to the compiler using the -I flag.
   125 # are normally passed to the compiler using the -I flag.
   126 
   126 
   127 STRIP_FROM_INC_PATH    = @abs_top_srcdir@/src
   127 STRIP_FROM_INC_PATH    = @abs_top_srcdir@
   128 
   128 
   129 # If the SHORT_NAMES tag is set to YES, doxygen will generate much shorter 
   129 # If the SHORT_NAMES tag is set to YES, doxygen will generate much shorter 
   130 # (but less readable) file names. This can be useful is your file systems 
   130 # (but less readable) file names. This can be useful is your file systems 
   131 # doesn't support long names like on DOS, Mac, or CD-ROM.
   131 # doesn't support long names like on DOS, Mac, or CD-ROM.
   132 
   132 
   449 # documented source files. You may enter file names like "myfile.cpp" or 
   449 # documented source files. You may enter file names like "myfile.cpp" or 
   450 # directories like "/usr/src/myproject". Separate the files or directories 
   450 # directories like "/usr/src/myproject". Separate the files or directories 
   451 # with spaces.
   451 # with spaces.
   452 
   452 
   453 INPUT                  = @abs_top_srcdir@/doc \
   453 INPUT                  = @abs_top_srcdir@/doc \
   454                          @abs_top_srcdir@/src/lemon \
   454                          @abs_top_srcdir@/lemon \
   455 			 @abs_top_srcdir@/src/lemon/bits \
   455                          @abs_top_srcdir@/lemon/bits \
   456                          @abs_top_srcdir@/src/lemon/concept \
   456                          @abs_top_srcdir@/lemon/concept \
   457                          @abs_top_srcdir@/src/demo \
   457                          @abs_top_srcdir@/demo \
   458                          @abs_top_srcdir@/src/test/test_tools.h
   458                          @abs_top_srcdir@/test/test_tools.h
   459 
   459 
   460 # If the value of the INPUT tag contains directories, you can use the 
   460 # If the value of the INPUT tag contains directories, you can use the 
   461 # FILE_PATTERNS tag to specify one or more wildcard pattern (like *.cpp 
   461 # FILE_PATTERNS tag to specify one or more wildcard pattern (like *.cpp 
   462 # and *.h) to filter out the source-files in the directories. If left 
   462 # and *.h) to filter out the source-files in the directories. If left 
   463 # blank the following patterns are tested: 
   463 # blank the following patterns are tested: 
   492 
   492 
   493 # The EXAMPLE_PATH tag can be used to specify one or more files or 
   493 # The EXAMPLE_PATH tag can be used to specify one or more files or 
   494 # directories that contain example code fragments that are included (see 
   494 # directories that contain example code fragments that are included (see 
   495 # the \include command).
   495 # the \include command).
   496 
   496 
   497 EXAMPLE_PATH           = ../src/demo \
   497 EXAMPLE_PATH           = ../demo \
   498                          ../LICENSE \
   498                          ../LICENSE \
   499                          .
   499                          .
   500 
   500 
   501 # If the value of the EXAMPLE_PATH tag contains directories, you can use the 
   501 # If the value of the EXAMPLE_PATH tag contains directories, you can use the 
   502 # EXAMPLE_PATTERNS tag to specify one or more wildcard pattern (like *.cpp 
   502 # EXAMPLE_PATTERNS tag to specify one or more wildcard pattern (like *.cpp