[Vm-dev] Linux vm default plugins directory

Eliot Miranda eliot.miranda at gmail.com
Wed Sep 1 21:09:04 UTC 2010


On Wed, Sep 1, 2010 at 1:53 PM, Bert Freudenberg <bert at freudenbergs.de>wrote:

>
>
> On 01.09.2010, at 22:38, Eliot Miranda wrote:
>
>
>
> On Wed, Sep 1, 2010 at 12:22 PM, Bert Freudenberg <bert at freudenbergs.de>wrote:
>
>>
>>
>> On 01.09.2010, at 21:12, Eliot Miranda wrote:
>>
>> > Hi Wilhelm,
>> >
>> > On Wed, Sep 1, 2010 at 12:01 PM, Schwab,Wilhelm K <
>> bschwab at anest.ufl.edu> wrote:
>> >
>> >> A recurring theme is that I encounter a problem for which there is no
>> explanation from the system, hack the vm sources to add some tracing, and
>> correct the problem.  As a result, I end up building the vm from source and
>> so tend to use a shell script that runs it.
>> >>
>> > Set LD_LIBRARY_PATH to include the relevant directory.  Here's the
>> script I use at Teleplace
>>
>> The current "squeak" script fills in the plugins path, so there is no need
>> to fiddle with LD_LIBRARY_PATH.
>>
>
> If one has a plugin that depends on a secondary library then fiddling with
> LD_LIBRARY_PATH can be necessary.
>
>
> True, but that's not specific to squeak :)
>

Right.  But -plugins only solves the issue one level deep whereas fiddling
with LD_LIBRARY_PATH, as horribly ugly as that is, solves it for any depth,
hence in my book its the only way to go.

cheers
Eliot
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.squeakfoundation.org/pipermail/vm-dev/attachments/20100901/b6fbddcc/attachment.htm


More information about the Vm-dev mailing list