August 2015 - Pharo-users - lists.pharo.org

Re: [Pharo-users] Becoming good at VM development

by stepharo

Hi After the effort made by igor stasenko building the VM is a lot simpler than it used to. Did you try to compile the Pharo VM on your platform? Did you experience some problems? We should probably add a resource page to get started. I do not have the information but we can ask esteban. Stef > Thanks to all for your responses. > I am carefully reading the material presented by you. Ideally I will like to > compile the VM into Chrome's NaCL to run an image under Chrome OS. But first > things first, as they say. I have to understand the Squeak/Pharo VM. > One question, is Mariano's blog still relevant? It seems to me that Pharo VM > is not build that way anymore? > > ãããã¨ãã > > > > -- > View this message in context: http://forum.world.st/Becoming-good-at-VM-development-tp4846536p4847217.html > Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. > >

Aug. 31, 2015

Re: [Pharo-users] Becoming good at VM development

by Mariano Martinez Peck

On Mon, Aug 31, 2015 at 2:49 PM, Ichiseki <is076(a)outlook.com> wrote: > Thanks to all for your responses. > I am carefully reading the material presented by you. Ideally I will like > to > compile the VM into Chrome's NaCL to run an image under Chrome OS. But > first > things first, as they say. I have to understand the Squeak/Pharo VM. > One question, is Mariano's blog still relevant? It seems to me that Pharo > VM > is not build that way anymore? > > The exact instructions on how to compile the VM are not exactly as now. So for that I would recommend reading elsewhere (I think the README in git has some info). A few things have changed. But besides compiling, most of the concepts explained remain the same. Cheers, -- Mariano http://marianopeck.wordpress.com

Aug. 31, 2015

Re: [Pharo-users] Becoming good at VM development

by Ichiseki

Thanks to all for your responses. I am carefully reading the material presented by you. Ideally I will like to compile the VM into Chrome's NaCL to run an image under Chrome OS. But first things first, as they say. I have to understand the Squeak/Pharo VM. One question, is Mariano's blog still relevant? It seems to me that Pharo VM is not build that way anymore? ãããã¨ãã -- View this message in context: http://forum.world.st/Becoming-good-at-VM-development-tp4846536p4847217.html Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

Aug. 31, 2015

Re: [Pharo-users] Publish to Monticello and mirror to git

by Sean P. DeNigris

EstebanLM wrote > with this script (from squeaksource to github): For a Smalltalk solution, I've wrapped and tweaked the original MC script that was floating around on the lists. It needs a cleanup and won't work on Windows because I used NBMacShell, but could easily be cleaned up if others find it helpful. In Pharo 4.0 (may work in 5.0): Metacello new repository: 'github://seandenigris/MonticelloProjectMigrate/repository'; baseline: 'McProjectMigrate'; load. See the class comment for a usage example: | source destination files | source := MCHttpRepository allSubInstances detect: [ :e | e location includesSubstring: 'Playground' ]. destination := MCHttpRepository allSubInstances detect: [ :e | e location includesSubstring: 'Engelbart' ]. files := source allVersionNames select: [ :e | e includesSubstring: 'Chord' ]. McProjectMigrate new source: source; destination: destination; versionFilenames: files; execute. For git, just specify a filetree repo as the destination, and you'll want to replace the final send of #execute with #executeBitbucket (nothing BitBucket-specific; as I said it needs a cleanup!). N.B. The only part that is not handled is filtering existing versions. I wasn't sure how to compare mcz versions with their git counterparts, so it pushes them all by default. ----- Cheers, Sean -- View this message in context: http://forum.world.st/Publish-to-Monticello-and-mirror-to-git-tp4846989p484… Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

Aug. 31, 2015

Re: [Pharo-users] Publish to Monticello and mirror to git

by HernÃ¡n Morales Durand

