--===============1650957812==
Content-Type: multipart/signed;
boundary="nextPart1384132.7BRl7XjMvH";
protocol="application/pgp-signature";
micalg=pgp-sha1
Content-Transfer-Encoding: 7bit

--nextPart1384132.7BRl7XjMvH
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

On Sunday 19 March 2006 22:58, Frans Englich wrote:
> Shouldn't ui_*.h files be excluded? That's how moc in Qt 4.0 generates ui
> files(in some cases, at least).

Why, in particular? Does moc generate files with Doxygen-style comments in =
it?=20
In any case, I'd recommend building APIDOX from a clean source directory, n=
ot=20
one with all kinds of cruft in it.

> I haven't yet managed to get doxygen.sh working on a module, but I'm pret=
ty
> 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?

Well, there's awful few examples in the KDE APIDOX. In any case you can set=
=20
these things on a per-directory basis (as described in the APIDOX howto,=20
http://developer.kde.org/documentati...rary/howto.php ) with

DOXYGEN_SET_EXAMPLE_RECURSIVE =3D YES

in Makefile.am.

=2D-=20
These are your friends - Adem
GPG: FEA2 A3FE Adriaan de Groot

--nextPart1384132.7BRl7XjMvH
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (FreeBSD)

iD8DBQBEHdmVdqzuAf6io/4RAn76AKCblwplm9zF8hMTALq04U4iVSCprwCeM/T5
yL6gFvEc/2tD0VRjqCDSp/E=
=lrtt
-----END PGP SIGNATURE-----

--nextPart1384132.7BRl7XjMvH--

--===============1650957812==
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 <<

--===============1650957812==--