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

Friedrich W. H. Kossebau Friedrich.W.H at Kossebau.de
Fri Feb 20 21:55:05 UTC 2004

Am Freitag, 20. Februar 2004 18:20 schrieb Steven T. Hatton:
> On Friday 20 February 2004 11:10 am, Amilcar do Carmo Lucas wrote:
> > Steven T. Hatton wrote:
> > > cd kde/kdelibs/work/kdelibs-3.2.0/
> > > make apidox
> > > mv apidocs <whereever>
> >
> > It works MUCH better if you replace
> > mv apidocs <whereever>
> > with
> > make apidox-install
> That's not a target in the kdelibs-3.2.0/Makefile.  I have been doing that
> in the kdevelop cvs tree.
> > After doing the kdelibs API doc install you need to reconfigure kdevelop.
> 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.

-------------- next part --------------
[General Doxygen]
KDE Libraries (Doxygen)=$HOME/Programmieren/kdeinstall/share/doc/HTML/en/kdelibs-apidocs

[General Qt]
Guide to the Qt Translation Tools=$HOME/Programmieren/kdeinstall/doc/html/linguist.dcf
Qt Assistant Manual=$HOME/Programmieren/kdeinstall/doc/html/assistant.dcf
Qt Designer Manual=$HOME/Programmieren/kdeinstall/doc/html/designer.dcf
Qt Reference Documentation=$HOME/Programmieren/kdeinstall/doc/html/qt.dcf
qmake User Guide=$HOME/Programmieren/kdeinstall/doc/html/qmake.dcf


More information about the KDevelop-devel mailing list