<div dir="ltr">On Wed, Apr 24, 2013 at 7:22 PM, Carl Ritson <span dir="ltr"><<a href="mailto:C.G.Ritson@kent.ac.uk" target="_blank">C.G.Ritson@kent.ac.uk</a>></span> wrote:<br><div class="gmail_extra"><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"><span style="color:rgb(34,34,34)">Going forward, I don't think there are any immediate plans to use the</span><br>
</div>
TVM/KRoC toolchain for teaching at Kent in the next academic year.<br></blockquote><div><br></div><div style>Good to know.</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
its a reasonable option. I suspect that the majority of issues with<br>
platforms (such as Windows and Mac) are largely build difficulties and<br>
requirements for supporting tools (like Perl) rather than issues with<br>
the code base (ignoring 64-bit). This means that as long as you don't<br></blockquote><div><br></div><div style>It's just about build issues and workload at the moment. My (selfish) goal is to get to the point where it is easy (again?) to use the Arduino with occam. Making sure the 32- and 64-bit Linux builds are good (which they are, essentially) should let me host a compile server and meet my needs without handling the changes in tools that are part of the native Windows/Mac builds. </div>
<div style><br></div><div style>I don't anticipate doing anything that creates more work. Tell me if it looks like I am, as that isn't the intent.<br></div><div style><br></div><div style>Cheers,</div><div style>Matt</div>
</div></div></div>