On Sun, Oct 20, 2013 at 04:15:15PM -0700, Ian Piumarta wrote:
> Dave,
> 
> On Oct 20, 2013, at 15:33 , David T. Lewis wrote:
> 
> > Well, I guess the last official Unix build that Ian Piumarta did was about
> > a year ago, so a refresh might be in order some time soon.
> 
> Doesn't time fly?  I'll do the necessary as promptly as I can when your latest src is ready.
> 

The SVN trunk/src is up to date as of today, although this is in the
new flat directory layout with internal and external plugins in the
same directory. So to compile from trunk/src we need to either update
the cmake build to use that structure, or regenerate once more in the
traditional internal/external directory structure (which is easy to do).

> > He's kind of a pushover for that sort of influence ;-)
> 
> Beer works even better, whenever proximity permits. :)
> 

If proximity should ever permit, I'll definitely supply the beer :)


> > wouldn't it me nice if we had a real VM build slave
> > running on squeakvm.org that would do continuous builds from the latest
> > sources in the Subversion repository?
> 
> We could very easily do that for 32-bit Linux right there on squeakvm.org.  The Mac and Windows machines that I use to build binaries here are both up 24/7 and could be made to rebuild a binary archive whenever the trunk changes.  Having your generated src in the trunk would make that very easy (and src can finally be removed from the Unix tree).
> 
> For more exotic Unix builds (Solaris, *BSD) I run the OS in VirtualBox and have a script to update source, build everything and upload binaries, in parallel.  Adding Mac OS and Win32 to that script should not be difficult.  A cron job could run it whenever the most recent commit reaches (say) one hour of age.
> 
> Unless there a particular well-known cross-platform unattended build framework, having some indispensable feature, that we absolutely should use for all of this?
> 

The Jenkins framework that Frank has been using on build.squeak.org
seems to do a very nice job of tracking these things. I think we
could use it as the supervisory trigger to initiate updates on
squeakvm.org, and also to display the result of those updates. The
actual build procedures, including VirtualBox builds, can and should
be your own build procedures on squeakvm.org.

So -- if the existing builds could be set to run under cron, then it
should be a small additional step to wire them into Jenkins to trigger
the builds and display the results.

Dave