[Vm-dev] Error compiling Cog.

[Igor Stasenko]

On 30 March 2011 16:51, Mariano Martinez Peck <marianopeck at gmail.com> wrote:
>
>
> On Wed, Mar 30, 2011 at 4:19 PM, Igor Stasenko <siguctua at gmail.com> wrote:
>>
>> On 30 March 2011 16:00, Mariano Martinez Peck <marianopeck at gmail.com>
>> wrote:
>> >
>> >
>> >
>> > On Wed, Mar 30, 2011 at 3:59 PM, Mariano Martinez Peck
>> > <marianopeck at gmail.com> wrote:
>> >>
>> >>
>> >> On Wed, Mar 30, 2011 at 3:56 PM, stephane ducasse
>> >> <stephane.ducasse at gmail.com> wrote:
>> >>>
>> >>> but why (ConfigurationOfCog project version: '1.3') load
>> >>> does not work?
>> >>>
>> >>
>> >> because it has versions of VMMaker that doesnt match with the latest in
>> >> git. So, if today you load the latest from git, and using 1.3, you cannot
>> >> compile
>> >>
>> >
>> > What I mean is that there could have been changes in the "platform"
>> > code, which is in git, and that the VMMaker expect those changes. If you
>> > load the last platform code from git, it has those changes. But if you load
>> > an old version of VMMaker, then it expects "older" platform code.
>> >
>> >
>>
>> Exactly.
>> And LoadVMMaker.st script placed there exactly for eliminating the
>> problems when you unable to determine which VMMaker version works with
>> given sources snapshot.
>
> WOW. That's awesome. I didn't know about that.
>

Heh.. i were talking about that from very starting ;)

> Last thing...instead of havign to load an specific version of CMake by
> hand....why not integrate such package under ConfigurationOfCog ?


Because i not quite handy with Metacello. I using metacello as a
trained monkey. :)
I just took what was already there and modified it a bit to make sure
it loads without errors into pharo images.

> if you don't want  to put it in the default group, no problem, but at lesat you can
> define a new group like 'VMakerWithCmake' so that we can do:
>
>
>
> ((Smalltalk at: #ConfigurationOfCog) project
>     version: '1.5') load: 'VMakerWithCmake'.
>
> and that's all :)


So, if you know how to do that, please do. And i will happily integrate it.

I'd like to note to everyone:

 - an automated build process works, but its not perfect. (but its
much better than we had before ;)

So, a criticism and help or ideas how to improve it is welcome.

>
> Another idea is to put in the #description of each version of
> ConfigurationOfCog, which is the expected version of git to work. I used to
> do this wtih SVN and ConfogurationOfVMMaker.
> this way we can map from the other side ;)
> even more...in the description you can directlty put which sohuld be the git
> command.
>

Well, that will be unnecessary, because multiple git snapshots may
work with same configuration.
(You may fix or change some platform code, which not requires any
changes on VMMaker side).


This means that my scheme keeps correspondence in direction
source => VMMaker

in that way for each source snapshot you know which version of VMMaker
you should use.
But not in reverse order.


> cheers
>
> Mariano
>
>
>>
>> This is a link between git snapshot and sources which stored outside
>> of it (in SqS/VMMaker or elsewhere).
>> And by having this link, we can reproduce an image and then generate
>> source files, so we don't need to put a generated sources under
>> source-control anymore.
>>
>>
>> --
>> Best regards,
>> Igor Stasenko AKA sig.
>
>



-- 
Best regards,
Igor Stasenko AKA sig.