From: Wolfgang Grandegger <wg@domain.hid>
To: xenomai-core <xenomai@xenomai.org>
Subject: [Xenomai-core] [PATCH] Doxygen hyperlinking utilitiy and demo programs
Date: Fri, 10 Nov 2006 12:33:00 +0100 [thread overview]
Message-ID: <4554636C.4070704@domain.hid> (raw)
[-- Attachment #1: Type: text/plain, Size: 471 bytes --]
Hello,
the attached patch adds the RT-Socket-CAN utility programs as examples
to the Doxygen documentation setup. This creates some nice cross
reference from the documented API functions to the example code lines
and vice versa. In a similar way, the Xenomai demo programs and code
snippets could be integrated making it much easier to find example code
or the description of an API function used in an example.
Please have a look and comment?
Thanks.
Wolfgang.
[-- Attachment #2: xenomai-doxygen-examples.patch --]
[-- Type: text/x-patch, Size: 1880 bytes --]
Index: include/rtdm/rtcan.h
===================================================================
--- include/rtdm/rtcan.h (revision 1810)
+++ include/rtdm/rtcan.h (working copy)
@@ -1116,7 +1116,15 @@
/** @} */
+/*!
+ * @anchor Utilities @name CAN test and utility functions
+ * @{ */
+/** @example rtcanconfig.c */
+/** @example rtcansend.c */
+/** @example rtcanrecv.c */
/** @} */
+/** @} */
+
#endif /* _RTCAN_H */
Index: doc/doxygen/Doxyfile-common.in
===================================================================
--- doc/doxygen/Doxyfile-common.in (revision 1810)
+++ doc/doxygen/Doxyfile-common.in (working copy)
@@ -383,27 +383,27 @@
# EXCLUDE_PATTERNS tag to specify one or more wildcard patterns to exclude
# certain files from those directories.
-EXCLUDE_PATTERNS =
+EXCLUDE_PATTERNS = "*.c"
# The EXAMPLE_PATH tag can be used to specify one or more files or
# directories that contain example code fragments that are included (see
# the \include command).
-EXAMPLE_PATH =
+EXAMPLE_PATH = ../../src/utils
# If the value of the EXAMPLE_PATH tag contains directories, you can use the
# EXAMPLE_PATTERNS tag to specify one or more wildcard pattern (like *.cpp
# and *.h) to filter out the source-files in the directories. If left
# blank all files are included.
-EXAMPLE_PATTERNS =
+EXAMPLE_PATTERNS =
# If the EXAMPLE_RECURSIVE tag is set to YES then subdirectories will be
# searched for input files to be used with the \include or \dontinclude
# commands irrespective of the value of the RECURSIVE tag.
# Possible values are YES and NO. If left blank NO is used.
-EXAMPLE_RECURSIVE = NO
+EXAMPLE_RECURSIVE = YES
# The IMAGE_PATH tag can be used to specify one or more files or
# directories that contain image that are included in the documentation (see
next reply other threads:[~2006-11-10 11:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-10 11:33 Wolfgang Grandegger [this message]
2006-11-11 17:28 ` [Xenomai-core] [PATCH] Doxygen hyperlinking utilitiy and demo programs Gilles Chanteperdrix
2006-11-11 19:18 ` Wolfgang Grandegger
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4554636C.4070704@domain.hid \
--to=wg@domain.hid \
--cc=xenomai@xenomai.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.