[Vm-dev] plugin location

Douglas Brebner squeaklists at fang.demon.co.uk
Thu Aug 27 12:21:08 UTC 2009

Andreas Raab wrote:
> Ian Piumarta wrote:
>>> Would this affect the FFI and its attempts to load platform libraries?
>> It would continue to find anything that dlopen() would find; i.e.,
>> anything with the platform's expected prefix and suffix in the
>> standard shared library locations including whatever influence
>> environment variables might have on the search.
> But it wouldn't find it in any of the "additional" locations that you
> were looking at, right? It's probably okay (most Unix users know that
> they have to set LD_LIBRARY_PATH) but I'm still a little concerned
> that this may break apps if people switch from one VM to the next.
> Perhaps leave it as an option for the FFI and drop it for good on the
> 4.0 switch? (changes in major versions are just easier to explain than
> the change from 3.10-6 to 3.10-7 ;-)
On platforms using ELF executables you can embed paths for the run time
linker into the exe itself so each vm (and plugin) can be built to look
in its own specific places.

More information about the Vm-dev mailing list