[Pkg-kde-talk] arts and kdelibs uploaded to alioth
Gary Cramblitt
garycramblitt@comcast.net
Mon, 28 Feb 2005 15:38:27 +0000
On Monday 28 February 2005 07:54 pm, Pierre Habouzit wrote:
> in fact, my real concerns with kdeaccessibility is not really wrt
> ksttd/ksayit/kdemultilmedia deps, but some stange things wrt some
> includes, and some shared libraries (I think we'll have to provide a
> libkttsd + a libkttsd-dev package). But I have to study that a bit
> more ;)
If you assume there will be a kdelibs-dev that installs
kdelibs/interfaces/kspeech/kspeech.h and kspeechsink.h, then a kttsd-dev is
not required.
If you are talking about kdeaccessibility/kttsd/libkttsd, it is convenience
library for kttsd development. Anyone working on kttsd will work with the
entire source, so there should not be a separate libkttsd package. (But
don't confuse this with ksayit/KTTSD_Lib, which is a convenience library for
ksayit.)
There are some things going on with includes that might confuse. Applications
using kttsd typically include the kspeech.h and kspeechsink.h files, which
are installed from kdelibs/interfaces/kspeech. They define the dcop
interface to kttsd and are compiled with dcop2idl. A copy of these files is
in the compat directory so that kttsd can be built for older KDEs (3.2 and
above). configure.in.in detects if the .h files are installed, and if not,
gets them from the compat directory. So, as I said, as long as you assume
there will be a kttsd-dev that installs these .h files, then a kttsd-dev is
not required.
But you are the expert. Hope this helps.
--
Gary Cramblitt (aka PhantomsDad)
KDE Text-to-Speech Maintainer
http://accessibility.kde.org/developer/kttsd/index.php