[Vm-dev] Error compiling Cog.

[Igor Stasenko]

On 30 March 2011 20:11, Mariano Martinez Peck <marianopeck at gmail.com> wrote:
>
>> >
>> >
>> > ((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.
>>
>
>
> Find the ConfigurationOfCog attached. As an example, I've created the
> version 1.6 and baseline 1.4
>
> Notice that in the baseline I added:
>
> spec repository: 'http://www.squeaksource.com/VMMaker';
>               package: 'CMakeVMMaker' with: [spec requires: #('Cog') ] .
>
>
> and in the version I added:
>
> package: 'CMakeVMMaker' with: 'CMakeVMMaker-IgorStasenko.51'.
>
> So...for new versions, the only thing you will need to do is to set that
> version, just the same you do with the rest.
>
> So..this:
>
> Gofer new
>     squeaksource: 'MetacelloRepository';
>     package: 'ConfigurationOfCog';
>     load.
>
> ((Smalltalk at: #ConfigurationOfCog) project
>     version: '1.5') load.
>
>
> ((MCHttpRepository     location: 'http://www.squeaksource.com/VMMaker' user:
> '' password: '')
> versionFromFileNamed: 'CMakeVMMaker-IgorStasenko.51.mcz') load.
>
>
> now is reduced to:
>
>
> Gofer new
>     squeaksource: 'MetacelloRepository';
>     package: 'ConfigurationOfCog';
>     load.
>
> ((Smalltalk at: #ConfigurationOfCog) project
>     version: '1.5') load.
>
>
Nice. Thanks.

>
>>
>> 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.
>
> The same the other way arround ;)
> The same VMMaker version can work with different git snapshos
>
>>
>> (You may fix or change some platform code, which not requires any
>> changes on VMMaker side).
>>
>
> or vice-versa
>
>>
>> This means that my scheme keeps correspondence in direction
>> source => VMMaker
>>
>
> but why not adding  VMMaker -> source
> also ?
>
how you suppose to do that?
In configs then you need to put an array of git commits which working
with your config? Or what?

And then i will be forced to commit sources to git, while
configuration of it to load is not there yet (because only after
commit
i can get an url to these sources and then put it into config and
finally upload new config to squeaksource).

It looks a bit complicated, isnt? And extra manual work..

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



-- 
Best regards,
Igor Stasenko AKA sig.