We don't currently host binaries, in part because it hasn't been set up, and in part because IR is such a fast moving target right now. After RailsConf we can figure out what and where to host some stuff.
Jim Deville ________________________________________ From: [EMAIL PROTECTED] [EMAIL PROTECTED] On Behalf Of Ben Hall [EMAIL PROTECTED] Sent: Sunday, May 25, 2008 1:09 PM To: ironruby-core@rubyforge.org Subject: [Ironruby-core] IronRuby Binaries and Known DLR build Hello, Scenario. I want to host the DLR within my application, as such I reference MS.Scripting and MS.Scripting.Core. I can then happily reference IP2 because it was compiled against the same version. However, the same can't be said for IronRuby. Because there aren't any binaries available to download (Unless I am mistaken, I read they were going to be added to the repos but I couldn't them) and because you are building from the DLR source instead of known releases it looks like i'm going to need two copies of the DLR assemblies within my application. An example of where this is a problem, TokenizerService is within the DLR for IronRuby but not for IronPython. At some point, I take it the DLR will merge into a single release and known assembly for other language providers and hosts to use instead of multiple different versions? Thanks Ben Blog.BenHall.me.uk _______________________________________________ Ironruby-core mailing list Ironruby-core@rubyforge.org http://rubyforge.org/mailman/listinfo/ironruby-core _______________________________________________ Ironruby-core mailing list Ironruby-core@rubyforge.org http://rubyforge.org/mailman/listinfo/ironruby-core
