"Dirk A. Mueller" wrote:
> 
> On Die, 04 Jan 2000, Mosfet wrote:
> 
> > > a) locate the lib ourself and give lt_dlopen() the full path
> > Ah, this is the problem. I always install the modules in the KDE library
> > directory then use  KStdDirs with "lib" as the type to get their full
> > path.
> 
> So it should be fixed this way?
> 
> Well, still somehow suboptimal because I think the ldconfig cache is still
> faster than locating the thing on our own, maybe traversing half of the disk
> until we find it. Unfortunately ldconfig does only work with .so files.
> 
> why at all do we need that .la files? what's their advantage? lt_dlopen()
> seem to handle the pure .so files pretty well.
> 
> In addition we're loosing some functionality here. I don't think that
> locate("lib", "..") searches always in the same places like /etc/ld.so.conf
> does. so it might be unclear for users why KDE 2.0 won't find it's libs even
> if they have set ld.so.conf correctly.
> 
> Do we really need the yet another layer of complexity above ld.so.conf ?
> 
Hmm, isn't ld.so.conf only for ld.so? kinit works around ld.so exactly
because
it sucks :)

Greetings, Stephan

-- 
Programmers, heed this: If someone starts asking you about
agricultural genomes, it's likely time to get a handler. 
                                zdnet.com about Torvalds