<div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote">On Fri, Jul 11, 2014 at 6:16 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:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"> <br><u></u><div><div style="font-size:10pt;font-family:Verdana,Arial,Helvetica,sans-serif">
<div>Hi all.<br></div><div><br></div><div>I am considering storing the #defines needed for configuring a build in the CMakeVMMaker(Squeak) Configuration and generating the script from an ordered collection of them.</div><div>
My latest commit just has the stuff Ian had in his config.cmake plus some extra headers/libs that I scavenged from the GNU build tree.</div><div><br></div><div>Can I consider the <br><blockquote style="border:1px solid rgb(204,204,204);padding:7px;background-color:rgb(245,245,245)">
<div>platforms/unix/config/<a href="http://config.in" target="_blank">config.in</a></div></blockquote> file as the definitive list for what a build might need?</div></div></div></blockquote><div><br></div><div>You mean platforms/unix/config/<a href="http://config.h.in">config.h.in</a> right? If so, then on unix, yes.</div>
<div><br></div></div>-- <br>best,<div>Eliot</div>
</div></div>