On Wed, Sep 14, 2016 at 4:21 PM, Blondeau Vincent
<vincent.blond...@worldline.com> wrote:
>> >
>> >>
>> >> I try to move the R dll close to my Pharo VM and also inside the
>> >> Plugins directory but without success ...
>> >
>> > It should be at the same location that libcairo.2.dylib
>> >
>> >> Is there a way to say where are the R dll instead of copying them ?
>>
>> Are you using the system to do the library path resolution? Or finding the
>> library file in Pharo and then passing an absolute path to FFI?
>
> I think that the system that do the resolution:
> I defined in a trait:
> ffiLibraryName
> ^ #R
> And the library is named R.dll (under windows).
>
> Maybe I should do like CairoLibrary?
My limited understanding is that #ffiLibraryName should return a class
rather than a symbol. Thus...
MyClass class >> ffiLibraryName
^ R
R >> win32ModuleName
^ 'libr.N.dll'. "or whatever is the actual dll filename"
cheers -ben
