The iOS VM has another layout even. And the exe is smaller than 600KB. Phil
2013/3/12 Esteban Lorenzano <esteba...@gmail.com>: > not exactly, but yes, some of the plugins that are internal in Eliot's are > external for pharo (no real important reason: we decided to put as external > as many as possible :) > > Esteban > > On Mar 12, 2013, at 11:15 AM, Frank Shearar <frank.shea...@gmail.com> wrote: > >> Also, it looks like the Pharo VM uses only external plugins? The >> Squeak VM has a bunch of those plugins, but as internal ones. That's >> probably most of the difference Phil's asking about. >> >> frank >> >> On 12 March 2013 09:57, Esteban Lorenzano <esteba...@gmail.com> wrote: >>> We use an automated building method that tries to be exactly the same in >>> each platform. We decided not to create bundles but dylibs because bundles >>> are mac-specific stuff and .dylibs same (but for mac) as .so and .dll. >>> Our process builds the vm, the plugins and the third party libraries as an >>> all-in-one. Eliot builds are hand made, and when there is a process (like >>> the autotool for unix builds), they are platform-specific. >>> >>> TL;DR: Is easier for us to build all the vm stuff in an unified way :) >>> >>> Esteban >>> >>> On Mar 12, 2013, at 10:49 AM, "p...@highoctane.be" <p...@highoctane.be> >>> wrote: >>> >>>> Eliot's CogVM vs PharoVM on Mac application contents. Quite different. >>>> >>>> And worth some explanations :-) Why is it that way? >>>> >>>> Phil >>>> >>>> 2013/3/12 Stephan Eggermont <step...@stack.nl>: >>>>>> It would be good to have a parallel job, but the problem is that you will >>>>>> get a message saying that the VM is too old for the Pharo 2.0 image. >>>>> >>>>> I started the latest MOOSE image on Eliots latest VM on mac. >>>>> It still has the 'old vm' warning. >>>>> Adding a monticello repository (directory) doesn't work. >>>>> Tests are still running >>>>> >>>>> Stephan >>>>> >>>>> >>>> <2013-03-12_10-43-37.png> >>> >>> >> > >
<<attachment: 2013-03-12_11-24-37.png>>
