<div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote">2014-05-16 4:55 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:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br>
On Thu, May 15, 2014 at 04:40:11PM -0700, gettimothy wrote:<br>
><br>
> Estaban,<br>
><br>
> Thank you.<br>
><br>
> Eliot, David, Tim....<br>
><br>
> How should this be handled in regard to <a href="http://source.squeak.org" target="_blank">source.squeak.org</a>?<br>
><br>
<br>
I do not have a clue.<br>
<br>
What I would say is:<br>
<br>
1) The upstream trunk sources for the platforms sources are in Subversion.<br>
<br>
2) The upstream trunk sources for the Smalltalk VM (aka "VMMaker") are at <a href="http://source.squeak.org" target="_blank">source.squeak.org</a>.<br>
<br>
3) The entire raison d'etre for CMake is to be platform independent. The notion<br>
of generating different versions of CMake for various operating systems, and then<br>
further compounding it with different versions for the various flavors of Squeak<br>
and Pharo (and Cuis and ...) images seems to be missing the point.<br>
<br></blockquote><div><br></div><div>The diferences should be (and I think are) in the specific arrangement of which plugin is integrated or not in the VM.<br><br> <br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
There are good and valid reasons to do things differently in the various downstream<br>
projects, and where possible we all hope that those various projects will contribute<br>
changes back to the trunk. Be that as it may, the upstream sources are in Subversion<br>
for the platform sources, and at <a href="http://source.squeak.org" target="_blank">source.squeak.org</a> for the Smalltalk VM sources.<br>
<br>
There is a reason why Ian Piumarta (who created both the CMake build for Squeak,<br>
as well as the earlier libtool build system from which the Cog build is derived)<br>
organized the CMake scripts the way that he did. Any necessary CMake customizations<br>
related to specific modules, such as a plugin, are defined in small "config.cmake"<br>
and "build.cmake" files that are located in the same directories as their source code<br>
files. If you need to make some change to the build process for a specific module, you<br>
will know where to look. Changes are versioned in the same source control system<br>
as their respective module source files.<br>
<br>
Extending Ian's CMake build process to support Cog may not be a trivial undertaking,<br>
but it certainly can be done. Accomplishing this would make it significantly easier<br>
to support Cog, Spur, and interpreter VM development in the future, and I have to<br>
think that this is largely what Tim had in mind when he challenged us to come up<br>
with a unified build process that would prove satisfactory to the key stakeholders<br>
(Ian, Eliot, Tim).<br>
<br>
Don't get me wrong, there is great stuff in CMakeVMMaker, most importantly that it<br>
consolidates the knowledge of how to apply CMake across a range of OS platforms.<br>
It is also really nice to be able to browse the configurations directly from<br>
your Squeak/Pharo image. But from the point of view of maintaining the actual<br>
build system, the design that Ian came up with, along with the policy of maintaining<br>
CMake configurations close to their associated module source files, seems to me<br>
to be the right way to approach the problem.<br>
<br>
Dave<br>
<br>
> ---- On Thu, 15 May 2014 16:31:30 -0700 Esteban <a href="mailto:Lorenzano%26lt%3Bestebanlm@gmail.com">Lorenzano&lt;estebanlm@gmail.com</a>&gt; wrote ----<br>
><br>
> pharo sources are stored in filetree format along with the other sources in github. Also, if you do not want to use it, there is a mirror here:<br>
><br>
> <a href="http://smalltalkhub.com/#!/~Pharo/PharoVM" target="_blank">http://smalltalkhub.com/#!/~Pharo/PharoVM</a><br>
><br>
> cheers,<br>
> Esteban<br>
><br>
><br>
> On 16 May 2014, at 01:28, gettimothy &<a href="mailto:lt%3Bgettimothy@zoho.com">lt;gettimothy@zoho.com</a>&gt; wrote:<br>
><br>
> Howdy folks.<br>
><br>
> I just now realized that Pharo LoadVMMaker.st script loads CMakeVMMaker-jeanbaptistearnaud.282 whereas I have been using <a href="http://source.squeak.org" target="_blank">source.squeak.org</a>'s CMakeVMMaker-EstebanLorenzano.213 that is auto-loaded in Squeak with the BuildSqueak45Image.st<br>
><br>
> Does anybody know where to find CMakeVMMaker-jeanbaptistearnaud.282? Its not on <a href="http://source.squeak.org" target="_blank">source.squeak.org</a>.<br>
><br>
> I have tried tracking it down, but I cannot find it.<br>
><br>
> thx.<br>
><br>
> tty<br>
><br>
</blockquote></div><br></div></div>