<!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 bgcolor="#ffffff" text="#000000">
gettimothy wrote:
<blockquote
cite="mid:146a9e90928.-2802336409375319131.-2240327022383006958@zoho.com"
type="cite">
<pre wrap="">Outputting an entire CMake build tree happens in milliseconds with a message to a platform's builder.</pre>
<div
style="font-size: 10pt; font-family: Verdana,Arial,Helvetica,sans-serif;">
<blockquote
style="border: 1px solid rgb(204, 204, 204); padding: 7px; background-color: rgb(245, 245, 245);">
<div>
<div>SqueakLinux64x86w32CompatBuilder<br>
configureA: #Linux64x86w32BitSqueakCogV3SlackwareNoGLConfig
forBuildType: #build;<br>
generate. <br>
</div>
</div>
</blockquote>
<br>
<div>Now admittedly that looks odd-ball because my system is an
oddball system, but all builds have the same structure, so in "normal
land"</div>
<br>
<div><br>
</div>
<div>A moment's reflection will tell you that the enterprising
Seaside Developer can put a front end on this sucker and put in a very
user friendly way for people to download custom builds</div>
<div>If it was a wizard thingy, the steps could be:</div>
<div><br>
</div>
</div>
</blockquote>
I though I was going to be asking for the moon... for something to
parse the VMMaker classes in the system into a desktop GUI selection
tool, there you've already thought of something similar. Not
withstanding any Seaside UI, I think a desktop UI would be more use for
individuals to explore how the build system works - and the
infrastructure would be common between the two UI.<br>
<br>
cheers -ben<br>
</body>
</html>