[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-core-devel
Subject:    Re: KLibLoader broken on OSX
From:       Thiago Macieira <thiago () kde ! org>
Date:       2006-10-07 19:02:30
Message-ID: 200610072102.51018.thiago () kde ! org
[Download RAW message or body]


Dirk Mueller wrote:
>Oh, ok. Misunderstanding. I've not claimed that the code is supposed to
> stay that way forever. :) The problem is that we currently have about
> 23 places in KDE (according to lxr), that call KLibrary::findLibrary
> (which maps a lib to an absolute path) without actually loading it. I
> could certainly use the qlibrary code in your test.cpp to implement the
> searching, however I fear that it is a little bit slow to dlopen it
> just for fun. I was planning to get rid of those 23 places to be able
> to remove the findLibrary API ,then we can simplify the stuff a lot and
> benefit from the behaviour in QLibrary you pointed out.

Well, why do they find a library but don't load them? Are you also sure 
they don't load later?

I tried the search in lxr.kde.org and found only 3 circumstances (not 
places) where findLibrary is used without loading the library:

* IOSlave launching (the library is found in klauncher, but kdeinit 
actually opens it)
* kst: I have no idea why it puts the result of findLibrary in a widget
* Kross: it checks for the presence of its Python and Ruby interpreters by 
finding the library instead of finding .desktop files.
-- 
  Thiago Macieira  -  thiago (AT) macieira.info - thiago (AT) kde.org
    PGP/GPG: 0x6EF45358; fingerprint:
    E067 918B B660 DBD1 105C  966C 33F5 F005 6EF4 5358

[Attachment #3 (application/pgp-signature)]

[prev in list] [next in list] [prev in thread] [next in thread]