Re: [Pharo-dev] PharoSpur32Vm

2017-12-30 Thread Stephane Ducasse
Thanks for asking because I hope that this is the case. Stef On Sat, Dec 30, 2017 at 2:59 AM, Nicolai Hess wrote: > > > 2017-07-23 23:18 GMT+02:00 Nicolai Hess : >> >> >> >> 2017-07-23 22:38 GMT+02:00 Nicolas Cellier >> : >>> >>> >>> >>> 2017-07-23 19:56 GMT+02:00 Nicolai Hess : >

Re: [Pharo-dev] PharoSpur32Vm

2017-12-29 Thread Nicolai Hess
2017-07-23 23:18 GMT+02:00 Nicolai Hess : > > > 2017-07-23 22:38 GMT+02:00 Nicolas Cellier gmail.com>: > >> >> >> 2017-07-23 19:56 GMT+02:00 Nicolai Hess : >> >>> >>> >>> 2017-07-23 19:42 GMT+02:00 Hernán Morales Durand < >>> hernan.mora...@gmail.com>: >>> 2017-07-22 10:03 GMT-03:00 Nicolai

Re: [Pharo-dev] PharoSpur32Vm

2017-07-23 Thread Nicolai Hess
2017-07-23 22:38 GMT+02:00 Nicolas Cellier < nicolas.cellier.aka.n...@gmail.com>: > > > 2017-07-23 19:56 GMT+02:00 Nicolai Hess : > >> >> >> 2017-07-23 19:42 GMT+02:00 Hernán Morales Durand < >> hernan.mora...@gmail.com>: >> >>> 2017-07-22 10:03 GMT-03:00 Nicolai Hess : >>> > >>> > Hm, I tried to

Re: [Pharo-dev] PharoSpur32Vm

2017-07-23 Thread Nicolas Cellier
2017-07-23 19:56 GMT+02:00 Nicolai Hess : > > > 2017-07-23 19:42 GMT+02:00 Hernán Morales Durand >: > >> 2017-07-22 10:03 GMT-03:00 Nicolai Hess : >> > >> > Hm, I tried to create the build environment used for the >> > windows vm build from opensmalltalk. >> > >> > I setup a cygwin environment wi

Re: [Pharo-dev] PharoSpur32Vm

2017-07-23 Thread Nicolai Hess
2017-07-23 19:42 GMT+02:00 Hernán Morales Durand : > 2017-07-22 10:03 GMT-03:00 Nicolai Hess : > > > > Hm, I tried to create the build environment used for the > > windows vm build from opensmalltalk. > > > > I setup a cygwin environment with the same install commands as from > > https://github.co

Re: [Pharo-dev] PharoSpur32Vm

2017-07-23 Thread Nicolai Hess
2017-07-22 20:26 GMT+02:00 Eliot Miranda : > Hi Nicolai, > > > On Jul 22, 2017, at 6:03 AM, Nicolai Hess wrote: > > Hm, I tried to create the build environment used for the > windows vm build from opensmalltalk. > > I setup a cygwin environment with the same install commands as from > https://git

Re: [Pharo-dev] PharoSpur32Vm

2017-07-23 Thread Hernán Morales Durand
2017-07-22 10:03 GMT-03:00 Nicolai Hess : > > Hm, I tried to create the build environment used for the > windows vm build from opensmalltalk. > > I setup a cygwin environment with the same install commands as from > https://github.com/OpenSmalltalk/opensmalltalk-vm/blob/Cog/.appveyor.yml > > My pro

Re: [Pharo-dev] PharoSpur32Vm

2017-07-22 Thread Stephane Ducasse
+ 1 I'm curious to know the libraries that are making more trouble. (I'm thinking about FreeType) because we should throw away. Stef On Fri, Mar 17, 2017 at 12:54 AM, Ben Coman wrote: > Great to hear this news. > Thanks for your efforts Nicolas. > cheers -ben > > On Fri, Mar 17, 2017 at 4:51 AM,

Re: [Pharo-dev] PharoSpur32Vm

2017-07-22 Thread Eliot Miranda
Hi Nicolai, > On Jul 22, 2017, at 6:03 AM, Nicolai Hess wrote: > > Hm, I tried to create the build environment used for the > windows vm build from opensmalltalk. > > I setup a cygwin environment with the same install commands as from > https://github.com/OpenSmalltalk/opensmalltalk-vm/blob/

Re: [Pharo-dev] PharoSpur32Vm

2017-07-22 Thread Nicolai Hess
Hm, I tried to create the build environment used for the windows vm build from opensmalltalk. I setup a cygwin environment with the same install commands as from https://github.com/OpenSmalltalk/opensmalltalk-vm/blob/Cog/.appveyor.yml My problems, first it is missing make and wget, I can add make

