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

Steven T. Hatton hattons at globalsymmetry.com
Sat Feb 21 12:14:02 UTC 2004


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

On Friday 20 February 2004 03:53 pm, Friedrich W. H.  Kossebau wrote:
> Am Freitag, 20. Februar 2004 18:20 schrieb Steven T. Hatton:

> > Even easier.  exit KDevelop, rm ~/.kde/share/config/kdevdoctreeviewrc.
> > Restart KDevelop.  It now points to the on-line documentation that all
> > works great. :)
>
> Then restart KDevelop once again: And have all qt and kde links not working
> again. Could it be that the doc part fails with non standard install
> directories somewhere between saving the config and loading it again?
>
> See my automatically new created kdevdoctreeviewrc attached.
>
> Greetings
> Friedrich

I didn't want to bring this up yesterday.  Just as shooting the horse you are 
riding is a bad idea, so is flogging one after it is dead. ;-)  However,  
after I attempted to build KDevelop under my homecooked KDEDIR, I discovered 
that the styles in the KDevelop documentation were applied correctly, as 
opposed to when I built outside of the KDEDIR.  Unfortunately, the 
architecture.html was still missing, as was much of the content in the other 
pages.  This may be due to my not having generated all of the KDE 
documentation.  The only documentation I created was that 
in /download/org/kde/konstruct/kde/kdelibs/work/kdelibs-3.2.0.  After having 
done make apidox and running make install again, I found documentation in the 
$KDEDIR/share/doc/HTML/en/kdevelop-apidocs/html.  I will also observe that 
there *is* (now) a target called install-apidox in that Makefile.  I really 
thought I had run grep correctly when looking for it.  Perhaps I typed docs 
instead of dox?  I'm now trying yet again. to build and install the 
kdelibs-api documentation, and then build KDevelop in that tree.

As far as documentation that I was missing after blowing away the config file, 
the only one I noticed was the kdelibs-api.  Which I will borrow from your 
example.  Thank you.

The worst part about all this is that everytime I try something new, it gets 
just a little closer to the way its supposed to be.  It has been fairly 
time-consumming and distracting.  To my mind,  Helena Petrovna Blavatsky is 
lucid and coherent in comparrison to Makefiles.

I really love books, and electronic documentation is the form in which they 
are now created and stored.  To me this is one of the most important aspects 
of KDevelop, and the KDE in general.  I whish I understood the documentation 
system better.

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

iD8DBQFANz2qH2SF0i7rrGwRAryXAJ9xxxaGvCEw4u2jsBS/0h33SQo1qgCeKuhH
Ww3HHVQ6ujfAyH3K03+Yk/E=
=xCiB
-----END PGP SIGNATURE-----




More information about the KDevelop-devel mailing list