Hi Igor. I was thinking a couple of things:
1) So...once I hace download anything from GIT, what I always need to do is: a) take a pharo core 1.3 b) open the LoadVMMaker.st so that I can see which versions of metacello and cmake I need. c) evaluate that over the pharo image d) move my image to /build so that it finds the /src and /platform by default
So...I wonder what are the reason of not having such PharoCore image already commited in GIT under /image. You can even save it with a workspace opened with the code of LoadVMMaker.st is it just the size of it?
If I want to do it for myself, what is the best strategy? clone to my own fork, add the image there and then just pull the changes?
2) #prepareVMMaker does this:
prepareVMMaker
| maker allPlugins |
maker := VMMaker forPlatform: 'Cross'. maker sourceDirectoryName: (self srcDir assureExistence fullName). maker platformRootDirectoryName: (self topDir / 'platforms' ) fullName.
And
srcDir "Answer the value of srcDir"
^ srcDir ifNil: [ srcDir := self topDir / 'src' ]
This is cool because I can script the cong to use another src. But you don't do the same for 'platform'. So I cannot do:
CogDebugMacOSConfig new srcDir: 'myFolder'; platformsDir: 'myPlatofrm'; generateSources; generate.
Since the platform directory will be overwritten.
Cheers
Mariano
On 3 April 2011 11:45, Mariano Martinez Peck marianopeck@gmail.com wrote:
Hi Igor. I was thinking a couple of things:
- So...once I hace download anything from GIT, what I always need to do is:
a) take a pharo core 1.3 b) open the LoadVMMaker.st so that I can see which versions of metacello and cmake I need. c) evaluate that over the pharo image d) move my image to /build so that it finds the /src and /platform by default
So...I wonder what are the reason of not having such PharoCore image already commited in GIT under /image. You can even save it with a workspace opened with the code of LoadVMMaker.st is it just the size of it?
If I want to do it for myself, what is the best strategy? clone to my own fork, add the image there and then just pull the changes?
- #prepareVMMaker does this:
prepareVMMaker
| maker allPlugins |
maker := VMMaker forPlatform: 'Cross'. maker sourceDirectoryName: (self srcDir assureExistence fullName). maker platformRootDirectoryName: (self topDir / 'platforms' ) fullName.
And
srcDir "Answer the value of srcDir"
^ srcDir ifNil: [ srcDir := self topDir / 'src' ]
This is cool because I can script the cong to use another src. But you don't do the same for 'platform'. So I cannot do:
CogDebugMacOSConfig new srcDir: 'myFolder'; platformsDir: 'myPlatofrm'; generateSources; generate.
Since the platform directory will be overwritten.
probably a mistake. platforms dir should also be configurable. and it should use it if it set.
Cheers
Mariano
Ok. I will commit later the fix. Cheers
Mariano
On Mon, Apr 4, 2011 at 3:00 AM, Igor Stasenko siguctua@gmail.com wrote:
On 3 April 2011 11:45, Mariano Martinez Peck marianopeck@gmail.com wrote:
Hi Igor. I was thinking a couple of things:
- So...once I hace download anything from GIT, what I always need to do
is:
a) take a pharo core 1.3 b) open the LoadVMMaker.st so that I can see which versions of metacello
and cmake I need.
c) evaluate that over the pharo image d) move my image to /build so that it finds the /src and /platform by
default
So...I wonder what are the reason of not having such PharoCore image
already commited in GIT under /image. You can even save it with a workspace opened with the code of LoadVMMaker.st
is it just the size of it?
If I want to do it for myself, what is the best strategy? clone to my
own fork, add the image there and then just pull the changes?
- #prepareVMMaker does this:
prepareVMMaker
| maker allPlugins | maker := VMMaker forPlatform: 'Cross'. maker sourceDirectoryName: (self srcDir assureExistence fullName). maker platformRootDirectoryName: (self topDir / 'platforms' )fullName.
And
srcDir "Answer the value of srcDir"
^ srcDir ifNil: [ srcDir := self topDir / 'src' ]This is cool because I can script the cong to use another src. But you
don't do the same for 'platform'. So I cannot do:
CogDebugMacOSConfig new srcDir: 'myFolder'; platformsDir: 'myPlatofrm'; generateSources; generate.
Since the platform directory will be overwritten.
probably a mistake. platforms dir should also be configurable. and it should use it if it set.
Cheers
Mariano
-- Best regards, Igor Stasenko AKA sig.
On Sun, Apr 3, 2011 at 11:45 AM, Mariano Martinez Peck < marianopeck@gmail.com> wrote:
Hi Igor. I was thinking a couple of things:
- So...once I hace download anything from GIT, what I always need to do
is: a) take a pharo core 1.3 b) open the LoadVMMaker.st so that I can see which versions of metacello and cmake I need. c) evaluate that over the pharo image d) move my image to /build so that it finds the /src and /platform by default
So...I wonder what are the reason of not having such PharoCore image already commited in GIT under /image. You can even save it with a workspace opened with the code of LoadVMMaker.st is it just the size of it?
If I want to do it for myself, what is the best strategy? clone to my own fork, add the image there and then just pull the changes?
Igor, and this question ? do you know ?
- #prepareVMMaker does this:
prepareVMMaker
| maker allPlugins | maker := VMMaker forPlatform: 'Cross'. maker sourceDirectoryName: (self srcDir assureExistence fullName). maker platformRootDirectoryName: (self topDir / 'platforms' ) fullName.And
srcDir "Answer the value of srcDir"
^ srcDir ifNil: [ srcDir := self topDir / 'src' ]This is cool because I can script the cong to use another src. But you don't do the same for 'platform'. So I cannot do:
CogDebugMacOSConfig new srcDir: 'myFolder'; platformsDir: 'myPlatofrm'; generateSources; generate.
Since the platform directory will be overwritten.
Cheers
Mariano
On 7 April 2011 00:33, Mariano Martinez Peck marianopeck@gmail.com wrote:
On Sun, Apr 3, 2011 at 11:45 AM, Mariano Martinez Peck marianopeck@gmail.com wrote:
Hi Igor. I was thinking a couple of things:
- So...once I hace download anything from GIT, what I always need to do is:
a) take a pharo core 1.3 b) open the LoadVMMaker.st so that I can see which versions of metacello and cmake I need. c) evaluate that over the pharo image d) move my image to /build so that it finds the /src and /platform by default
So...I wonder what are the reason of not having such PharoCore image already commited in GIT under /image. You can even save it with a workspace opened with the code of LoadVMMaker.st is it just the size of it?
If I want to do it for myself, what is the best strategy? clone to my own fork, add the image there and then just pull the changes?
Igor, and this question ? do you know ?
do not commit image to repository. we want to move away from it, because image is not sources , but just a big binary blob. What you can do is to change the image url, which image should be taken (see codegen-scripts/image.url)
this url used by hudson to download an image which is then used as a base image to load vmmaker.
currently we using an url of last successful pharo-core 1.3 image build. And so, if something goes wrong (like introducing some incompatibility in pharo image which makes VMMaker not loadable or , prevents it from working), we know about it immediately and can fix it.
This is why it called 'continuous integration'. :)
- #prepareVMMaker does this:
prepareVMMaker
| maker allPlugins |
maker := VMMaker forPlatform: 'Cross'. maker sourceDirectoryName: (self srcDir assureExistence fullName). maker platformRootDirectoryName: (self topDir / 'platforms' ) fullName.
And
srcDir "Answer the value of srcDir"
^ srcDir ifNil: [ srcDir := self topDir / 'src' ]
This is cool because I can script the cong to use another src. But you don't do the same for 'platform'. So I cannot do:
CogDebugMacOSConfig new srcDir: 'myFolder'; platformsDir: 'myPlatofrm'; generateSources; generate.
Since the platform directory will be overwritten.
Cheers
Mariano
-- Mariano http://marianopeck.wordpress.com
vm-dev@lists.squeakfoundation.org
-
Igor Stasenko -
Mariano Martinez Peck