<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On 7 November 2013 21:36, Frank Shearar <span dir="ltr"><<a href="mailto:frank.shearar@gmail.com" target="_blank">frank.shearar@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">But Tim's point still stands, because deployment is the problem you<br>
solve after having solved the "build it" problem :)<br>
<span class="HOEnZb"><font color="#888888"><br></font></span></blockquote><div><br></div><div>This is not an issue. You can always run VM on other machine, where it runs to generate<br></div><div>config/source files, and then build VM on machine where VM don't runs yet.<br>
</div><div>Not mentioning cross-compiling approach.<br></div><div>And that technique already employed in pharo building for number of builds, like for<br></div><div>iphone and android platforms. <br></div><div>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.<br>
</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="HOEnZb"><font color="#888888">
frank<br>
</font></span><div class="HOEnZb"><div class="h5"><br>
On 7 November 2013 20:13, Chris Muller <<a href="mailto:asqueaker@gmail.com">asqueaker@gmail.com</a>> wrote:<br>
> Deployment should be regarded a separate problem than building.<br>
><br>
> On Thu, Nov 7, 2013 at 2:00 PM, tim Rowledge <<a href="mailto:tim@rowledge.org">tim@rowledge.org</a>> wrote:<br>
>><br>
>><br>
>> 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.<br>
>> 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.<br>
>><br>
><br>
<br>
</div></div></blockquote></div><br><br clear="all"><br>-- <br>Best regards,<br>Igor Stasenko.
</div></div>