nolden at kde.org
Thu Jun 21 11:23:57 UTC 2001
"F at lk Brettschneider" wrote:
> Ralf Nolden wrote:
> > CVS by falkbr wrote:
> > >
> > > kdevelop ChangeLog,1.352.2.278.2.127,1.352.2.278.2.128
> > > Author: falkbr
> > > Wed Jun 20 23:49:07 UTC 2001
> > >
> > > Modified Files:
> > > ChangeLog
> > > Log Message:
> > > - finished the redesign of the KDevelop setup by a QWizard
> > > - I noticed htdig hasn't got a htdig.conf file in the KDevelop installation
> > > But how is it supposed to work then?
> > hmmm...if we really want to provide this by ourselves then we should
> > make this a htdig.conf.in that is adapted to the path of the
> > installation ( $prefix ) by make -f Makefile.cvs and turned into a
> > htdig.conf.
> I don't have a clue about automake/autoconf. Someone other must do this
> job. :-(
> > Still, then the problem to locate htdig remains. I don't
> > think you could solve this problem shortterm, currently the distributors
> > are taking care of that to povide a system-specific htdig.conf for their
> > distro's.
> OK. You mean, the distributors will hack into the KDevelop-2.0 package
> and put their locate("appdata", "tools/htdig.conf") in?
> Ralf, how did it work for KDevelop-1.4???
On SuSE, Klaas Freitag adjusts a htdig.conf in the specfile and places
it to the right location on installation
(/opt/kde2/share/apps/kdevelop/tools/htdig.conf) and adds the necessary
dependencies to htdig for the installation. He also makes sure that the
API docs of the KDE 2.x library that's being shipped with the distro is
generated during the build process and placed in /opt/kde2 plus the
pre-set defaults of those pathes. So the user generally has to only run
the index generation dialog, which is named in a special booklet inside
kdevelop on suse how to do that. Please check the 1.3 version shipped
with SuSE 7.1 pro.
I think we can't do much about that currently and taking Bernd's
approach for indexing that's ( I think) from kdehelp or something which
also deals with htdig. Currently, the developer not using a distro
version that covers this stuff is good advised by reading the
README.htdig file in the base directory of the sourcetree and copy that
into his own htdig.conf file plus adjusting the pathes. It's eventually
quite simple and I think the (advanced) user can handle this currently
who is also the same user to install it from scratch on a distro or a
system like BSD or whatever.
PS: I will be away from tomorrow morning on until saturday evening. I
think all issues that needed clearing are already dealt with, but if you
have some questions for things you want to do over the weekend, please
post them here or mail me personally so we can clear this out until
tonight (i.e. in 7/8/9 hours from now). I'll post this to core-devel as
KDE 2 - Trust I seek and I find in You,
everyday for a something new,
open mind for a different view,
and nothing else matters....
nolden at kde.org
The K Desktop Environment The KDevelop Project
to unsubscribe from this list send an email to kdevelop-devel-request at kdevelop.org with the following body:
More information about the KDevelop-devel