llvm dev - Mar 2005 - [LLVMdev] VC++ 2003

I am currently playing around with llvm using Visual C++ Express
(beta). It works flawlessly. It takes a while to get started but once
you do, everything is perfect. Make sure to get the latest CVS
sources, the 1.4 release doesn't play nice with Visual Studio. Once
you do, extract the file I attach to this email into the llvm\win32
folder. Then add llvm/win32\tools folder to a list of executable
search paths in VC options->directories. The instructions aren't
complete on this and it took me a couple of hours to figure out how to
get this working. Once you do this, you can just double click on the
sln file and build.


On Wed, 9 Mar 2005 18:11:32 -0600, Misha Brukman <brukman at uiuc.edu>
wrote:
> On Wed, Mar 09, 2005 at 04:07:19PM -0800, xavier wrote:
> > I was trying to know if LLVM 1.5 works better with VC++ 2003 and to
> > what extent. This link:
> >
> > llvm.cs.uiuc.edu/releases/1.5
> >
> > Referred to in : llvm.cs.uiuc.edu/docs/ReleaseNotes.html
> >
> > Is broken
> 
> LLVM 1.5 hasn't been released yet. :)
> This is the current work-in-progress that will be finished soon.  If you
> want the most current version of LLVM, please use CVS:
> 
> llvm.cs.uiuc.edu/docs/GettingStarted.html#checkout
> 
> > Where can I find more information? In particular:
> > Can the LLVM be compiled using VC++ 2003?
> > Does it generate bytecode and executable code?
> 
> llvm.cs.uiuc.edu/docs/GettingStartedVS.html
> 
> --
> Misha Brukman :: misha.brukman.net :: llvm.cs.uiuc.edu
> 
> _______________________________________________
> LLVM Developers mailing list
> LLVMdev at cs.uiuc.edu         llvm.cs.uiuc.edu
> mail.cs.uiuc.edu/mailman/listinfo/llvmdev
>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: tools.zip
Type: application/x-zip-compressed
Size: 1174967 bytes
Desc: not available
URL:
<lists.llvm.org/pipermail/llvm-dev/attachments/20050309/0792500f/attachment.bin>

Vyacheslav Akhmechet wrote:
>Then add llvm/win32\tools folder to a list of executable
>search paths in VC options->directories. 
>
Actually, this is not required and the projects are set up to work 
without that directory being in the search path.  That list of 
directories is global to the whole machine, and it is bad form for LLVM 
to have an impact on any other solutions that you may wish to build.
>The instructions aren't
>complete on this and it took me a couple of hours to figure out how to
>get this working. Once you do this, you can just double click on the
>sln file and build.
>  
>
Please e-mail me any difficulties you had in following the 
instructions.  In particular, why were you forced to modify the 
executable search path?

> Please e-mail me any difficulties you had in following the
> instructions.
Visual Studio instructions say that LLVM requires bison, flex and sed
in the llvm/win32/tools directory and provide appropriate links to
download them. This isn't complete because bison also expects
llvm/win32/share directory which has to include bison/m4sugar/ along
with appropriate m4sugar files. Furthermore, Unxutils at sourceforge
project doesn't include m4sugar with its distribution which adds an
additional degree of frustration. None of this is a big deal but it
takes some time to get working, especially for someone who isn't used
to gnu tools (like myself).
> In particular, why were you forced to modify the
> executable search path?
At this point, I'm not sure. I'll check tonight when I get home and
will get back to you.