mirror/mbedtls
1
0
Fork 0
mirror of https://github.com/Mbed-TLS/mbedtls.git synced 2024-12-29 09:21:19 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity
dbe435cda0
mbedtls/doxygen/mbedtls.doxyfile

45 lines
1.7 KiB
Plaintext
Raw Normal View History

Bump version to 3.3.0. No changes to .so versions. Signed-off-by: Dave Rodgman <dave.rodgman@arm.com>
2022-12-08 14:43:19 +00:00
PROJECT_NAME = "mbed TLS v3.3.0"
Have doxygen run in the doxygen directory When the Doxywizzard GUI is used and the doxyfile is loaded, the workind directory for doxygen is set to the location of the doxyfile. However the Make and CMake build systems expect doxygen to be ran from the top level directory. This commit unifies the build system and the Doxywizzard GUI so that all of them expect doxygen to be executed in the doxygen directory.
2018-01-19 15:21:11 +00:00
OUTPUT_DIRECTORY = ../apidoc/
- Added Doxygen source code documentation parts (donated by Fox-IT)
2011-01-06 12:28:03 +00:00
FULL_PATH_NAMES = NO
OPTIMIZE_OUTPUT_FOR_C = YES
EXTRACT_ALL = YES
EXTRACT_PRIVATE = YES
EXTRACT_STATIC = YES
CASE_SENSE_NAMES = NO
Look for documentation only in specific directories Generate the documentation from include and doxygen/input only. Don't get snared by files containing Doxygen comments that lie in other directories such as tests, yotta, crypto/include, ... The only difference this makes in a fresh checkout is that the documentation no longer lists target_config.h. This file is from yotta, does not contain any Doxygen comment, and its inclusion in the rendered documentation was clearly an oversight.
2018-09-26 15:49:57 +00:00
INPUT = ../include input
Use only headers for doxygen (no doc in C files)
2015-03-10 17:37:30 +00:00
FILE_PATTERNS = *.h
- Added Doxygen source code documentation parts (donated by Fox-IT)
2011-01-06 12:28:03 +00:00
RECURSIVE = YES
Doxygen: don't traverse symbolic links We don't use symbolic links as part of our build process, so tell Doxygen not to traverse them. In particular, if I have a symbolic link to a directory outside the build tree, I don't want Doxygen to follow it.
2017-12-22 14:34:37 +00:00
EXCLUDE_SYMLINKS = YES
- Added Doxygen source code documentation parts (donated by Fox-IT)
2011-01-06 12:28:03 +00:00
SOURCE_BROWSER = YES
REFERENCED_BY_RELATION = YES
REFERENCES_RELATION = YES
ALPHABETICAL_INDEX = NO
HTML_OUTPUT = .
HTML_TIMESTAMP = YES
doxygen: enable the search engine Signed-off-by: Andrzej Kurek <andrzej.kurek@arm.com>
2022-01-21 13:43:44 +00:00
SEARCHENGINE = YES
- Added Doxygen source code documentation parts (donated by Fox-IT)
2011-01-06 12:28:03 +00:00
GENERATE_LATEX = NO
Adjust doxyfile to expand MBEDTLS_PRIVATE macro. Signed-off-by: Mateusz Starzyk <mateusz.starzyk@mobica.com>
2021-05-20 12:41:22 +00:00
MACRO_EXPANSION = YES
EXPAND_ONLY_PREDEF = YES
Add an include path to the doxyfile to fix preprocessing for docs Previously, doxygen was unable to effectively use preprocessing to determine which parts of code should be documented. This was due to its inability to include headers during preprocessing, which was discovered by running it in preprocessing debug mode: doxygen -d preprocessor mbedtls.doxyfile An example of failure: "#include mbedtls/config.h: not found! skipping..." With the following fix includes are properly preprocessed with the documentation being considerably larger. Signed-off-by: Andrzej Kurek <andrzej.kurek@arm.com>
2020-03-27 16:58:13 +00:00
INCLUDE_PATH = ../include
Adjust doxyfile to expand MBEDTLS_PRIVATE macro. Signed-off-by: Mateusz Starzyk <mateusz.starzyk@mobica.com>
2021-05-20 12:41:22 +00:00
EXPAND_AS_DEFINED = MBEDTLS_PRIVATE
- Added Doxygen source code documentation parts (donated by Fox-IT)
2011-01-06 12:28:03 +00:00
CLASS_DIAGRAMS = NO
HAVE_DOT = YES
Upgraded doxygen config file
2013-09-10 14:17:15 +00:00
DOT_GRAPH_MAX_NODES = 200
- Added Doxygen source code documentation parts (donated by Fox-IT)
2011-01-06 12:28:03 +00:00
MAX_DOT_GRAPH_DEPTH = 1000
DOT_TRANSPARENT = YES
Define a workaround for empty \retval description Since Clang 15, `clang -Wdocumentation` warns about an empty description in a Doxygen `\retval` command: ``` include/psa/crypto.h:91:23: error: empty paragraph passed to '\retval' command [-Werror,-Wdocumentation] * \retval #PSA_SUCCESS ~~~~~~~~~~~~~~~~~~~^ ``` Ideally `\retval` directives should have a description that describes the precise meaning of the return value, but we commonly use an empty description when the return value is a status code and the status code's description is sufficient documentation. As a workaround, define a Doxygen command `\emptydescription` that we can use to make the description source code non-empty, without changing the appearance. Using the command will be done in a subsequent commit. Signed-off-by: Gilles Peskine <Gilles.Peskine@arm.com>
2023-02-14 18:15:40 +00:00
Words. Use them! Signed-off-by: Gilles Peskine <Gilles.Peskine@arm.com>
2023-02-23 12:37:54 +00:00
# We mostly use \retval declarations to document which error codes a function
Further documentation improvements Signed-off-by: Gilles Peskine <Gilles.Peskine@arm.com>
2023-02-23 12:03:30 +00:00
# can return. The reader can follow the hyperlink to the definition of the
# constant to get the generic documentation of that error code. If we don't
# have anything to say about the specific error code for the specific
# function, we can leave the description part of the \retval command blank.
# This is perfectly valid as far as Doxygen is concerned. However, with
# Clang >=15, the -Wdocumentation option emits a warning for empty
# descriptions.
Define a workaround for empty \retval description Since Clang 15, `clang -Wdocumentation` warns about an empty description in a Doxygen `\retval` command: ``` include/psa/crypto.h:91:23: error: empty paragraph passed to '\retval' command [-Werror,-Wdocumentation] * \retval #PSA_SUCCESS ~~~~~~~~~~~~~~~~~~~^ ``` Ideally `\retval` directives should have a description that describes the precise meaning of the return value, but we commonly use an empty description when the return value is a status code and the status code's description is sufficient documentation. As a workaround, define a Doxygen command `\emptydescription` that we can use to make the description source code non-empty, without changing the appearance. Using the command will be done in a subsequent commit. Signed-off-by: Gilles Peskine <Gilles.Peskine@arm.com>
2023-02-14 18:15:40 +00:00
# https://github.com/Mbed-TLS/mbedtls/issues/6960
# https://github.com/llvm/llvm-project/issues/60315
Further documentation improvements Signed-off-by: Gilles Peskine <Gilles.Peskine@arm.com>
2023-02-23 12:03:30 +00:00
# As a workaround, you can write something like
Improve documentation of documentation workaround Signed-off-by: Gilles Peskine <Gilles.Peskine@arm.com>
2023-02-21 09:21:12 +00:00
# \retval #PSA_ERROR_INSUFFICIENT_MEMORY \emptydescription
Further documentation improvements Signed-off-by: Gilles Peskine <Gilles.Peskine@arm.com>
2023-02-23 12:03:30 +00:00
# This avoids writing redundant text and keeps Clang happy.
Define a workaround for empty \retval description Since Clang 15, `clang -Wdocumentation` warns about an empty description in a Doxygen `\retval` command: ``` include/psa/crypto.h:91:23: error: empty paragraph passed to '\retval' command [-Werror,-Wdocumentation] * \retval #PSA_SUCCESS ~~~~~~~~~~~~~~~~~~~^ ``` Ideally `\retval` directives should have a description that describes the precise meaning of the return value, but we commonly use an empty description when the return value is a status code and the status code's description is sufficient documentation. As a workaround, define a Doxygen command `\emptydescription` that we can use to make the description source code non-empty, without changing the appearance. Using the command will be done in a subsequent commit. Signed-off-by: Gilles Peskine <Gilles.Peskine@arm.com>
2023-02-14 18:15:40 +00:00
ALIASES += emptydescription=""
Reference in New Issue Copy Permalink