it depends. Sometimes, passing a wrong type of argument through nbffi (because of a badly wrapped signature), breaks the VM, almost but not completely freezing it while consuming 100% CPU. Maybe this is happening, but in that case the native window would probably not open.��

On Fri, May 18, 2012 at 5:29 PM, Igor Stasenko <siguctua@gmail.com> wrote:
On 18 May 2012 07:34, chadwick <mathnoir@gmail.com> wrote:
>
>>
>> yeah.. but make sure you linking with right 32bit lib.. otherwise you
>> will get things like that.
>>
>
>
> ok I changed the FFI path to OpenGL library to
> /usr/lib32/nvidia-current-updates/libGL.so.1/usr/lib32/nvidia-current-updates/libGL.so.1
>
> and now
>
> GLTTRenderingDemo new openInWorld.
>
> does something, i.e. there's no error either in Pharo or in the console, but
> I don't see anything, there's just a sense that something is being computed
> as the machine runs slower.
>
hard to say anything. looks like it renders something somewhere but
then results are lost.


--
Best regards,
Igor Stasenko.




--
Lic. Javier Pim��s
Ciudad de Buenos Aires