<div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote">On 7 November 2013 22:50, Chris Muller <span dir="ltr"><<a href="mailto:ma.chris.m@gmail.com" target="_blank">ma.chris.m@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><br><div class="gmail_extra"><div class="gmail_quote"><div class="im">On Thu, Nov 7, 2013 at 3:28 PM, 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:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Wait, why are we talking about deploying a Squeak application here?<br>
We're talking about taking a blank machine and being able to build a<br>
Squeak VM on it.<br>
<br>
Tim's saying that you can't drive a C compiler from within the image<br>
on a machine for which no VM has ever been built, because there is no<br>
VM. ("Machine" here means a machine architecture, rather than, say, a<br>
fresh Ubuntu install.) You need a bootstrap. And<br>
configure/cmake/whatever happens to provide a very easy way to<br>
bootstrap to the first VM that can run an image that _can_ drive a C<br>
compiler to build the next gen VM.<br></blockquote><div><br></div></div><div>Hm, ok. That's a pretty rarely-occurring event to be putting a lot thought into a framework for. I'm doubtful such a framework would ever "work the first time" on new platforms.</div>
<div><br></div><div>For building deployable packages on existing platforms, Igors words really resonated with me. I'll butt out now. :)</div><div><div class="h5"><div><br></div></div></div></div></div></div></blockquote>
<div><br>Thanks for supportive words :)<br><br></div><div>For android, which does not supported by cmake Dimiry Golubovsky just managed to do it in a way how it can work: he wrote a configuration (in smalltalk)<br></div><div>
which generates files which compatible with android build infrastructure.<br>I don't know the details, but you can always look at <br>CMakeVMMaker-Android category in CMakeVMMaker package.<br><br></div><div>That means two things:<br>
- CMakeVMMaker despite its name actually does not means 'cmake only'.<br> - the guy with little knowledge of android nuances (like me),<br> can easily pick up this work and modify it in case of need.<br></div>
<div><br>What else i can say?<br></div><div>If people for some reason don't like it, it would be stupid to force it upon them.<br></div><div>The thing is there, open source, and everyone is welcome to use or abuse it.<br>
<br></div><div>So, if you don't like it, you're free to write own..<br>I informed that same work been done (and it works, works well).<br>so rather than starting from scratch, i would twink twice, because i could take<br>
</div><div>what's already done as a starting point and improve or change it (if i don't like something).<br></div><div>So the decision whether to use it or write own from scratch is up to you, people. <br></div><div>
I'm out.<br clear="all"></div></div><br>-- <br>Best regards,<br>Igor Stasenko.
</div></div>