On Thu, Jul 2, 2009 at 10:13 AM, rogerdpack<[email protected]> wrote: > >> I am lost now about what the 'problem' is?!! I can't see any valid >> reason to be making a C file and asking to complile it for a app >> scaffold and there's no explanation pointing this problem on just my >> machine. > > looks like merb uses parse tree to introspect methods [parse tree > apparently uses ruby inline to do its compilation at run time]. > Typically parse tree ships with binaries already built, but that might > only be for ruby 1.8.6 > > xyou could try with 1.8.6 or try installing the mingw compiler > [devkit: > http://programming-gone-awry.blogspot.com/2009/05/ruby-19-one-click-installer.html] > [and a a mingw friendlier rubyinline > http://github.com/rogerdpack/rubyinline/tree/master] >
AFAIK RubyInline was MinGW friendly :-P I worked and send the patches to it, but seems that something changed. Lot of projects to send patches. Too bad ParseTree cannot be built like normal gems. -- Luis Lavena AREA 17 - Perfection in design is achieved not when there is nothing more to add, but rather when there is nothing more to take away. Antoine de Saint-Exupéry --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "merb" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/merb?hl=en -~----------~----~----~----~------~----~------~--~---
