Hi Nicolai,

If you look at appveyor.yml configuration on https://github.com/OpenSmalltalk/opensmalltalk-vm/blob/Cog/.appveyor.yml, you will see that the pharo brand is not yet in the matrix.

It's because builds are based on cygwin, but as I understood, some library used by some plugin required by pharo refuse to compile with cygwin. They appear to work with mingw32.

Cygwin provides headers for legacy directx, some distribution of mingw32 did in the past, but it does not seem the case anymore.

Using the directx headers from Microsoft SDK is a problem. They are not redistributable and can't be found anymore on the net (too old). We cannot seriously base the builds on something so fragile (both technically and legally) in the long term.

Also, the 64 bits VM does only work with clang, and we don't have anything available as a 64bits Microsoft SDK... So pharo has to fix that too.

In the interim, you should look at https://github.com/pharo-project/pharo-vm/blob/master/.appveyor.yml and follow the scripts there.

I hope that Esteban will find time to resolve all these problems and have pharo brand back on opensmalltalk-vm. I guess that any form of help is welcome.

Nicolas

2017-03-11 8:33 GMT+01:00 Nicolai Hess <nicolaihess@gmail.com>:

I still have problems building a vm on windows.

can you give me some hints how to start ?

I cloned the recent pharo-vm project,

in opensmalltalk-vm\build.win32x86\pharo.cog.spur\

run

mvm

But I got a couple of problems (mingw-32 compiler commands not found, I had to adjust the include path for finding directx header, missing variable replacement for git-versions).

So I may miss some important steps.

Is there a repository where I can clone the mingw environment used to build the win32-pharo-vm, the environment used on the build-server ?

Thanks

Nicolai

2017-02-04 1:50 GMT+01:00 Nicolai Hess <nicolaihess@gmail.com>:

2017-02-04 1:44 GMT+01:00 Nicolai Hess <nicolaihess@gmail.com>:

2017-01-23 8:59 GMT+01:00 Esteban Lorenzano <estebanlm@gmail.com>:

On 22 Jan 2017, at 13:19, Nicolai Hess <nicolaihess@gmail.com> wrote:

2017-01-22 10:21 GMT+01:00 Cl��ment Bera <bera.clement@gmail.com>:

Hi,

I believe they're built from��https://github.com/OpenSmalltalk/vm��using travis and appveyor. On the gitbhub readme there are relevant links. All built artifacts are also kept on bintray for history.��

Thank you!

no, they aren���t :)

instead, they are built here:��https://github.com/pharo-project/pharo-vm

(README still not updated)

what did changed ? I am not able to build the vm on windows anymore (something wrong with generating the generator.image, I'll now reset my local pharo-vm build directory and see if it works afterwards).

see attached the stderr log :

'Errors in script loaded from u:\github\pharo-vm\scripts\LoadVMMaker.st'
[31mMessageNotUnderstood: receiver of "default:" is nil
[0mUndefinedObject(Object)>>doesNotUnderstand: #default:
BaseSoundSystem class>>initialize
MCMethodDefinition>>postloadOver:

....

��

Are we still working with branch spur-64, or are we back on master ?

��

Esteban

��

On Sun, Jan 22, 2017 at 9:25 AM, Nicolai Hess <nicolaihess@gmail.com> wrote:

Where are the latest Pharo-spur-vms (32bit) are built?

I don't see them on the build server, only the buildresults at
http://files.pharo.org/vm/pharo-spur32/linux/

The latest builds on the buildserver are from the last year only.

nicolai