[Vm-dev] plugin location
bert at freudenbergs.de
Thu Aug 27 09:10:45 UTC 2009
On 27.08.2009, at 10:36, Andrew Gaylard wrote:
> On Thu, Aug 27, 2009 at 4:16 AM, Ian
> Piumarta<piumarta at speakeasy.net> wrote:
>> Does anyone use the plugin mechanism to load libraries that are not
>> on Unix? Or to override just one or two of the installed ones from
>> a user
>> I'm thinking of simplifying the search strategy (which is indeed
>> w.r.t. overriding installed plugins as Subbu points out) along with
>> all the
>> junk related to probing for a zillion prefixes and suffixes. Unlike
>> libtool, CMake manages to build loadable modules with predictable
>> names regardless of the platform. That, combined with a launch
>> script that
>> can add a -plugins option to the VM args, suggests it ought to be
>> to find the plugin precisely on the first attempt, without having
>> to search
>> at all.
>> The advantage is vastly simpler logic that is completely predictable.
>> The disadvantage is that it will not be possible to subvert the
>> mechanism to load system libraries, and it will not be possible to
>> the installed plugins with a single plugin built in a different
>> Would either of these be a noticeable loss?
> Nope. Go for it!
> - Andrew
As for debugging, what I usually do is symlink the plugin from my
build dir to the default plugin dir.
Out of curiosity, which other extensions than .so are in use currently?
- Bert -
More information about the Vm-dev