Pharo VM

> Hi,
>
> well.. we already have git repositories:
>
> https://gitorious.org/cogvm/blessed
>
> and a cool process to build vm's:
>
> http://marianopeck.wordpress.com/2011/04/10/building-the-vm-from-scratch-using-git-and-cmakevmmaker/
> http://marianopeck.wordpress.com/2011/04/16/building-the-vm-second-part/
>
> and I'm even packaging "pharo branded vm's" for mac:
>
> https://ci.lille.inria.fr/pharo/view/VM/job/Pharo-Mac-Cocoa/
>
> but this last part is just a "start job"... more need to be done.
> to be clear: we are NOT forking cog or anything, just branding it in a way
> who fit us better, and working on plugins we think are needed to be there.
>
> best,
> Esteban
>
> El 21/02/2012, a las 9:58a.m., Schwab,Wilhelm K escribió:
>
> And when do we begin to "live long and prosper" with Spock's help?   Sorry,
> had to ask, it's a wonderful idea.
>
>
> ________________________________________
> From: [hidden email]
> [[hidden email]] on behalf of Pavel Krivanek
> [[hidden email]]
> Sent: Tuesday, February 21, 2012 7:10 AM
> To: Pharo Development
> Subject: [Pharo-project] Pharo VM
>
> Hi Stef,
>
> last year you mentioned that in January you want to brand our own VM.
> Is there any progress in this area? Will there be still two VMs (Cog
> and Stack)? Will we have own git repository?
>
> Cheers,
> -- Pavel
>
>
>

> On 21 February 2012 16:50, Pavel Krivanek <[hidden email]> wrote:
>> I'm asking because Stef mentioned that and I told it to a friend that
>> should create and maintain Fedora packages for Pharo. So he naturally
>> decided to wait....
>>
> Here some news:
> We finally got windows slave up and running. So, now we can build Vms
> for all 3 platforms and test them.
>
> Now there are 2 things left before releasing updated VMs:
> - test why windows VM crashing randomly
> - create an job for building 1-click package.
>
> P.S. An automatic builds often detecting various discrepancies here
> and there, since it doing everything from scratch every time,
> which you usually don't do if run things manually.
> Which is good, because it helps us to ensure that things we do are
> reproducable, but it means having more work :)
>
>
>
> --
> Best regards,
> Igor Stasenko.
>

> - create an job for building 1-click package.
>
> P.S. An automatic builds often detecting various discrepancies here
> and there, since it doing everything from scratch every time,
> which you usually don't do if run things manually.
> Which is good, because it helps us to ensure that things we do are
> reproducable, but it means having more work :)
>
>
>
> --
> Best regards,
> Igor Stasenko.
>

>>>
>> Here some news:
>> We finally got windows slave up and running. So, now we can build Vms
>> for all 3 platforms and test them.
>
> Excellent news to me
>
>>
>> Now there are 2 things left before releasing updated VMs:
>> - test why windows VM crashing randomly
>
> - test why dave mason got mac vm crashing that much.
>
>> - create an job for building 1-click package.
>>
>> P.S. An automatic builds often detecting various discrepancies here
>> and there, since it doing everything from scratch every time,
>> which you usually don't do if run things manually.
>> Which is good, because it helps us to ensure that things we do are
>> reproducable, but it means having more work :)
>>
>>
>>
>> --
>> Best regards,
>> Igor Stasenko.
>>
>
>

>
>> but this last part is just a "start job"... more need to be done.
>> to be clear: we are NOT forking cog or anything, just branding it in a way
>> who fit us better, and working on plugins we think are needed to be there.
>
> yes, the icon for .image has wrong transparency and an ugly font… I
> should apply some obsessive-compulsive detail-fixing effort to that,
> but I need a proper graphics editor ;)
>
>
> --
> Damien Pollet
> type less, do more [ | ] http://people.untyped.org/damien.pollet
>

>>> I've just tried it and it does not find the .sources file that CogVM
>>> cocoa finds fine.
>>
>> what do you mean? where should look for and it doesn't?
>
> I have Pharo.app and PharoV10.sources in the same directory. When I
> opened an image, I had an error dialog saying "could not find
> …/Pharo.app/PharoV10.sources"
>
> It might be still an image problem, I know there were discrepancies
> between Smalltalk vmPath and similar methods / primitives…
>

> On 22 February 2012 16:59, Damien Pollet <[hidden email]> wrote:
>>>> I've just tried it and it does not find the .sources file that CogVM
>>>> cocoa finds fine.
>>>
>>> what do you mean? where should look for and it doesn't?
>>
>> I have Pharo.app and PharoV10.sources in the same directory. When I
>> opened an image, I had an error dialog saying "could not find
>> …/Pharo.app/PharoV10.sources"
>>
>> It might be still an image problem, I know there were discrepancies
>> between Smalltalk vmPath and similar methods / primitives…
>>
> ah yes, we had a discussion about that recently.
> if i remember the vm path should return path to vm binary, not a
> "wrapper" folder which mac using.
>
> just want to make things same for all platforms. then on image side we
> can always differ based on what OS it runs.
>
>> --
>> Damien Pollet
>> type less, do more [ | ] http://people.untyped.org/damien.pollet
>>
>
>
>
> --
> Best regards,
> Igor Stasenko.
>

> (btw... Damien, that problem should be present on any cocoa build, not just Pharo.app :)
>
> Esteban
>
> El 22/02/2012, a las 1:05p.m., Igor Stasenko escribió:
>
>> On 22 February 2012 16:59, Damien Pollet <[hidden email]> wrote:
>>>>> I've just tried it and it does not find the .sources file that CogVM
>>>>> cocoa finds fine.
>>>>
>>>> what do you mean? where should look for and it doesn't?
>>>
>>> I have Pharo.app and PharoV10.sources in the same directory. When I
>>> opened an image, I had an error dialog saying "could not find
>>> …/Pharo.app/PharoV10.sources"
>>>
>>> It might be still an image problem, I know there were discrepancies
>>> between Smalltalk vmPath and similar methods / primitives…
>>>
>> ah yes, we had a discussion about that recently.
>> if i remember the vm path should return path to vm binary, not a
>> "wrapper" folder which mac using.
>>
>> just want to make things same for all platforms. then on image side we
>> can always differ based on what OS it runs.
>>
>>> --
>>> Damien Pollet
>>> type less, do more [ | ] http://people.untyped.org/damien.pollet
>>>
>>
>>
>>
>> --
>> Best regards,
>> Igor Stasenko.
>>
>
>