--Boundary-00=_eQdHEEGMgbNtiXQ
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

On Sunday 19 March 2006 21:51, Frans Englich wrote:
> On Thursday 16 March 2006 23:10, Frans Englich wrote:
>
> Another issue:
>
> Exclude ui_*.h
>
> recurse example path


Ugh, me cannot speak. That was me 1) scratching down some things, and 2)
Incapable of handling a mail program. The readable version:

Shouldn't ui_*.h files be excluded? That's how moc in Qt 4.0 generates ui
files(in some cases, at least).

I haven't yet managed to get doxygen.sh working on a module, but I'm pretty
sure it will have trouble locating the files I @include. Wouldn't it be
practical if EXAMPLE_RECURSIVE is set to YES? Or would it break some other
case?

I'm no Doxygen expert[1], but is the attached patch acceptable?


Cheers,

Frans

1.
And far from an expert at handling a MUA as well. Really, what I'm an expert
in is saying MOO. (getting a bit late over here)

--Boundary-00=_eQdHEEGMgbNtiXQ
Content-Type: text/x-diff;
charset="iso-8859-1";
name="Doxyfile.global.diff"
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
filename="Doxyfile.global.diff"

Index: ../admin/Doxyfile.global
================================================== =================
--- ../admin/Doxyfile.global (revision 493239)
+++ ../admin/Doxyfile.global (working copy)
@@ -61,6 +61,7 @@
EXCLUDE_SYMLINKS = NO
EXCLUDE_PATTERNS = *.moc.* \
moc* \
+ ui_*.h \
*.all_cpp.* \
*unload.* \
*/test/* \
@@ -68,7 +69,7 @@
*_p.h
EXAMPLE_PATH =
EXAMPLE_PATTERNS =
-EXAMPLE_RECURSIVE = NO
+EXAMPLE_RECURSIVE = YES
IMAGE_PATH =
INPUT_FILTER =
FILTER_SOURCE_FILES = NO

--Boundary-00=_eQdHEEGMgbNtiXQ
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline


>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<


--Boundary-00=_eQdHEEGMgbNtiXQ--