There is a step where you do:If you want to load VMMaker, you have to do it from the GitHub directions.Hi Nicolai,Question1The Primitives you mention is a class variable.
Put your cursor on it and hit the blue "C" button on the right of the Nautilus code pane to see where it is used.
You'll notice that it is initialized in DiskStore class>>useFilePlugin
useFilePlugin
��� Primitives := FilePluginPrims newFilePluginPrims in turn provides an interface to the real file plugin.
e.g.
FilePluginPrims >> size: id
��� "Answer the size of this file."
��� <primitive: 'primitiveFileSize' module: 'FilePlugin'>
��� self primitiveFailedSo, class variables are WrittenLikeThis and you may thing that it is a class. But it is either a class variable or a global (e.g. Display, Transcript)In a workspace, try: Display class <printIt> Transcript class <printIt>
You'll see the real classes.When using spotlight for example, you'll never find anything if you type Display for example. Even if the completion will propose something to you (hey, someone fixing this?)
Question2cd image && ./newImage.shand it loads all you need and you end up with the generator image.I've been using it in my fork https://github.com/philippeback/pharo-vm
Follow the directions of the README.md and you'll be ready with ease.
If you use OSX, it is working very smoothly.Windows will require some more fiddling but there is nothing stopping you.The generator already has VMMaker in.
Now, please bear in mind that the PharoVM isn't the same VM as Squeak uses, so, the process is not with the Morphic based VMMaker tool (green thing) where you select plugins etc.
Here, you are going to use the PharoVMBuilder which does all of the automation.will generate all CMake files, all Slang based files etc../pharo generator.image eval 'PharoVMBuilder buildWin32'
I plan to do a video of all the steps very soon. This will help.Now, the VMSimulator isn't fully operational in the PharoVM, I am working on getting it right.At this point, it executes bytecodes without problems, but we need to port some more code to the new transcript, filesystem etc.
Just a question of doing it. I am looking at that, hopefully� this will work in december.Hope this clarifies the situation for you.Enjoy,
Phil---Philippe BackDramatic Performance ImprovementsMob: +32(0) 478 650 140 | Fax: +32 (0) 70 408 027Blog: http://philippeback.be | Twitter: @philippebackHigh Octane SPRLrue cour Boisacq 101 | 1301 Bierges | BelgiumPharo Consortium Member -�http://consortium.pharo.org/Featured on the Software Process and Measurement Cast -�http://spamcast.libsyn.com
Sparx Systems Enterprise Architect and Ability Engineering EADocX Value Added Reseller�On Fri, Nov 29, 2013 at 10:55 AM, Nicolai Hess <nicolaihess@web.de> wrote:the generator.image from pharo http://files.pharo.org/vm/src/.BTW it is terrible hard to load vmmaker in a "normal" image. Now I useOk, it has something to do with vm primitives, and I know that code likethat I can not find the source for.What is this "Primitives" not a class? I am suprised there is some codeLooking at the code for DiskStore>>basicEntryAt:I find this code:
"Primitives lookupDirectory: encodedPath filename: encodedBasename)"
<primitive: 'primitiveDirectoryEntry' module: 'FilePlugin'>
is in the vmmaker-package for FilePlugin.
But even in this image it is not possible to load the vmmaker tool.