how to create apidocs for libraries?

mETz mETz81 at
Thu Jun 2 19:14:08 BST 2005

On Dienstag Mai 24 2005 22:07, Adriaan de Groot wrote:
> On Tuesday 24 May 2005 18:02, mETz wrote:
> > topic says it all, how to use admin/ in a project. Right now
> > Noatun has a selfmade "api" target which breaks with srcdir != builddir
> > so I want to use something else. Also aKode is missing a target to create
> > apidocs AFAICS.
> include admin/
> in each and every where docs might be generated, and in their
> parents too. So start with the toplevel, add it there. Create a
> Mainpage.dox with one big /** comment containing documentation with
> optional doxygen @em markup */, re-create Makefile, run make apidox . Now
> add same include (relative path, so add ../) to subdir with suitable doxied
> headers. Same exercise. Docs show up in apidocs/ in builddir.

When adding include admin/ to toplevel and adding a 
Mainpage.dox all I get on apidox target is:

: no rule to create target: apidox-am-toplevel- at KDE_HAS_DOXYGEN@()

I'm using unsermake and I can create apidocs just fine for kdelibs (just 
updated them a few days ago).

Bye, Stefan aka mETz

More information about the kde-core-devel mailing list