<div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote">2014-05-16 14:58 GMT+02:00 David T. Lewis <span dir="ltr"><<a href="mailto:lewis@mail.msen.com" target="_blank">lewis@mail.msen.com</a>></span>:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div class=""><br>
On Fri, May 16, 2014 at 01:24:37PM +0200, Nicolas Cellier wrote:<br>
><br>
> 2014-05-16 4:55 GMT+02:00 David T. Lewis <<a href="mailto:lewis@mail.msen.com">lewis@mail.msen.com</a>>:<br>
><br>
> ><br>
</div><div class="">> > 3) The entire raison d'etre for CMake is to be platform independent. The<br>
> > notion<br>
> > of generating different versions of CMake for various operating systems,<br>
> > and then<br>
> > further compounding it with different versions for the various flavors of<br>
> > Squeak<br>
> > and Pharo (and Cuis and ...) images seems to be missing the point.<br>
> ><br>
> ><br>
> The diferences should be (and I think are) in the specific arrangement of<br>
> which plugin is integrated or not in the VM.<br>
><br>
<br>
</div>FYI, the <a href="http://plugins.int" target="_blank">plugins.int</a> and plugins.ext files control this. The conventions that<br>
Eliot is using for the Cog build, including the flattened directory structure<br>
for generated code and the plugins configuration files, are now used in Ian's<br>
CMake build also. There is no difference between the two build systems in that<br>
regard.<br>
<br>
Dave<br>
<br>
</blockquote></div><br></div><div class="gmail_extra">But if you want to be able to reproduce always the same artefact, this configuration has to be stored somewhere...<br>The Pharo choice is to deliberately store the configuration in image as much as possible, and generate thos configuration files.<br>
Beside Pharo config is also about setting specific Pharo icons, about adding more plugins not readily available like Cairo and point to specific version of the cairo library installed by upper level script, etc...<br><br>
</div></div>