Hi Jon,
I think I need to clarify a little more. You do not need to install
LLVM yourself. I fact, we usually recommend that people don't and use
your configure and build logic to download and build (if necessary)
LLVM.
Aditionally, Rubinius does not use any of the LLVM executables (llvm-
gcc, llc, lli, llvm-as, etc). It solely uses LLVM as a C++ library:
headers, .a files, etc. So pointing Rubinius to where you installed
the executables won't work unless that's the LLVM build dir that also
happens to contain the headers and library files.
Sorry for the confusion.
- Evan // via iPhone
On Mar 8, 2010, at 1:19 PM, Jon <[email protected]> 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 :)
Thanks!!
Jon
Jon
--
--- !ruby/object:MailingList
name: rubinius-dev
view: http://groups.google.com/group/rubinius-dev?hl=en
post: [email protected]
unsubscribe: [email protected]
--
--- !ruby/object:MailingList
name: rubinius-dev
view: http://groups.google.com/group/rubinius-dev?hl=en
post: [email protected]
unsubscribe: [email protected]
