| 31 |
|
# This could be handy for archiving the generated documentation or |
| 32 |
|
# if some version control system is used. |
| 33 |
|
|
| 34 |
< |
PROJECT_NUMBER = 1.0 |
| 34 |
> |
PROJECT_NUMBER = 2.0 |
| 35 |
|
|
| 36 |
|
# The OUTPUT_DIRECTORY tag is used to specify the (relative or absolute) |
| 37 |
|
# base path where the generated documentation will be put. |
| 38 |
|
# If a relative path is entered, it will be relative to the location |
| 39 |
|
# where doxygen was started. If left blank the current directory will be used. |
| 40 |
|
|
| 41 |
< |
OUTPUT_DIRECTORY = doc/ |
| 41 |
> |
OUTPUT_DIRECTORY = @CMAKE_CURRENT_BINARY_DIR@/doc/ |
| 42 |
|
|
| 43 |
|
# If the CREATE_SUBDIRS tag is set to YES, then doxygen will create |
| 44 |
|
# 4096 sub-directories (in 2 levels) under the output directory of each output |
| 574 |
|
# directories like "/usr/src/myproject". Separate the files or directories |
| 575 |
|
# with spaces. |
| 576 |
|
|
| 577 |
< |
INPUT = src/ |
| 577 |
> |
INPUT = @CMAKE_CURRENT_SOURCE_DIR@/src/ |
| 578 |
|
|
| 579 |
|
# This tag can be used to specify the character encoding of the source files |
| 580 |
|
# that doxygen parses. Internally doxygen uses the UTF-8 encoding, which is |
