2013/10/31 Clément Bera <bera.clem...@gmail.com>

> Does Alien support ARM ?
>

no


>
> How to do FFI on ARM then if NativeBoost and FFI does not support it ?
>

IMHO you should do a VM plugin
easiest and fastest path currently

Luc


>
>
> 2013/10/31 Igor Stasenko <siguc...@gmail.com>
>
>>
>>
>>
>> On 31 October 2013 11:23, Annick Fron <i...@afceurope.com> wrote:
>>
>>> Hi Igor
>>>
>>> I have done that, but still gets an error, do I need to remove
>>> NativeBoost ?
>>> Annick
>>>
>>>
>> FFI not supported on ARM
>>
>>
>>>  Le 30 oct. 2013 à 14:12, Igor Stasenko <siguc...@gmail.com> a écrit :
>>>
>>> AFAIK, it should be in Configurations browser.
>>> Else try this:
>>>
>>> Gofer new
>>>   squeaksource: 'MetacelloRepository';
>>>
>>>   package: 'ConfigurationOfFFI';
>>>   load.
>>>
>>> (Smalltalk at: #ConfigurationOfFFI) project lastVersion load
>>>
>>>
>>>
>>>
>>> On 30 October 2013 09:41, Annick Fron <i...@afceurope.com> wrote:
>>>
>>>> My problem is that the Raspberry does not support native boost (as yet
>>>> !).
>>>> Where can I load the old FFI ?
>>>>
>>>> Le 29 oct. 2013 à 16:57, Igor Stasenko <siguc...@gmail.com> a écrit :
>>>>
>>>>
>>>>
>>>>
>>>> On 29 October 2013 16:27, Annick Fron <i...@afceurope.com> wrote:
>>>>
>>>>> Hi
>>>>>
>>>>> I want to launch a simple init with the following C signature :
>>>>>
>>>>> void gst_init (int *argc, char **argv[])
>>>>>
>>>>> If I write
>>>>>
>>>>> <apicall: void 'gst_init' (int*, char**) module: 'blabla'>
>>>>>
>>>>> I get a Smalltalk syntax error
>>>>>
>>>>> Annick Fron
>>>>>
>>>>>
>>>> To use this syntax, you must load old FFI implementation.
>>>> Or use NativeBoost:
>>>>
>>>> init: intarg with: chararg
>>>>
>>>>  <primitive: 'primitiveNativeCall' module: 'NativeBoostPlugin'>
>>>>
>>>>
>>>>
>>>>
>>>> self nbCall: 'void gst_init (int * intarg, char ** chararg)' module:
>>>> 'blaba'
>>>>
>>>>
>>>> --
>>>> Best regards,
>>>> Igor Stasenko.
>>>>
>>>>
>>>>
>>>
>>>
>>> --
>>> Best regards,
>>> Igor Stasenko.
>>>
>>>
>>>
>>
>>
>> --
>> Best regards,
>> Igor Stasenko.
>>
>
>

Reply via email to