Re: [Pharo-users] Pharo and Pi

2015-03-19 Thread itli...@schrievkrom.de
I found the NB approach as a fresh breeth of air - beside all the problems (I am/was not aware of). Marten -- Marten Feldtmann

Re: [Pharo-users] Pharo and Pi

2015-03-18 Thread stepharo
Stef wrote: Our goal is to remove the dependencies to nativeboost. I know that FFI is now maintained again and there is some initiative on a (more) unified FFI. Also there may be some issues with NB: harder to understand than FFI, not complete for ARM, ... not working with Spur, not working w

Re: [Pharo-users] Pharo and Pi

2015-03-18 Thread stepharo
Our goal is to remove the dependencies to nativeboost. So we will release Pharo 40 and esteban will work on an FFI to remove NB. Stef Le 18/3/15 16:33, Sebastian Heidbrink a écrit : Hi Torsten, we tried to start pharo 4.0 on the Parallella board , which is somehow like the Pi2 and did succeed

Re: [Pharo-users] Pharo and Pi

2015-03-18 Thread itli...@schrievkrom.de
As I posted on my blog yesterday: Pharo 3 is running. Marten Am 18.03.2015 um 15:35 schrieb Torsten Bergmann: > Read about "piCore" this week which is a Tiny Core Linux > for the Pi. > > As there is > - a quick bootable Pharo on top of TinyLinux (Mikes "PharoNOS" project) > - a Pharo that is

Re: [Pharo-users] Pharo and Pi

2015-03-18 Thread Sebastian Heidbrink
Hi Torsten, we tried to start pharo 4.0 on the Parallella board , which is somehow like the Pi2 and did succeed partially. The problem with Pharo4 and the VM is that there is no NativeBoost nor OSProcess available o ARM VMs. I just strated to do some reseach on this and can't provide more

Re: [Pharo-users] Pharo and Pi - FastBltBit

2015-03-18 Thread Mircea
Also here: https://ci.inria.fr/pharo-contribution/view/ARM-Raspberry/job/RaspberryPi-Cross-Compilation-FastBltBit/ What does FastBltBit mean? Google turns up some results but they are inco

Re: [Pharo-users] Pharo and Pi

2015-03-18 Thread Mircea
Count me in too. Just bought two Pi 2s and rand the PharoS VM on top or Raspbian OS (linux). Quick conclusion. Running apps is fine, but optimizations seem lacking somehow as it took 30 minutes to install and compile Seaside and it only ever used one processor of the Pi 2’s four (quad-core). T