FWIW, the major issue seems to be Merlin/Main/Runtime/Microsoft.Scripting/Microsoft.Scripting.Build.csproj not including Runtime\BindingRestrictionsHelpers.cs<br><br><div class="gmail_quote">On Tue, Feb 3, 2009 at 9:19 PM, Michael Letterle <span dir="ltr"><<a href="mailto:michael.letterle@gmail.com">michael.letterle@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Build is currently broken and it appears that MERLIN_ROOT is still required?<br><br><div class="gmail_quote">
<div><div></div><div class="Wj3C7c">On Fri, Jan 30, 2009 at 4:48 PM, Jim Deville <span dir="ltr"><<a href="mailto:jdeville@microsoft.com" target="_blank">jdeville@microsoft.com</a>></span> wrote:<br>
</div></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div><div></div><div class="Wj3C7c">
<div link="blue" vlink="purple" lang="EN-US">
<div>
<p>Sorry for missing the past couple of days, but I have
finally pushed a new revision to Github. As of this change (1ee05cdd),
MERLIN_ROOT is no longer required. You can now download it, get into a VS
Command prompt, and run rake compile from Merlin/Main/Languages/Ruby. Let me
know if you have problems.</p>
<p> </p>
<p>Enjoy!</p>
<p>JD</p>
</div>
</div>
<br></div></div>_______________________________________________<br>
Ironruby-core mailing list<br>
<a href="mailto:Ironruby-core@rubyforge.org" target="_blank">Ironruby-core@rubyforge.org</a><br>
<a href="http://rubyforge.org/mailman/listinfo/ironruby-core" target="_blank">http://rubyforge.org/mailman/listinfo/ironruby-core</a><br>
<br></blockquote></div><font color="#888888"><br><br clear="all"><br>-- <br>Michael Letterle<br>IronRuby MVP<br><a href="http://blog.prokrams.com" target="_blank">http://blog.prokrams.com</a><br><br><br>
</font></blockquote></div><br><br clear="all"><br>-- <br>Michael Letterle<br>IronRuby MVP<br><a href="http://blog.prokrams.com">http://blog.prokrams.com</a><br><br><br>