<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On Aug 30, 2011, at 2:06 PM, David Blaikie wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><div class="im">Why not build a bunch of cross-compilers, and use the right one depending on the</div>
target? </blockquote><div><br></div><div>I honestly don't know what it takes to setup a cross compiler, and I wouldn't be the one doing it - I expect this would fall on Tanya's plate. <br><br></div></div></blockquote><div><br></div>I don't really feel comfortable having the demo machine being a cross compiler for a bunch of targets we don't officially support or test for a release. What is the benefit in that? Having something crash is not a good demo.<br><br></div><div>-Tanya</div><div><br><blockquote type="cite"><div class="gmail_quote"><div>My best guess at an answer to your question would be: it's not worth it. Which is all fuzzy & subjective, of course (& only a guess coming from me, since I don't know the cost & don't have a vested interest in the value it will provide)</div>
<div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">That said, I'm not going to give you a hard time if you cheat :) </blockquote><div><br></div><div>Fair enough - I'll take a look at Bjarke's work & either take it wholesale (perhaps with a warning when the user selects anything other than x86 32/64) or at least make it work for x86 32/64.</div>
<div> </div><div>- David</div></div>
</blockquote></div><br></body></html>