KDEVELOP_1_4: kdevelop

Bernd Gehrmann bernd at physik.hu-berlin.de
Thu Jun 21 11:32:44 UTC 2001

On Thu, 21 Jun 2001, F at lk Brettschneider wrote:
> > 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. :-(

foodir = $(kde_datadir)/whatever
htdig.conf: $(srcdir)/htdig.conf.in
	sed -e 's/\$foodir/'$foodir'/g' < $(srcdir)/htdig.conf.in > htdig.conf

Add backslashes and apostrophes to taste. Stir well :-)

> > 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???

In HEAD, I use

  KConfig config("khelpcenterrc", true);
  QString exe = config.readEntry("htdig", kapp->dirs()->findExe("htdig"));

If the htdig support in khelpcenter hasn't been removed for KDE 2.2, this
should work.


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

More information about the KDevelop-devel mailing list