[Pharo-project] Problem with Pharo 1.3 in Windows

Torsten Bergmann astares at gmx.de
Thu May 19 10:26:27 CEST 2011


Henrik Sperre Johansen
>Here's how we do it for our application:

PLEASE NO. Why use Reshacker? Its just a hacker tool
to manipulate the resource section in an EXISTING EXE file.

I remember that this was the recommended way of a well 
known commercial smalltalk vendor to customize the VM icon. But this
is just a workaround since the VM source code was not available there.

Maybe it is OK for Henrik too since he dont want to look into VM building.

But for Pharo WE HAVE the VM sources and now also a win build slave 
for hudson therefore should just use a custom *.rc for the build.

I once suggested this to Andreas, he integrated it and his 
standard Win32 VM includes a versioninfo in the Squeak.rc file. 
I also suggested it to Eliot but he didnt included it (yet).

I dont really care if he integrates into Cog since for a customized 
Pharo VM we use a custom "PharoCog.rc" file anyway 
(instead of Squeak.rc) during the build step.

Read my post here, including the correct files for Cog:
 http://lists.gforge.inria.fr/pipermail/pharo-project/2011-May/049093.html

If you copy them into the dir where Makefile lives you just
have to change the name of the VM to build in the Makefile

See also "Customization" at http://squeakvm.org/win32/compiling.html

So if you switch to

 VM = MyKillerApp 

in the Makefile the build includes

  MyKillerApp.def.in
  MyKillerApp.rc  

instead of Squeak.def.in/Squeak.rc

And in MyKillerApp.rc you can set the version info and point
to a custom MyKillerApp.ico.

And in the end you get a branded MyKillerApp.exe
Simple!

Bye
T.
-- 
Empfehlen Sie GMX DSL Ihren Freunden und Bekannten und wir
belohnen Sie mit bis zu 50,- Euro! https://freundschaftswerbung.gmx.de



More information about the Pharo-project mailing list