Thank you for this Esteban. I dreamed about a magic button in MC :) cheers, HernÃ¡n 2015-08-31 6:10 GMT-03:00 Esteban Lorenzano <estebanlm(a)gmail.com>: > This does not have anything to do with Pharo so no matter the version :) > > I keep in sync the VMMaker repositories using a jenkins job with this > script (from squeaksource to github): > > #! /bin/bash > > set -e > > eval `ssh-agent` > ssh-add $HOME/.ssh/id_rsa_estebanlm > > PACKAGES="'VMMaker.oscog'" > REPOSITORY=cog > > # Clone > git clone -b spur64 git@github.com:estebanlm/pharo-vm.git $REPOSITORY > cd $REPOSITORY > git config --local user.email "estebanlm(a)gmail.com" > git config --local user.name "Esteban Lorenzano" > cd - > > > # Get Pharo (and prepare it) > wget -O- get.pharo.org/50+vm | bash > ./pharo Pharo.image get OSProcess > > # Execute sync script > ./pharo Pharo.image eval " > | origin destination | > > origin := (MCHttpRepository location: 'http://source.squeak.org/VMMaker') > instVarNamed: 'cacheFileNames' put: true; > yourself. > destination := MCFileTreeRepository new > directory: '$REPOSITORY/mc' asFileReference ensureCreateDirectory; > instVarNamed: 'cacheFileNames' put: true; > yourself. > > #($PACKAGES) do: [ :eachPackageName | > | infoOrigin infoDest versionNumber newer | > > VTermOutputDriver stdout black: 'Updating ', eachPackageName; lf. > > infoOrigin := origin versionInfoFromVersionNamed: eachPackageName. > infoDest := destination versionInfoFromVersionNamed: > eachPackageName. > versionNumber := infoDest versionNumber. > > newer := (({infoOrigin}, (infoOrigin allAncestors)) > select: [ :each | > each versionNumber > versionNumber > or: [ > each versionNumber = versionNumber > and: [ each id ~= infoDest id ] ] > ]) > sorted: [ :a :b | a timeStamp < b timeStamp ]. > > newer do: [ :each | | summary | > [ > VTermOutputDriver stdout green: ('New version: ', > each name); lf. > > VTermOutputDriver stdout << 'Store ' << each name > << ' in ' << destination description; cr. > destination storeVersion: (origin > versionFromFileNamed: (each name, '.mcz')). > > VTermOutputDriver stdout << 'Commit ' << each > name; cr. > summary := each summary copyReplaceTokens: String > cr with: String crlf. > OSProcess waitForCommand: '(cd $REPOSITORY; git > add -A ; git commit -m \"', summary, '\")' ] > on: Error do: [ :e | > VTermOutputDriver stdout yellow: ('Warning: ', e > messageText); lf ] ] ]. > > VTermOutputDriver stdout << 'OK'; cr. > " > > cd $REPOSITORY > git push --force origin spur64 > git branch --verbose > cd - > > git stuff is to add my credentials, thatâs because I use one of our > structure servers. One of your own shouldnât need that part. > > basically, script does: > > 1) clone mirrored repo > 2) run a script comparing PACKAGES and versions, generate a new > export+commit for each new version. > 3) does a push with all new commits > > cheers, > Esteban > > > > On 30 Aug 2015, at 21:23, HernÃ¡n Morales Durand < > hernan.morales(a)gmail.com> wrote: > > > > Is it possible right now in Pharo 4 or 5 on any platform? > > > > Cheers, > > > > HernÃ¡n > > > > >

Aug. 31, 2015

Re: [Pharo-users] Publish to Monticello and mirror to git

by Esteban Lorenzano

This does not have anything to do with Pharo so no matter the version :) I keep in sync the VMMaker repositories using a jenkins job with this script (from squeaksource to github): #! /bin/bash set -e eval `ssh-agent` ssh-add $HOME/.ssh/id_rsa_estebanlm PACKAGES="'VMMaker.oscog'" REPOSITORY=cog # Clone git clone -b spur64 git@github.com:estebanlm/pharo-vm.git $REPOSITORY cd $REPOSITORY git config --local user.email "estebanlm(a)gmail.com" git config --local user.name "Esteban Lorenzano" cd - # Get Pharo (and prepare it) wget -O- get.pharo.org/50+vm | bash ./pharo Pharo.image get OSProcess # Execute sync script ./pharo Pharo.image eval " | origin destination | origin := (MCHttpRepository location: 'http://source.squeak.org/VMMaker') instVarNamed: 'cacheFileNames' put: true; yourself. destination := MCFileTreeRepository new directory: '$REPOSITORY/mc' asFileReference ensureCreateDirectory; instVarNamed: 'cacheFileNames' put: true; yourself. #($PACKAGES) do: [ :eachPackageName | | infoOrigin infoDest versionNumber newer | VTermOutputDriver stdout black: 'Updating ', eachPackageName; lf. infoOrigin := origin versionInfoFromVersionNamed: eachPackageName. infoDest := destination versionInfoFromVersionNamed: eachPackageName. versionNumber := infoDest versionNumber. newer := (({infoOrigin}, (infoOrigin allAncestors)) select: [ :each | each versionNumber > versionNumber or: [ each versionNumber = versionNumber and: [ each id ~= infoDest id ] ] ]) sorted: [ :a :b | a timeStamp < b timeStamp ]. newer do: [ :each | | summary | [ VTermOutputDriver stdout green: ('New version: ', each name); lf. VTermOutputDriver stdout << 'Store ' << each name << ' in ' << destination description; cr. destination storeVersion: (origin versionFromFileNamed: (each name, '.mcz')). VTermOutputDriver stdout << 'Commit ' << each name; cr. summary := each summary copyReplaceTokens: String cr with: String crlf. OSProcess waitForCommand: '(cd $REPOSITORY; git add -A ; git commit -m \"', summary, '\")' ] on: Error do: [ :e | VTermOutputDriver stdout yellow: ('Warning: ', e messageText); lf ] ] ]. VTermOutputDriver stdout << 'OK'; cr. " cd $REPOSITORY git push --force origin spur64 git branch --verbose cd - git stuff is to add my credentials, thatâs because I use one of our structure servers. One of your own shouldnât need that part. basically, script does: 1) clone mirrored repo 2) run a script comparing PACKAGES and versions, generate a new export+commit for each new version. 3) does a push with all new commits cheers, Esteban > On 30 Aug 2015, at 21:23, HernÃ¡n Morales Durand <hernan.morales(a)gmail.com> wrote: > > Is it possible right now in Pharo 4 or 5 on any platform? > > Cheers, > > HernÃ¡n >

