What my build scrip *really* looks like. w/API DOCS problem

[Steven T. Hatton]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Friday 20 February 2004 05:52 am, Amilcar do Carmo Lucas wrote:
>
> It somehow does not find the tag files that should come with the kdelibs
> API documentation.
> If your kdelibs API documentation does not have .tag files then there is
> no way of building any decent
> KDevelop API documentation

Steve Binner was kind enough to reply to my request for help, and tell me I 
could build the API documentation for the KDELIBS from the konstruct tree as 
follows:

 cd kde/kdelibs/work/kdelibs-3.2.0/
 make apidox
 mv apidocs <whereever>

Strangely, that created a directory called ...work/kdelibs-3.2.0/apidocs, not 
kdelibs-apidocs.  I created a directory called /home/apidox/public and 
symlinked the apidocs to /home/apidox/public/cvs-api.  That got rid of these 
messages: "Error: Tag file `/home/apidox/public/cvs-api/dcop/dcop.tag' does 
not exist or is not a file. Skipping it..."  But I still have no 
architecture.html. 

I think I've had enough fun with doxygen for the week.  I tried following what 
was going on in the Doxygen.am and Makefile.am at the root of the kdevelop 
cvs source, but I have to admit, I get a bit lost.

Thanks for the help.  I may revisit this in the future, but for now, it's 
probably not a productive use of my time.

STH
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)

iD8DBQFANiksH2SF0i7rrGwRAhPDAJ9gA2pLm3mgsC863xjReoBYFxs52ACgxAQP
ksZ1r1nESsm6GD0CeM5R030=
=6s9v
-----END PGP SIGNATURE-----