[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-devel
Subject:    'make doc' (was:Re: Documentation standard ??)
From:       Matthias Elter <me () main-echo ! net>
Date:       1999-07-07 15:55:22
[Download RAW message or body]

On Wed, 07 Jul 1999, Michael Koch wrote:
> Am Mit, 07 Jul 1999 schrieb Stephan Kulow:
> > Michael Koch wrote:
> > > 
> > > > >
> > > > Well, I like to have the documentation in the headers.
> > > 
> > > Well, the documentation is in the headers, but some people (like me) want to
> > > have HTML- or TEX-Documentation of the API. Thatīs why Iīm using kdoc every day.
> > > 
> > Well, I was refering to the way doxygen does it. There most stuff is in
> > the sources.
> 
> Ah, I see, another concept.
> 
> We need to decide this. When the pre-2.0-libs (1.89) are shipped, there should
> be a HTML-documentation included or as extra tgz or whatever. Thats for
> developers switching to KDE-2.0 programming. Different documentation tools used
> in the libs are very bad.

Have a look into current Linux distros, most if not all do not ship with KDE
library docu...know why? Packagers are lazy ;) they don't want to download kdoc
(kdesdk) and generate the docu by hand. Why not simply move kdoc into kdesupprt
(its just a few KB) and add a 'docu' target to kdelibs/Makefile.am
(Stephan?:) that automagically generates the docu?

-- 
Matthias Elter
me@kde.org / me@main-echo.net
Computer science student university of Wuerzburg

[prev in list] [next in list] [prev in thread] [next in thread]