Also
- Reorganize the usage message, since the options list has gotten
quite long.
- Standardize internal variables with underscores between words (very
un-ns-3 like, but really this whole thing should be in python in wscript).
On Dec 6, 2013, at 8:28 AM, Daniel Lertpratchya <nikkipui@gmail.com>
wrote:
I recently ran the doxygen.warnings.report.sh script and I got the
following error. I tried on a fresh copy of ns-3-dev and Brian
also has the same problem.
'build' finished successfully (1.649s)
Rebuilding doxygen docs with full errors...Done.
mv: missing destination file operand after ‘doc/doxygen.log’
Try 'mv --help' for more information.
No filters.
cat: doc/doxygen.warnings.log: No such file or directory
grep: doc/doxygen.warnings.log: No such file or directory
cat: doc/doxygen.warnings.log: No such file or directory
On Dec 6, 2013, at 10:36 AM, Daniel Lertpratchya <nikkipui@gmail.com>
wrote:
I think doxygen.warnings.report.sh line 150 should be changed from
$log to $LOG. That seems to fix the problem for me.
You can now point to the standard log file, or specific log file.
You can also filter out test and examples.
Usage: doxygen.warnings.report.sh.mod [-eth] [-f <log-file> | -l | -s]
Run doxygen to generate all errors; report error counts
by module and file.
The default behavior is to modify doxygen.conf temporarily to
report all undocumented elements, and to reduce the run time.
The output of this special run is kept in doc/doxygen.warnings.log.
The -f or -l options use alternate log files.
-e Filter out warnings from */examples/*
-t Filter out warnings from */test/*
-f Skip doxygen run; use existing <log-file>.
-s Skip doxygen run; use existing warnings log doc/doxygen.warnings.log
-l Skip doxygen run; use the normal doxygen log doc/doxygen.log
Only the first of -f <log-file>, -s, or -l will have effect.
-h Print this usage message
Direct doxygen warnings to doxygen.log.
doxygen.warnings.report.sh moves this to doxygen.warnings.log, so
subsequent normal oxygen builds don't overwrite it.
