llvm dev - Jan 2010 - [LLVMdev] Compiling Kaleidoscope on Windows

I'm trying to get the Kaleidoscope tutorial mini compiler working on
Windows (as a trial run for developing a compiler using LLVM).

Kaleidoscope uses the C++ linkage method of code generation (as
opposed to spitting out intermediate code in a text or binary file),
which as I understand it is the preferred way of doing it for a few
reasons, one of them being that it gives you JIT capability, which in
turn lets you provide an interactive mode.

This requires compiling it with the LLVM headers, and presumably
libraries, which don't seem to be included in the Windows binary
distribution of LLVM, so presumably it is necessary to go to the
source distribution.

Is it necessary to compile the whole shebang from source, or would it
suffice/be easier to just compile the libraries?  All the references I
could find with Google, discuss the first option.

According to
http://stackoverflow.com/questions/2129263/how-to-build-llvm-using-gcc-4-on-windows
it seems LLVM prefers to use MinGW 3.4.5 rather than 4.x, is this
correct?

http://blogs.tedneward.com/2008/02/24/Building+LLVM+On+Windows+Using+MinGW32.aspx
discusses a procedure involving MinGW 3.4.5, is that the recommended
procedure? He mentions LLVM version 2.2, which is a few versions
behind the current release. Are the versions of the various components
of MinGW he mentions, still the preferred ones for working with LLVM
2.6?

Thanks to OvermindDL1 for pointing this out: compiling with Visual C++
actually works! Basically it's just a matter of running cmake (default
settings are fine) then nmake, and I've got what appears to be a
working version of LLVM.

Kaleidoscope crashes on attempting to exit with ^Z:

C:\llvm\bin>Kaleidoscope.exe
ready> 1+2;
ready> Evaluated to 3.000000
ready> 3*4;
ready> Evaluated to 12.000000
ready> ^Z
ready> ; ModuleID = 'my cool jit'

declare void @abort()

define double @0() {
entry:
  ret double 3.000000e+000
}

define double @1() {
entry:
  ret double 1.200000e+001
}
While deleting: double ()* %
An asserting value handle still pointed to this value!
UNREACHABLE executed at C:\d\llvm-2.6\lib\VMCore\Value.cpp:492!

I hope this is just a bug in Kaleidoscope itself, anyone got any idea?

I don't suppose anyone knows what (or how to find out what) the actual
command to compile Kaleidoscope is? I followed cmake/nmake down
through maybe half a dozen levels before getting lost, so I tried to
develop a compiler invocation from scratch. I got as far as

cl /EHsc /I\d\llvm-2.6\include /I\llvm\include /wd4355 toy.cpp

which successfully generated toy.obj and spat out 86 link time error
messages -- as expected, it needs the libraries specified.
cmakelists.txt says set(LLVM_LINK_COMPONENTS core jit interpreter
native) so I made a guess at the .lib file corresponding to the first
of these, and tried

cl /EHsc /I\d\llvm-2.6\include /I\llvm\include /wd4355 toy.cpp
\llvm\lib\llvmcore.lib

in the hope that the number of link time error messages would go
down... but it actually goes up to 395, and the earlier ones don't
obviously have anything to do with llvm itself. Any ideas? The first
few error messages are

msvcprtd.lib(MSVCP90D.dll) : error LNK2005: "public: __thiscall
std::basic_string<char,struct std::char_traits<char>,class
std::allocator<char> >::~basic_string<char,struct
std::char_traits<char>,class std::allocator<char> >(void)"
(??1?$basic_string at DU?$char_traits at D@std@@V?$allocator at D@2@@std@@QAE at
XZ)
already defined in toy.obj
msvcprtd.lib(MSVCP90D.dll) : error LNK2005: "public: __thiscall
std::basic_string<char,struct std::char_traits<char>,class
std::allocator<char> >::basic_string<char,struct
std::char_traits<char>,class std::allocator<char> >(class
std::basic_string<char,struct std::char_traits<char>,class
std::allocator<char> > const &)"
(??0?$basic_string at DU?$char_traits at D@std@@V?$allocator at D@2@@std@@QAE at
ABV01@@Z)
already defined in toy.obj
msvcprtd.lib(MSVCP90D.dll) : error LNK2005: "public: __thiscall
std::basic_string<char,struct std::char_traits<char>,class
std::allocator<char> >::basic_string<char,struct
std::char_traits<char>,class std::allocator<char> >(char const
*)"
(??0?$basic_string at DU?$char_traits at D@std@@V?$allocator at D@2@@std@@QAE at
PBD@Z)
already defined in toy.obj
msvcprtd.lib(MSVCP90D.dll) : error LNK2005: "public: char const *
__thiscall std::basic_string<char,struct std::char_traits<char>,class
std::allocator<char> >::c_str(void)const "
(?c_str@?$basic_string at DU?$char_traits at D@std@@V?$allocator at
D@2@@std@@QBEPBDXZ)
already defined in toy.obj
msvcprtd.lib(MSVCP90D.dll) : error LNK2005: "public: static unsigned
int __cdecl std::char_traits<char>::length(char const *)"
(?length@?$char_traits at D@std@@SAIPBD at Z) already defined in toy.obj