[HowTo] Compile CogVM for Windows 7 using MinGW/MSYS

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
22 messages Options
12
Reply | Threaded
Open this post in threaded view
|

Re: Ways to build a VM (was: Re: [Vm-dev] [HowTo] Compile CogVM for Windows 7 using MinGW/MSYS)

stephane ducasse-2

> Just to add, http://github.com/pharo-project/pharo-vm now builds completely
> autonomous under travis: https://travis-ci.org/pharo-project/pharo-vm
>
> that means, this is currently the only build that takes a complete setup into
> account. Even our current jenkins job rely on a properly setup slave, with
> travis you have to specify exactly which packages you want.

Camillo which packages are you talking about? Linux one the slave environment?
I love to read
https://travis-ci.org/pharo-project/pharo-vm

BTW I could not see GStreamer plugin and I know that annick needs it and we will be looking at it with JB

Stef

Reply | Threaded
Open this post in threaded view
|

Re: [HowTo] Compile CogVM for Windows 7 using MinGW/MSYS

Eliot Miranda-2
In reply to this post by Tobias Pape
 



On Thu, Sep 26, 2013 at 1:06 AM, Tobias Pape <[hidden email]> wrote:
 
Hi Stephane

Am 26.09.2013 um 09:05 schrieb stephane ducasse <[hidden email]>:

>
> I do not understand what your objectives are.

This mail just wanted to list
the different ways to build a VM that are currently
used to make everyone aware of what other parties
do.
  The starting point was that, from simply starting off
the squeakvm site, it was a bit tricky to get to
compile a VM for on your own. And hence Marcel provided this
short tutorial.
 Eliot just wants to build the Cog VM in a way he has not
to put too much effort into learning the build environment
(did I understand you the right way, Eliot?).

Exactly.  I want to be able to spend time being productive, not fighting/learning/changing build environments.
 
> Our objective was to offer to the community an automatically build set of vms that do not require
> to be a guru to compile.

And you achieved that! :)

> If people want to use our jenkins farm they simply can (just ask for an account and this is it).

Thank you for that great offer!

> We will continue improving it and use it to control the complexity. We are working on building a benchmark server.
> Now if people prefer to do it manually, they also can, we just do not want.

Understandable. There are always some small thing you just want to change,
and that is the point where one might want to compile manually. For
example, in Marcel's case, he just needed a Windows VM that has no
memory-cap of 512 MB, and he just wanted to compile a Cog VM with
more Memory. Setting up an automated build for this small task
seems overkill to me.
  However, in most other cases, continuous integration is clearly the
way to go!

Best
        -Tobias




--
best,
Eliot
12