[Pharo-project] OneClick for 2.0 available again
Hannes wrote
Thorsten,
reading what you have written, am I right that we just need a NBCog.ini
file for MSwindows?
We already have an INI file in the Pharo 2.0 one-click. This INI file contains the correct entry about where to find the image file. But it is named "CogVM.ini" instead of "NBCog.ini" since according to the naming convention it has to be named like the VM (which is currently NBCog.exe). So as I wrote just rename CogVM.ini into NBCog.ini and it works. Bye Torsten (without h)
On Mon, Feb 11, 2013 at 12:32 PM, Torsten Bergmann <astares@gmx.de> wrote:
Hannes wrote
Thorsten,
reading what you have written, am I right that we just need a NBCog.ini
file for MSwindows?
We already have an INI file in the Pharo 2.0 one-click. This INI file contains the correct entry about where to find the image file.
But it is named "CogVM.ini" instead of "NBCog.ini" since according to the naming convention it has to be named like the VM (which is currently NBCog.exe).
So as I wrote just rename CogVM.ini into NBCog.ini and it works.
I did this now and the next build should have the right ini Marcus -- Marcus Denker -- denker@acm.org http://www.marcusdenker.de
Yes, Marcus, it is Pharo 2.0 now starts fine in MSWindows when double-clicking on NBCog.exe. What now remains to be updated is the README.txt [1] Replace CogVM.exe --> NBCog.exe And probably remove 'Pharo 1.0' --Hannes [1] Current version or README.txt Pharo 1.0 - Mac: launch Pharo2.0-one-click.app - Linux: launch Pharo2.0-one-click.sh - Windows: launch CogVM.exe This distribution was built February 14, 2013. Please Note: ------------ Pharo does not yet natively run on a 64bits Linux. Just install the ia32/i386 runtime libraries and you should be fine. On Ubuntu and other debian-based systems, these libraries are named 'ia32-libs'. On 2/11/13, Marcus Denker <marcus.denker@inria.fr> wrote:
On Mon, Feb 11, 2013 at 12:32 PM, Torsten Bergmann <astares@gmx.de> wrote:
Hannes wrote
Thorsten,
reading what you have written, am I right that we just need a NBCog.ini
file for MSwindows?
We already have an INI file in the Pharo 2.0 one-click. This INI file contains the correct entry about where to find the image file.
But it is named "CogVM.ini" instead of "NBCog.ini" since according to the naming convention it has to be named like the VM (which is currently NBCog.exe).
So as I wrote just rename CogVM.ini into NBCog.ini and it works.
I did this now and the next build should have the right ini
Marcus
-- Marcus Denker -- denker@acm.org http://www.marcusdenker.de
Thanks, I changed the template and script -> correct .exe mentioned -> 2.0 instead of 1.0 The name of the .exe will change once again to "Pharo.exe" before we release. (We should then remember to update the README) On Feb 14, 2013, at 6:41 PM, "H. Hirzel" <hannes.hirzel@gmail.com> wrote:
Yes, Marcus, it is Pharo 2.0 now starts fine in MSWindows when double-clicking on NBCog.exe.
What now remains to be updated is the README.txt [1] Replace CogVM.exe --> NBCog.exe
And probably remove 'Pharo 1.0'
--Hannes
[1] Current version or README.txt
Pharo 1.0
- Mac: launch Pharo2.0-one-click.app - Linux: launch Pharo2.0-one-click.sh - Windows: launch CogVM.exe
This distribution was built February 14, 2013.
Please Note: ------------
Pharo does not yet natively run on a 64bits Linux. Just install the ia32/i386 runtime libraries and you should be fine. On Ubuntu and other debian-based systems, these libraries are named 'ia32-libs'.
On 2/11/13, Marcus Denker <marcus.denker@inria.fr> wrote:
On Mon, Feb 11, 2013 at 12:32 PM, Torsten Bergmann <astares@gmx.de> wrote:
Hannes wrote
Thorsten,
reading what you have written, am I right that we just need a NBCog.ini
file for MSwindows?
We already have an INI file in the Pharo 2.0 one-click. This INI file contains the correct entry about where to find the image file.
But it is named "CogVM.ini" instead of "NBCog.ini" since according to the naming convention it has to be named like the VM (which is currently NBCog.exe).
So as I wrote just rename CogVM.ini into NBCog.ini and it works.
I did this now and the next build should have the right ini
Marcus
-- Marcus Denker -- denker@acm.org http://www.marcusdenker.de
participants (3)
-
H. Hirzel -
Marcus Denker -
Torsten Bergmann