mirror of
https://github.com/RT-Thread/rt-thread.git
synced 2026-02-09 05:00:00 +08:00
Some checks failed
ToolsCI / Tools (push) Waiting to run
AutoTestCI / components/cpp11 (push) Waiting to run
AutoTestCI / kernel/atomic (push) Waiting to run
AutoTestCI / kernel/atomic/riscv64 (push) Waiting to run
AutoTestCI / kernel/atomic_c11 (push) Waiting to run
AutoTestCI / kernel/atomic_c11/riscv64 (push) Waiting to run
AutoTestCI / kernel/device (push) Waiting to run
AutoTestCI / kernel/ipc (push) Waiting to run
AutoTestCI / kernel/irq (push) Waiting to run
AutoTestCI / kernel/mem (push) Waiting to run
AutoTestCI / kernel/mem/riscv64 (push) Waiting to run
AutoTestCI / kernel/thread (push) Waiting to run
AutoTestCI / kernel/timer (push) Waiting to run
AutoTestCI / rtsmart/aarch64 (push) Waiting to run
AutoTestCI / rtsmart/arm (push) Waiting to run
AutoTestCI / rtsmart/riscv64 (push) Waiting to run
AutoTestCI / components/utest (push) Waiting to run
RT-Thread BSP Static Build Check / ESP32C3 (push) Waiting to run
RT-Thread BSP Static Build Check / Infineon_TI_microchip (push) Waiting to run
RT-Thread BSP Static Build Check / RT-Thread Online Packages (STM32F407 RT-Spark) (push) Waiting to run
RT-Thread BSP Static Build Check / RTduino/Arduino Libraries (Raspberry Pico) (push) Waiting to run
RT-Thread BSP Static Build Check / RTduino/Arduino Libraries (STM32F412 Nucleo) (push) Waiting to run
RT-Thread BSP Static Build Check / aarch64 (push) Waiting to run
RT-Thread BSP Static Build Check / gd32_n32_apm32 (push) Waiting to run
RT-Thread BSP Static Build Check / hpmicro (push) Waiting to run
RT-Thread BSP Static Build Check / i386-unknown (push) Waiting to run
RT-Thread BSP Static Build Check / llvm-arm (push) Waiting to run
RT-Thread BSP Static Build Check / mips (push) Waiting to run
RT-Thread BSP Static Build Check / nordic(yml) (push) Waiting to run
RT-Thread BSP Static Build Check / nuvoton (push) Waiting to run
RT-Thread BSP Static Build Check / nxp_renesas (push) Waiting to run
RT-Thread BSP Static Build Check / others_at32_hc32_ht32 (push) Waiting to run
RT-Thread BSP Static Build Check / riscv-none (push) Waiting to run
RT-Thread BSP Static Build Check / riscv64-unknown (push) Waiting to run
RT-Thread BSP Static Build Check / simulator (push) Waiting to run
RT-Thread BSP Static Build Check / stm32_f2_f4 (push) Waiting to run
RT-Thread BSP Static Build Check / stm32_f7_g0_h7_mp15_u5_h5_wb5 (push) Waiting to run
RT-Thread BSP Static Build Check / stm32l4_f0_f1 (push) Waiting to run
BSP compilation with more drivers / BSP Compilation with More Drivers (push) Waiting to run
pkgs_test / change (push) Has been skipped
doc_doxygen / doxygen_doc generate (push) Has been cancelled
doc_doxygen / deploy (push) Has been cancelled
Documentation is provided to clarify how to write doxygen documentation for RT-Thread. This document is also integrated as part of RT-Thread doxygen documentation. An example is also provided. The original README.md is removed and integrated into this document. Updated github actions for doxygen too. Signed-off-by: Chen Wang <unicorn_wang@outlook.com>
79 lines
2.6 KiB
C
79 lines
2.6 KiB
C
#ifndef _DOXYGEN_EXAMPLE_STRUCT_H_
|
|
#define _DOXYGEN_EXAMPLE_STRUCT_H_
|
|
|
|
/**
|
|
* @page page_howto_struct How to write doxygen documentation for structure.
|
|
*
|
|
* We recommend the following approach:
|
|
*
|
|
* A comment block before the structure definition is recommended to
|
|
* describe the general information of the structure type. In the
|
|
* comment block, a `@brief` is required, other commands (such as `@note`)
|
|
* are optional.
|
|
*
|
|
* If you feel that the description of `@brief` is not enough, you
|
|
* can add a detailed description part, which is also optional.
|
|
*
|
|
* Put member comments inside the structure definition and after every member.
|
|
*
|
|
* See
|
|
* <a href="https://github.com/RT-Thread/rt-thread/blob/master/documentation/0.doxygen/example/include/struct.h">documentation/0.doxygen/example/include/struct.h</a>
|
|
* for example.
|
|
*/
|
|
|
|
/**
|
|
* @addtogroup group_doxygen_example
|
|
*/
|
|
|
|
/** @{ */
|
|
|
|
/**
|
|
* @brief Brief description this structure
|
|
*
|
|
* Detailed description starts here, one line or multiple lines.
|
|
* Blah blah blah...
|
|
*
|
|
* @note This is a note for this structure, blah blah blah...
|
|
*/
|
|
struct dogygen_example_struct
|
|
{
|
|
int m1; /**< Some documentation for member 'm1'...
|
|
* Multiple lines ... Note the "multi-line" here refers
|
|
* to the code. Whether it is displayed in multiple lines
|
|
* on the specific HTML page depends on the browser rendering.
|
|
*
|
|
* @note We can also embed note for member 'm1'...
|
|
*/
|
|
int m2; /**< Some documentation for member 'm2'... */
|
|
int m3; /**< Some documentation for member 'm3'... */
|
|
int m4; /**< Some documentation for member 'm4'... */
|
|
int m5; /**< Some documentation for member 'm5'... */
|
|
};
|
|
|
|
/**
|
|
* @brief Brief description this structure
|
|
*
|
|
* Detailed description starts here, one line or multiple lines.
|
|
* Blah blah blah...
|
|
*
|
|
* @note This is a note for this structure, blah blah blah...
|
|
*/
|
|
struct dogygen_example_struct_another
|
|
{
|
|
int m1; /**< Some documentation for member 'm1'...
|
|
* Multiple lines ... Note the "multi-line" here refers
|
|
* to the code. Whether it is displayed in multiple lines
|
|
* on the specific HTML page depends on the browser rendering.
|
|
*
|
|
* @note We can also embed note for member 'm1'...
|
|
*/
|
|
int m2; /**< Some documentation for member 'm2'... */
|
|
int m3; /**< Some documentation for member 'm3'... */
|
|
int m4; /**< Some documentation for member 'm4'... */
|
|
int m5; /**< Some documentation for member 'm5'... */
|
|
};
|
|
|
|
/** @} */
|
|
|
|
#endif /* _DOXYGEN_EXAMPLE_STRUCT_H_ */
|