Re: [Pharo-dev] PharoSpur32Vm

2017-03-17 Thread Nicolai Hess
2017-03-17 23:41 GMT+01:00 Nicolas Cellier < nicolas.cellier.aka.n...@gmail.com>: > > > 2017-03-17 23:40 GMT+01:00 Nicolas Cellier gmail.com>: > >> >> >> 2017-03-17 23:32 GMT+01:00 Nicolai Hess : >> >>> >>> >>> 2017-03-16 21:51 GMT+01:00 Nicolas Cellier < >>> nicolas.cellier.aka.n...@gmail.com>:

Re: [Pharo-dev] PharoSpur32Vm

2017-03-17 Thread Nicolas Cellier
2017-03-17 23:40 GMT+01:00 Nicolas Cellier < nicolas.cellier.aka.n...@gmail.com>: > > > 2017-03-17 23:32 GMT+01:00 Nicolai Hess : > >> >> >> 2017-03-16 21:51 GMT+01:00 Nicolas Cellier > l.com>: >> >>> >>> >>> 2017-03-15 18:14 GMT+01:00 Nicolas Cellier < >>> nicolas.cellier.aka.n...@gmail.com>: >>>

Re: [Pharo-dev] PharoSpur32Vm

2017-03-17 Thread Nicolas Cellier
2017-03-17 23:32 GMT+01:00 Nicolai Hess : > > > 2017-03-16 21:51 GMT+01:00 Nicolas Cellier gmail.com>: > >> >> >> 2017-03-15 18:14 GMT+01:00 Nicolas Cellier > l.com>: >> >>> >>> >>> 2017-03-15 15:03 GMT+01:00 Esteban Lorenzano : >>> sorry for coming late to this thread… hard week :) why

Re: [Pharo-dev] PharoSpur32Vm

2017-03-17 Thread Nicolai Hess
2017-03-16 21:51 GMT+01:00 Nicolas Cellier < nicolas.cellier.aka.n...@gmail.com>: > > > 2017-03-15 18:14 GMT+01:00 Nicolas Cellier gmail.com>: > >> >> >> 2017-03-15 15:03 GMT+01:00 Esteban Lorenzano : >> >>> sorry for coming late to this thread… hard week :) >>> why we are trying to compile with

Re: [Pharo-dev] PharoSpur32Vm

2017-03-17 Thread p...@highoctane.be
Definitely interested in this! On Thu, Mar 16, 2017 at 9:51 PM, Nicolas Cellier < nicolas.cellier.aka.n...@gmail.com> wrote: > > > 2017-03-15 18:14 GMT+01:00 Nicolas Cellier gmail.com>: > >> >> >> 2017-03-15 15:03 GMT+01:00 Esteban Lorenzano : >> >>> sorry for coming late to this thread… hard we

Re: [Pharo-dev] PharoSpur32Vm

2017-03-16 Thread Ben Coman
Great to hear this news. Thanks for your efforts Nicolas. cheers -ben On Fri, Mar 17, 2017 at 4:51 AM, Nicolas Cellier < nicolas.cellier.aka.n...@gmail.com> wrote: > > > 2017-03-15 18:14 GMT+01:00 Nicolas Cellier gmail.com>: > >> >> >> 2017-03-15 15:03 GMT+01:00 Esteban Lorenzano : >> >>> sorry

Re: [Pharo-dev] PharoSpur32Vm

2017-03-16 Thread Nicolas Cellier
2017-03-15 18:14 GMT+01:00 Nicolas Cellier < nicolas.cellier.aka.n...@gmail.com>: > > > 2017-03-15 15:03 GMT+01:00 Esteban Lorenzano : > >> sorry for coming late to this thread… hard week :) >> why we are trying to compile with cygwin? >> is there a problem with the mingw distro? >> >> I didn’t ha

Re: [Pharo-dev] PharoSpur32Vm

2017-03-15 Thread Nicolas Cellier
2017-03-15 15:03 GMT+01:00 Esteban Lorenzano : > sorry for coming late to this thread… hard week :) > why we are trying to compile with cygwin? > is there a problem with the mingw distro? > > I didn’t have the time to update the README, sadly. But well… following > appveyor configuration should gi

Re: [Pharo-dev] PharoSpur32Vm

