<div dir="ltr">Hi Timothy,<div class="gmail_extra"><br><br><div class="gmail_quote">On Mon, May 26, 2014 at 9:41 AM, gettimothy <span dir="ltr"><<a href="mailto:gettimothy@zoho.com" target="_blank">gettimothy@zoho.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> <br><u></u><div><div style="font-size:10pt;font-family:Verdana,Arial,Helvetica,sans-serif"><div>Hi Eliot,</div><div><br>
</div><div>I would like to name the CMakeConfigurations so that the build directory they are deposited in is intuitive and is in line with your current thought processes.</div><div><br></div><div>I cannot figure out the heuristics of some of the abbreviations below:</div>
<div><br></div><div><div><br></div><div><blockquote style="border-top-color:rgb(204,204,204);border-left-color:rgb(204,204,204);border-right-color:rgb(204,204,204);border-bottom-color:rgb(204,204,204);border-top-width:1px;border-left-width:1px;border-right-width:1px;border-bottom-width:1px;border-top-style:solid;border-left-style:solid;border-right-style:solid;border-bottom-style:solid;padding-top:7px;padding-right:7px;padding-bottom:7px;padding-left:7px;background-color:rgb(245,245,245)">
<div>+ [ ] abldt<br> + [ ] bldt<br> + [ ] dbldt<br>+ [ ] astbld<br> + [ ] astbldt<br>+ [ ] bldt<br>+ [ ] dbgbld debug build?<br> + [ ] dbgbldt<br>+ [ ] astbld<br> + [ ] astbldt<br>+ [X] bld Cog Unix 32 build<br>
+ [ ] bldt <br>+ [ ] dbgbld <br>+ [ ] dbgbldt <br>+ [ ] abld<br> + [ ] abldt<br>+ [ ] dbld debug build?<br> + [ ] dbldt<br> + [ ] mtbld<br> + [ ] mtbldt</div></blockquote></div><div><br></div>
</div><div><br></div><div><br></div><div>I assume ....</div><div>'bld' is the default 32 bit unix build</div><div>'mtbld' is multi-threaded</div><div>'dbld' and 'dbgbld' are probably debug enabled</div>
<div>the 'a*' and '*t' directories have me stumped.</div></div></div></blockquote><div><br></div><div>a and ast are prefixes for assert. There are three VM configurations. Debug and Assert include assert code, with the Assert VMs being optimized with -O1 (asserts are slow to evaluate and a little optimization can really help). Debug VMs are entirely unoptimized (and hence crawl). The third is production where asserts are eliminated by the preprocessor.</div>
<div><br></div><div>Obviously I should be consistent and withe ruse a or ast, not both (and the same for d/bg). I'm about to revise the whole build directory stricture anyway to make it much more consistent, but I've yet to find the time.</div>
<div><br></div><div>The "t" suffix is for "threaded" and means that these VMs have the threaded heartbeat, with the others using the problematic itimer heartbeat. Alas older linux kernels don't allow the threaded heartbeat, but once we're not interested in supporting older then 2.6.14 (IIRC) then they can be dropped.</div>
<div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div style="font-size:10pt;font-family:Verdana,Arial,Helvetica,sans-serif"><div><br></div><div>If you have a moment, it will help clarity going forward.</div>
<div><br></div><div><br></div><div>thx,<br></div><div><br></div><div>tty</div></div></div><br></blockquote></div><br><br clear="all"><div><br></div>-- <br>best,<div>Eliot</div>
</div></div>