sure you can change the GEM_PATH What I tend to do is just build from source and copy the binaries over the ironruby install. Then I have to edit the .config files so it will work with unsigned assemblies.
There was a push yesterday and now there is a huge win. An RSpec batch now takes less than half the time it did before. At this point ironruby is very usable and I would take an app in production with it. --- Met vriendelijke groeten - Best regards - Salutations Ivan Porto Carrero Blog: http://flanders.co.nz Twitter: http://twitter.com/casualjim Author of IronRuby in Action (http://manning.com/carrero) On Fri, Jan 15, 2010 at 4:46 PM, Ryan Riley <ryan.ri...@panesofglass.org>wrote: > On Thu, Jan 14, 2010 at 3:13 PM, Ivan Porto Carrero > <i...@flanders.co.nz>wrote: > >> That's fine but my point is that if you just want to just use ironruby do >> NOT get the sources.. they haven't been updated in a while and the 1.0 RC1 >> version is probably very close to what you get with building from source but >> without the added hassle and changed gems location. There is no obvious win >> anymore when you build from source. >> > > That's a shame. Will this change at some point? I suppose it really doesn't > matter when all you want to do is use IronRuby. Are there any build options > to set the gems location? > > Ryan > > _______________________________________________ > 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
