<!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;'>Just an FYI to keep you updated.<br><br>1. Current work is on concurrently developing a Linux32x86 (w 32 bit compat libs) squeak.cog.spur/build Configuration AND the Help documentation to create the thing (Writing the Help is the time consuming stuff, but critical)<br>When that is done, I will test my Help writing, by porting the app to a pure 64x64 machine and duplicating that process for a pure linux 64x64 configuration.<br>That will ensure the Help pages needed by others to create their own Configurations for different platforms are reasonably solid.<br><br><br><br>2.a some of the Plugins processing currently has some hard-coded stuff from pharo that must be removed. for example<br>configDotCameraPlugin<br> ^'PLUGIN_REQUIRE_INCLUDE(V4L2 linux/videodev2.h /usr/include)' <br><br>needs rethinking<br><br>while:<br><br>configDotClipboardExtendedPlugin<br> ^'<br>IF (NOT X11_FOUND)<br> PLUGIN_DISABLE()<br>ENDIF ()'<br><br>is reasonable<br><br>2.b. Look critically at the Plugin processing...I am thinking wrappers to replace what I currently have.<br><br><br>3. Step back and look at the CMake generation process then refactor such that its methods clearly communicate the methodical process of creating a CMake build tree.<br>Currently it is conceptually cluttered incorporating code from Ian's CMake work and steps from the pharo CMakeVMMaker work.<br><br>The construction Idiom I am using is directly from Seaside's html component idiom. <br>Constructing a very complicated web-page using Seaside components is conceptually easy ; Constructing complicated CMake files should be too.<br><br><br>4. Decoupling the CMakeVMMakerSqueak from the existing pharo CMakeVMMaker<br><br>5. Enlist crowd-sourcing to complete the Configurations for each [Platform][Language.VM.MemoryModel][BuildType] [4 platforms]x [2 languages x 3 vms x 2 memory models] x [6 build types]=eleventy billion configurations (or maybe 288 )<br><br>6. (optional) "Auto" CMake templates creation and by CMake version as such....<br>parse the output of 'cmake --help-commands and create CMake Templates (classes) from that data.<br>CMake Templates are conceptually the same as Seaside HTML Components . <br>Composing them makes constructing CMakeLists.txt files easy process.<br><br>7. (optional) Seaside application that allows a user to select from or create on the fly a CMake build tree for their platform.<br><br>8. steal all the underpants.<br><br>9.???<br><br>10. profit!<br><br>cheers.<br><br>tty<br><br><br><br><br><br><br><br><br></div></body></html>