What my build scrip *really* looks like. w/API DOCS problem
Steven T. Hatton
hattons at globalsymmetry.com
Fri Feb 20 18:20:07 UTC 2004
-----BEGIN PGP SIGNED MESSAGE-----
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>
> 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
> After making kdevelop API documentation you'll get a warning about
> having to install it.
> Do not ignore this warning.
> Install it.
> (you do not need to be root if you install it to some place you have
> permissions to)
> The same applies to kdelibs API dox
> I've wasted enough time fixing Makefile.am and Doxygen.am. All you have
> to do is follow the instructions.
> If you want to do it differently then send in a patch, I'll review it.
One thing I haven't tried is to build KDevelop in the KDEDIR I built in my
user space. I really think that's the problem. That is, when the KDevelop
documentation is created, it wants to see KDevelop under $KDEDIR. And that is
consistent with the instructions. I hope running from a different KDEDIR that
the one I built in doesn't cause too many problems.
Unfortunately, with the way SuSE packaged things, I don't believe I could use
their installation to created the documentation. But that certainly isn't
the fault of anybody on the KDevelop project.
> Have fun,
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)
-----END PGP SIGNATURE-----
More information about the KDevelop-devel