On Mar 8, 2010, at 3:19 PM, Jon wrote: >> LLVM is used only at runtime, specificly within the JIT for lowlevel >> optimizations and code generation. >> >> The build options are because using the JIT is optional and therefore >> linking against LLVM is optional. > > I'm good now. > > This tells me that if I've installed the prebuilt MinGW LLVM binaries > (named llvm-as.exe, llvm-link.exe, llc.exe, lli.exe, etc) to c:\llvm I > need to point configure's --llvm-path to c:\llvm and then look out for > potential tool naming issues as the JIT may be trying to call the > tools by another name. Probably have to move the exe's to c:\llvm\bin > and put llvm headers and libraries in c:\llvm\include and c:\llvm\lib > as well after looking at > http://github.com/evanphx/rubinius/blob/master/vm/llvm/jit.hpp > And probably tweak configure a bit. > > I'll save compiling rubinius via llvm-gcc until I can get a basic msys/ > mingw setup working :)
There hasn't been a whole lot of attention from Windows users, so you may run into a few more challenges than usual. Rubinius needs to support Windows so be sure to open tickets when you run into problems building and running it under mingw. Patches are great too if you are so inclined. :) Good luck! cr -- --- !ruby/object:MailingList name: rubinius-dev view: http://groups.google.com/group/rubinius-dev?hl=en post: [email protected] unsubscribe: [email protected]
