<!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;'>>>No preference. It's up to you. But I'm curious; why are you putting it in an app?<br><div><br></div><div><br></div><div>As I do one gnu-build tree, I am going to do its corresponding CMake tree. </div><div><br></div><div>The CMake configuration files are generated from Squeak. </div><div><br></div><div>It would be like GNU makefiles and autoconf files are generated from Squeak.<br></div><div><br></div><div>Process is like this:</div><div><br></div><div>1. have a directory structure.</div><div>2. Tell CMakeVMMakerSqueak to generate which creates the CMake infrastructure within the specified directory. (Or generateWithSources to create VMMaker sources and CMake files)</div><div>3. from the command line, run the generated buils script 'build.sh' which</div><div> 3.a (on pharo, does some git stuff) </div><div> 3.b invokes cmake</div><div> 3.c invokes make</div><div>4. get your results out of the oscogvm/results directory.</div><div><br></div><div>If everything is stable, the end user just does a svn co of the cmake branch they want and invokes the build.sh script. <---THIS is what Tim R. wants as the deliverable</div><div><br></div><div>I have another process in place for vm developers similar to your buildsqueaktrunk.sh scripts. I sent you those scripts last week. They set you up with either </div><div>a standard VM build environment (complete with source tree set up relative to Squeak) or a CogVM build environment. The idea being to make it easy on newbie vm guys to get up and running.</div><div><br></div><div><br></div><div>Cheers </div><div><br></div><div>tty</div><div><br></div><div><br></div><div><br></div><div><br></div></div></body></html>