2017-03-15 Thread Esteban Lorenzano
sorry for coming late to this thread… hard week :) why we are trying to compile with cygwin? is there a problem with the mingw distro? I didn’t have the time to update the README, sadly. But well… following appveyor configuration should give you all you need to reproduce the build (that’s what

Re: [Pharo-dev] PharoSpur32Vm

2017-03-15 Thread Nicolai Hess
2017-03-15 9:22 GMT+01:00 philippe.b...@highoctane.be < philippe.b...@gmail.com>: > I made my own build here. > Not up to date with latest stuff but should work for the build process. > > https://ci.appveyor.com/project/philippeback/pharo-vm > > It uses my forked repo and provided you set your own

Re: [Pharo-dev] PharoSpur32Vm

2017-03-15 Thread philippe.b...@highoctane.be
I made my own build here. Not up to date with latest stuff but should work for the build process. https://ci.appveyor.com/project/philippeback/pharo-vm It uses my forked repo and provided you set your own bintray env vars for API keys will publish there. Check all of the output of env vars and w

Re: [Pharo-dev] PharoSpur32Vm

2017-03-15 Thread Nicolai Hess
2017-03-14 22:22 GMT+01:00 Nicolas Cellier < nicolas.cellier.aka.n...@gmail.com>: > > > 2017-03-14 9:30 GMT+01:00 Nicolas Cellier gmail.com>: > >> >> >> 2017-03-14 8:58 GMT+01:00 Nicolai Hess : >> >>> >>> >>> 2017-03-11 10:01 GMT+01:00 Nicolas Cellier < >>> nicolas.cellier.aka.n...@gmail.com>: >>

Re: [Pharo-dev] PharoSpur32Vm

2017-03-14 Thread Nicolas Cellier
2017-03-14 9:30 GMT+01:00 Nicolas Cellier < nicolas.cellier.aka.n...@gmail.com>: > > > 2017-03-14 8:58 GMT+01:00 Nicolai Hess : > >> >> >> 2017-03-11 10:01 GMT+01:00 Nicolas Cellier > l.com>: >> >>> Hi Nicolai, >>> >>> If you look at appveyor.yml configuration on >>> https://github.com/OpenSmallta

Re: [Pharo-dev] PharoSpur32Vm

2017-03-14 Thread Nicolas Cellier
2017-03-14 8:58 GMT+01:00 Nicolai Hess : > > > 2017-03-11 10:01 GMT+01:00 Nicolas Cellier gmail.com>: > >> 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

Re: [Pharo-dev] PharoSpur32Vm

2017-03-14 Thread Nicolai Hess
2017-03-11 10:01 GMT+01:00 Nicolas Cellier < nicolas.cellier.aka.n...@gmail.com>: > 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 becau

Re: [Pharo-dev] PharoSpur32Vm

2017-03-11 Thread Nicolas Cellier
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

Re: [Pharo-dev] PharoSpur32Vm

2017-03-10 Thread Nicolai Hess
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 find

Re: [Pharo-dev] PharoSpur32Vm

2017-02-03 Thread Nicolai Hess
2017-02-04 1:44 GMT+01:00 Nicolai Hess : > > > 2017-01-23 8:59 GMT+01:00 Esteban Lorenzano : > >> >> On 22 Jan 2017, at 13:19, Nicolai Hess wrote: >> >> >> >> 2017-01-22 10:21 GMT+01:00 Clément Bera : >> >>> Hi, >>> >>> I believe they're built from* https://github.com/OpenSmalltalk/vm >>>

Re: [Pharo-dev] PharoSpur32Vm

2017-02-03 Thread Nicolai Hess
2017-01-23 8:59 GMT+01:00 Esteban Lorenzano : > > On 22 Jan 2017, at 13:19, Nicolai Hess wrote: > > > > 2017-01-22 10:21 GMT+01:00 Clément Bera : > >> Hi, >> >> I believe they're built from* https://github.com/OpenSmalltalk/vm >> * using travis and appveyor. O

Re: [Pharo-dev] PharoSpur32Vm

2017-01-23 Thread Esteban Lorenzano
> On 22 Jan 2017, at 13:19, Nicolai Hess wrote: > > > > 2017-01-22 10:21 GMT+01:00 Clément Bera >: > Hi, > > I believe they're built from https://github.com/OpenSmalltalk/vm > using travis and appveyor. On the > gitbhub r

Re: [Pharo-dev] PharoSpur32Vm

2017-01-22 Thread Nicolai Hess
2017-01-22 10:21 GMT+01:00 Clément Bera : > 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. >

Re: [Pharo-dev] PharoSpur32Vm

2017-01-22 Thread Clément Bera
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. On Sun, Jan 22, 2017 at 9:25 AM, Nicolai Hess wrote:

[Pharo-dev] PharoSpur32Vm

2017-01-22 Thread Nicolai Hess
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