From koffice-devel  Mon Mar 21 11:53:18 2005
From: David Faure <faure () kde ! org>
Date: Mon, 21 Mar 2005 11:53:18 +0000
To: koffice-devel
Subject: Re: API documentation
Message-Id: <200503211253.19288.faure () kde ! org>
X-MARC-Message: https://marc.info/?l=koffice-devel&m=111140600815425

On Monday 21 March 2005 12:39, Raphael Langerhorst wrote:
> On Monday 21 March 2005 10:18, David Faure wrote:
> > On Saturday 19 March 2005 16:52, Raphael Langerhorst wrote:
> > > Hi everyone,
> > >
> > > I guess we have some kind of API documentation generation, so how
> > > does it currently work? And would it be good to migrate the
> > > current setup to the things in doc/api ?
> >
> > For the website, it currently works with a script (on the
> > webserver) which copies koffice/Doxyfile.temp into each subdir and
> > runs doxygen there.... I'd be happy with a cleaner solution. But I
> > can't use "make apidox" since this requires to configure koffice
> > first, which isn't possible on the webserver. The kdepim solution,
> > instead, looks clean.
> > Does koffice/doc/api generate docu correctly for all of koffice, or
> > does it require Makefile.am changes like the one in kdgantt?
> 
> Well, AFAIK at least make -f Makefile.cvs must be possible to use the 
> doxygen setup.

Right now this is a problem on the webserver (automake-1.6 wanted, 1.4 installed)
and I can't easily install software there (not root).

Since the current setup works, I'm inclined towards leaving it as it is.
Of course this doesn't prevent having something else (nicer?) for 
"make apidox" for developers who want to create their own api docs locally...

-- 
David Faure, faure@kde.org, sponsored by Trolltech to work on KDE,
Konqueror (http://www.konqueror.org), and KOffice (http://www.koffice.org).
_______________________________________________
koffice-devel mailing list
koffice-devel@kde.org
https://mail.kde.org/mailman/listinfo/koffice-devel