<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"><html><head><meta content="text/html;charset=UTF-8" http-equiv="Content-Type"></head><body ><div style='font-size:10pt;font-family:Verdana,Arial,Helvetica,sans-serif;'>Hi Tim.<br><blockquote style="border-top-color: rgb(204, 204, 204); border-left-color: rgb(204, 204, 204); border-right-color: rgb(204, 204, 204); border-bottom-color: rgb(204, 204, 204); border-top-width: 1px; border-left-width: 1px; border-right-width: 1px; border-bottom-width: 1px; border-top-style: solid; border-left-style: solid; border-right-style: solid; border-bottom-style: solid; padding-top: 7px; padding-right: 7px; padding-bottom: 7px; padding-left: 7px; background-color: rgb(245, 245, 245);"><div> > Here is what I have in place so far: <br>> <br>> 1. Get the latest Cog tree from svn co <a href="http://www.squeakvm.org/svn/squeak/branches/Cog" target="_blank">http://www.squeakvm.org/svn/squeak/branches/Cog</a> <br>> 2. cd Cog/image/ and run script to build an image which: <br>> 2.a builds image with tools per current process. <br>> 2.b (additionally loads FT2Plus Toxic bypass) <br>> 2.c additionally load the CMakeVMMaker package from source.squeak.org (now loading from SmalltalkHub) <br>> 2.d Recursively copies the parent Cog source code to image_directory/oscogvm/* <br>> 3.e Cleans the source tree to just source by finding and deleting all GNU-Build artefacts (Makefiles, autotool stuff) <br>> 3. User launches new image with the pristine source tree underneath it. <br>> 4. Run process SqueakVMBuilder buildXYZ (same as pharo process, but squeak names) to generate the source code and CMake stuff in the clean source tree. <br>> 5. Run generated 'build.sh' script which invokes CMake and make. <br> <br> <br>It’s those last two parts that imply something is going a bit off-track here. <br> <br>Now don’t forget I’m a fan of VMMaker, after all I invented it 14 years ago (actually so far as I can tell pretty much *exactly* ) but the convenience of being able to do an svn co, hit the OS-appropriate buttons and autoconfigure/build is considerable. Yes, I suppose one could have multiple svn branches for the (many, many) different versions of *nix but making use of the already existing CMake capability strikes me as more sensible. </div></blockquote><br><br><div>Existing functionality is unchanged. </div><div>There is only 1 SVN branch. </div><div>VMaker is unchanged</div><div>My additions are non-intrusive.<br></div><div><br></div><div>Regarding existing CMake capability, I am leveraging what the pharo team has already done. It appears Ian's work is hand coded CMakeLists.txt in trunk/platforms/unix and a configure script that generates the plugin CMake files. </div><div><br></div><div>Regarding your ability to just svn co and run cmake, I agree that will be nice and it can be done. However until the tool is mature we need something that will work with what we have without getting in the way. I believe this approach will accomplish that.</div><div><br></div><div>Hopefully I will have something in place tomorrow that you can test-drive.</div><div><br></div><div>cordially,</div><div><br></div><div><br></div><div>tty.</div><div><br></div><div><br></div></div></body></html>