Aug. 31, 2015

Re: [Pharo-users] where to find the ia32/i386 runtime libraries

by Sven Van Caekenberghe

One among many: https://www.youtube.com/watch?v=I5ogPOs3PLM might help. Please ask again if you keep on having problems. > On 31 Aug 2015, at 09:39, Ben Coman <btc(a)openInWorld.com> wrote: > > It would seem you already have the necessary ia32 libs since you have successfully opened Pharo. So the VM is there. I think you may not have chosen Don't from the context menu of the selection. > Cheers ben > > On 31 Aug 2015 11:47 am, "albert" <albert(a)spiritone.com> wrote: > Dear Sirs: > > I have: opensuse 13.2 x86_64, and glibc 2.19. > So, I downloaded: Default GNU/Linux Pharo4.0-linux.zip. > > After extracting zip, README.txt says: > ~ Just install the ia32/i386 runtime libraries and you should be fine. > > However, there are no files with such names among the extracted files. > > How to proceed installing the runtime libraries? > In advance, thank you. > > > By the way, opening pharo tells me: > ~ You can learn pharo by highlighting the next line and selecting [Do it] from the context menu:" > PharoTutorial go. > > Obviously, nothing happens when following these instructions -- the vm isn't there. > > When closing the pharo environment window, I get asked to save any changes. > At least, I get a dialog widget. > > Thanks, > Albert

Aug. 31, 2015

Re: [Pharo-users] where to find the ia32/i386 runtime libraries

by Ben Coman

It would seem you already have the necessary ia32 libs since you have successfully opened Pharo. So the VM is there. I think you may not have chosen Don't from the context menu of the selection. Cheers ben On 31 Aug 2015 11:47 am, "albert" <albert(a)spiritone.com> wrote: > Dear Sirs: > > I have: opensuse 13.2 x86_64, and glibc 2.19. > So, I downloaded: Default GNU/Linux Pharo4.0-linux.zip. > > After extracting zip, README.txt says: > ~ Just install the ia32/i386 runtime libraries and you should be fine. > > However, there are no files with such names among the extracted files. > > How to proceed installing the runtime libraries? > In advance, thank you. > > > By the way, opening pharo tells me: > ~ You can learn pharo by highlighting the next line and selecting [Do it] > from the context menu:" > PharoTutorial go. > > Obviously, nothing happens when following these instructions -- the vm > isn't there. > > When closing the pharo environment window, I get asked to save any changes. > At least, I get a dialog widget. > > Thanks, > Albert >

Aug. 31, 2015

where to find the ia32/i386 runtime libraries

by albert

Dear Sirs: I have: opensuse 13.2 x86_64, and glibc 2.19. So, I downloaded: Default GNU/Linux Pharo4.0-linux.zip. After extracting zip, README.txt says: ~ Just install the ia32/i386 runtime libraries and you should be fine. However, there are no files with such names among the extracted files. How to proceed installing the runtime libraries? In advance, thank you. By the way, opening pharo tells me: ~ You can learn pharo by highlighting the next line and selecting [Do it] from the context menu:" PharoTutorial go. Obviously, nothing happens when following these instructions -- the vm isn't there. When closing the pharo environment window, I get asked to save any changes. At least, I get a dialog widget. Thanks, Albert

Aug. 31, 2015

Publish to Monticello and mirror to git

by HernÃ¡n Morales Durand

Is it possible right now in Pharo 4 or 5 on any platform? Cheers, HernÃ¡n

Aug. 30, 2015