<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 12pt;
font-family:Calibri
}
--></style></head>
<body class='hmmessage'><div dir='ltr'>Does anyone have a full story around cm3 -boot?<div><br></div><div><br></div><div>I "fixed" Builder.GenObjectList to produce valid make code,</div><div>which is what I thought it was doing, but now I realize, I guess,</div><div>it was generating quake code.</div><div>The chunking was probably to workaround historical fixed size buffers</div><div>and buffer overflows in quake, <span style="font-size: 12pt;">that we have since fixed.</span></div><div><span style="font-size: 12pt;"><br></span></div><div><br></div><div>Anyway, I could fix this all up in one of a few ways:</div><div> - do nothing; do everything in python</div><div> - generate cmake stuff</div><div> - generate autotools/libtool stuff</div><div> - generate quake stuff</div><div> - other</div><div><br></div><div><br></div><div>Python nearly suffices, but the current direction bugs</div><div>me in multiple ways:</div><div> - I duplicate things like cflags/compiler/asssembler between config and python</div><div> - The python hardcodes knowing what is a program vs. a library</div><div><br></div><div><br></div><div>In going to try to complete the cm3 code here..like putting in linking,</div><div>it strikes me that one problem is when to do probing for libraries,</div><div>the logic around shared vs. static, prefering shared by default,</div><div>prefering static if build_standalone, and using whatever is found if only one.</div><div><br></div><div><br></div><div>Running that logic in cm3 -boot is slightly challenging.</div><div>We'd either assume and hardcode file presence, possibly just assuming static,</div><div><span style="font-size: 12pt;">or defer the logic to the next phase.</span></div><div><br></div><div><br></div><div> - Jay<br><br><br></div> </div></body>
</html>