documentation inside gideon

[Bernd Gehrmann]

On Fri, 8 Jun 2001, Thomas Fromm wrote:
> > The way it is currently implemented is that all tables of contents
> > that are installed in $prefix/share/kdevdoctreeview/tocs (iirc) are
> > displayed in the tree. This works for the python, perl and php docu-
> > mentation if it is detected by configure. If this doesn't work for
> > you (or someone else), look in gideon.m4.in and add your distribution-
> > specific path in the 'phpdocdirs=' line. I think I'll also add some
> > more warnings in configure.in.bot so that the user who compiles from
> > source can immediately see when something went wrong without going
> > through the whole configure output.
> 
> ok, but whats when gideon is shipped as rpm? for this case nobody calls a 
> configure, and then is the question when the dokumentation is morphed via
> .xsl. 
> at startup? 

When the rpm is built with the correct build dependencies (i.e. e.g.
the PHP and Python packages), then the files in doc/3rdparty get
configured accordingly and are read at startup.

Bernd.


-
to unsubscribe from this list send an email to kdevelop-devel-request at kdevelop.org with the following body:
unsubscribe »your-email-address«