Branded Cog for Win32 for Build slave (Was: [TODO] 1.3)

>provide a "Pharo Cog $VersionNumber" vm.
>
>The good news is that we now have a window build slave, so we will soon have >all 3 major architectures covered

Nice - the windows build slave arrived! Who maintains it?

So I expect the build slave to
 1. get the code from Eliots svn repository
 2. patch the code to "brand" the vm with custom Pharo icon and label
 3. Replace the name of the VM to build in the Makefile
 4. build it for use in OneClick or installer or to provide a zip  

Similar to what I've done so far manually.

OK, so attached is the "patch" for branding the
Cog VM for Win32 back from the Cog2378 that I used for Pharo 1.2.2.

 - PharoCog.def.in (always a copy of Squeak.def.in)
 - PharoCog.ico    (the custom icon for PharoCog)
 - PharoCog.rc     (the resource file including labeling and version)

Copy these three files in the same directory as the "Makefile"

Now set the name in the Makefile:

# The name of the VM to build
VM:=PharoCog

Now you can build.

Best would be to generate the "PharoCog.rc" from a Smalltalk in
the Hudson slave build script, so the version number (which is the
same as the one Eliot gives to Cog) is set dynamically.

   VALUE "FileDescription", "Pharo Cog Virtual Machine Revision 2378\0"
   VALUE "FileVersion", "1.2.2378\0"

So 1.2.2378 means Pharo 1.2 with Cog 2378.

If in doubt ask me. Who is building the slave?

We should do the same also for the standard VM (which is a little
bit different and with a different icon).
We can also let the build slave (beside one click) create the
full setup/installer.

Thx
Torsten
--
NEU: FreePhone - kostenlos mobil telefonieren und surfen!
Jetzt informieren: http://www.gmx.net/de/go/freephone

On May 18, 2011, at 10:44 AM, Torsten Bergmann wrote:

>> provide a "Pharo Cog $VersionNumber" vm.
>>
>> The good news is that we now have a window build slave, so we will soon have >all 3 major architectures covered
>
> Nice - the windows build slave arrived! Who maintains it?
>
The server is maintained by INRIA it services... the build infrastructure by Igor and the rest who has
access (i.e. me, but I stopped using windows *before* win95 was released...)

> So I expect the build slave to
> 1. get the code from Eliots svn repository
> 2. patch the code to "brand" the vm with custom Pharo icon and label
> 3. Replace the name of the VM to build in the Makefile
> 4. build it for use in OneClick or installer or to provide a zip  
>

yes.

        Marcus



--
Marcus Denker  -- http://www.marcusdenker.de
INRIA Lille -- Nord Europe. Team RMoD.

--
Mariano
http://marianopeck.wordpress.com

On 18 May 2011 14:14, Marcus Denker <[hidden email]> wrote:
Yes, it would be me who will set up Hudson slave on windows.

The delay with Windows, was that we had they already installed, but it
was french version, and then we asked to install english version
instead,
because i'm not too good in french and moreover, since we want a
community to participate in future, apparently we don't like to
introduce an unnecessary
language barrier to those who not knowing french :)



--
Best regards,
Igor Stasenko AKA sig.

why not from the github one?
Is there something wrong with it?

On 18 May 2011 20:11, Stéphane Ducasse <[hidden email]> wrote:
Of course not.
Actually opposite. We can create a branch of blessed repository where
we will put a modifications
for branding Cog , like custom icons , resource files and other settings.
And it will be much easier to do than manually patching files every
time after fetching from svn.


--
Best regards,
Igor Stasenko AKA sig.