<!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;'><div>Thanks Eliot.<br></div><div><br></div><div>>>I'm not sure I'm answering your question, but ave you seen processors/IA32/bochs/README.COG? Tis explains how to build the support libraries. </div><div>I know I had seen something on it somewhere, thanks for reminding me.</div><div><br></div><div>>>Specifically what do you expect to be documented?</div><div><br></div><div>An answer to the question "What the heck is this for?" for newbies like me (:</div><div><br></div><div>Let me elaborate a bit.</div><div><br></div><div>Last night, I got Bochs installed and running a couple of images from their site (alas, Plan9 hangs on boot, so no squeak install on Plan9 this week) so I can think about how this might fit together.</div><div>Here are my thoughts, such as they are...</div><div><br></div><div>1. Bochs emulates computer hardware and you can run various operating systems on that hardware emulation. </div><div>2. In the same way Cog targets the x86, ARM and RiscOS platforms, Cog targets the Bochs platform.</div><div>3. To do so, Cog needs some configuration on that platform to run, which is provided in bochs .conf.xyz file </div><div>3.a See the processors/IA32/bochs/README.COG for details of which config file to use). At this point, the ability to boot and use Bochs is assumed.</div><div>4. Boot your bochs image with that .conf.xyz file </div><div>4.b (does the image already have the SVN source tree on it? do we download it with svn?)</div><div>5. Navigate to the correct directory (which one?) and build the VM with the BochsPlugin </div><div>6. scratch chin and mutter "hmmmmm".</div><div>7 "The Cog simulator and the CogIA32CompilerTests use the Bochs plugin." while an image is running on Bochs platform?</div><div><br></div><div><br></div><div>As you can see, my thought process gets muddy at steps 4 through 7 and I would like to clean that up. </div><div>Then, put those thoughts into the class comment (or elsewhere) of the BochsPlugin such that</div><div>answering the question "what the heck is this for?" is shortened a bit (:</div><div><br></div><div><br></div><div><br></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></body></html>