KHTML Thai Word Break patchc

[Simon Hausmann]

On Friday 07 May 2004 00:10, Lars Knoll wrote:
> On Thursday 06 May 2004 18:33, David Faure wrote:
> > On Thursday 06 May 2004 18:24, Lars Knoll wrote:
> > > On Thursday 06 May 2004 18:15, David Faure wrote:
> > > > On Thursday 06 May 2004 18:01, Pattara Kiatisevi wrote:
> > > > > I have tested your code, there is some problems with the:
> > > > >
> > > > >  KLibrary *lib = loader->library("libthai");
> > > > >
> > > > > I have to change this "libthai" to "libthai.so.0" to make it work
> > > > > but I'm not sure it is a good idea to do that. A symlink
> > > > > /usr/lib/libthai.so --> /usr/lib/libthai.so.0 didn't help.
> > > >
> > > > I suppose this is because there is no libthai.la (libtool file),
> > > > right? In that case, giving "libthai.so" or "libthai.so.0" to
> > > > KLibLoader is the only way indeed. Given that ".so" files are for
> > > > development and not for runtime, giving "libthai.so.0" sounds correct
> > > > to me.
> > >
> > > At least my installation of libthai (downloaded the sources yesterday)
> > > installs a .la file. But it installs into /usr/local by default, could
> > > that make a difference?
> >
> > Yes, KLibLoader accepts full paths, but otherwise simply looks in the KDE
> > directories (for the resources "lib" and "module").
> > I guess this needs a configure check, that finds libthai.la, and saves
> > its location to config.h, so that you can give the full path to
> > KLibLoader::library().
>
> libthai only links against libc and has no other dependencies. In this case
> I think it might be fine to just open it with "libthai.so".

I think the safest way would be to open libthai.so.0 . libthai.so and 
libthai.la are usually put into development packages because in the regular 
packages they'd break multiple installations of the same library in differing 
major versions, and usually they are needed at link time only anyway. So 
either you open those and require people to install the development package 
of libthai or you stay with libthai.so.0 for example and by this also assure 
that the ABI is stable, because you either get the one of libthai.so.0 or 
you'd otherwise get a library with a different major version, which usually 
means breakage of ABI, which is better to avoid at run-time :)

Simon