The IronPython ones should be working, and nothing I did should change
IronRuby's installer builds. However, the old build script may
reference IronPython installers that no longer exist.
- Jeff
On Tue, Jan 3, 2012 at 8:14 PM, Tomas Matousek
wrote:
> Yes, the installer is broken. Jeff is working
Yes, the installer is broken. Jeff is working on some better installer building
scripts. I'm not sure what the status is atm.
Tomas
From: ironruby-core-boun...@rubyforge.org
[mailto:ironruby-core-boun...@rubyforge.org] On Behalf Of Orion Edwards
Sent: Tuesday, January 03, 2012 8:07 PM
To: ironr
I changed Silverlight 3 configuration to build against Mango reference
assemblies a couple of days ago. I'll rename Silverlight3 configuration to WP75
soon :)
Haven't tested if it works (at runtime) but it at least builds :)
IronRuby now also builds against Silverlight 5 and MonoAndroid. Nothing
I'd recommend to start with some simpler features than this one. This seems to
be quite non-trivial to implement efficiently and correctly.
Note that getting the current stack trace is very expensive, so you'd probably
want to encode the path into Ruby call-sites (RubyCallAction) or something lik
I did a git pull today of IronLanguages\main, and noticed a giant stack of
changes on December 30, 31 and Jan 1 - which look like they're related to
Win8 and Mango, amongst other things.
I'm trying to build the IronRuby installer - the process also builds the
IronPython installer along with it.
I thought I'd be a good samaritan and implement require_relative in
IronRuby, but I'm having real trouble figuring out what the current file's
path actually is.
The closest I've got is something like this:
* Pull apart the the caller/backtrace to get the file name
* File.expand_path(file, File
