On 7 November 2013 21:36, Frank Shearar <frank.shearar at gmail.com> wrote:

> But Tim's point still stands, because deployment is the problem you
> solve after having solved the "build it" problem :)
>
>
This is not an issue. You can always run VM on other machine, where it runs
to generate
config/source files, and then build VM on machine where VM don't runs yet.
Not mentioning cross-compiling approach.
And that technique already employed in pharo building for number of builds,
like for
iphone and android platforms.
Even building ppa-distro for linux goes same way: its just takes
configuration & sources (and all source files) generated by build server
and built somewhere on other end of the world in linux ppa build farms.


> frank
>
> On 7 November 2013 20:13, Chris Muller <asqueaker at gmail.com> wrote:
> > Deployment should be regarded a separate problem than building.
> >
> > On Thu, Nov 7, 2013 at 2:00 PM, tim Rowledge <tim at rowledge.org> wrote:
> >>
> >>
> >> One important thing to remember is coping with a first build on a new
> machine. Having a squeak app that can drive cc to build a vm would be very
> neat, but if you don't yet have a working vm for a device you could be in
> trouble.
> >> An advantage of the cmake process is that it bypasses that issue.
> Actually running the configure on the target machine means you get
> (hopefully!) accurate results when querying facilities. There is also some
> benefit in a production environment in being able to pass a 'normal' build
> job to someone else without having to find a squeak buildomatic cognizant
> person.
> >>
> >
>
>


-- 
Best regards,
Igor Stasenko.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.squeakfoundation.org/pipermail/squeak-dev/attachments/20131107/1e8957ef/attachment.htm