TinyOS 2.x: collect documentation from a program:
.br
\fBnesdoc\fR -o \fIdocumentation-directory\fR [\fB-preserve\fR]
- [\fB-new\fR] [\fB-target=\fIplatform\fR] [\fB-topdir=\fIdirectory\fR]
- [\fIncc-options\fR] \fIfiles...\fR
+ [\fB-new\fR] [\fB-quiet\fR] [\fB-target=\fIplatform\fR] [\fB-topdir=\fIdirectory\fR] [\fB-app\fR]
+ [\fIncc-options\fR] \fIfiles...\fR
TinyOS 2.x: generate nesdoc HTML pages:
.br
-\fBnesdoc\fR -o \fIdocumentation-directory\fR [\fB-new\fR] [\fB-target=\fIplatform\fR] \fB-html\fR
+\fBnesdoc\fR -o \fIdocumentation-directory\fR \fB-html\fR
+ [\fB-new\fR] [\fB-quiet\fR] [\fB-target=\fIplatform\fR]
.SH DESCRIPTION
\fB-new\fR
Force the use of the new nesdoc even when using a TinyOS 1.x source tree.
.TP
+\fB-quiet\fR
+Don't print informational messages.
+.TP
\fB-topdir=\fIdir\fR
Specify directory paths that should be stripped from the source file names
when generating "package names" for the documentation files. The directory
above \fBTOSDIR\fR is automatically added, so this option is only needed for
directories outside the main TinyOS distribution.
-
+.TP
+\fB-app\fR
+Also generate a graph for the whole application in the current directory -
+this is useful to check the wiring of a particular application.
.SH SEE ALSO
.IR ncc (1)