Just had a quick start with TalkFFI ... and after getting 32bit libs on Mac OS X it finally worked.

However running TalkFFI results in a wallback because (I assume) a type can't be infered. Is there any way to debug TalkFFI to get the C name of the offending type/function? All I'm seeing are their addresses :-(

CU,

Udo


On 24/03/15 17:33, kilon alios wrote:
If the library is big you can use TalkFFI (you will find it in
smalltalkhub) that automates the wrapping with nativeboost.

On Tue, Mar 24, 2015 at 4:58 PM, Udo Schneider
<udo.schnei...@homeaddress.de
<mailto:udo.schnei...@homeaddress.de>> wrote:

    I guess not :-)

    I'll try to wrap libUSB then.

    I assume the future-proof way to use "a" FFI framework is to use the
    NB notation? Do I remember correctly that the NB notation is
    supposed to remain the same although the backend will change to
    something more like traditional FFI?
    So using NB notation w/o relying on the code generation is safe,
    correct?

    CU,

    Udo



    On 23.03.2015 16:15, Udo Schneider wrote:

        All,

        does anybody have some code or plugin to access USB ports with
        Pharo?
        Maybe something using libUSB or OpenUSB?

        Thanks,

        Udo










Reply via email to