similar to: [LLVMdev] adding a target for "-march=" option in Visual Studio

No, No... That's OK. I appreciate your concerns. Seung Jae Lee ---- Original message ---- >Date: Mon, 16 Apr 2007 13:30:59 -0700 >From: Jeff Cohen <jeffc at jolt-lang.org> >Subject: Re: [LLVMdev] adding a target for "-march=" option in Visual Studio (Resolved) >To: LLVM Developers Mailing List <llvmdev at cs.uiuc.edu> > >Seung Jae Lee wrote:

I resolved this by adding the path of .obj file in the linker options in LLC property page. Thank you. Seung Jae Lee

Xi, I just installed VS2005 pro w/ SP1 for Win Vista. Thanks, Seung ---- Original message ---- >Date: Fri, 22 Feb 2008 12:36:43 +0800 >From: "Xi Wang" <xi.wang at gmail.com> >Subject: Re: [LLVMdev] Is there someone tried LLVM 2.1 on Visual Studio 2005? >To: "LLVM Developers Mailing List" <llvmdev at cs.uiuc.edu> > >I'm sorry but did you

Thank you for your kind explanation. I did it as you mentioned. That is, I set '-march=x86 hello.bc' in the Command Arguments. (I also set my compiled LLC, i.e., LLVM_ROOT_DIR\win32\debug\llc.exe, in the property name Command.) But, when I made a breakpoint in main( ) of llc.cpp and then started to debug I found the 'InputFilename'(llc.cpp:176) is shown like {???}. Therefore it

Seung Jae Lee wrote: > I followed the steps in "Getting Started with the LLVM System using Microsoft Visual Studio" in the document in LLVM page. > > I made hello.c file exactly same shown in the page. > I made hello.bc on UNIX and transferred it to my Windows computer. > And I typed "llc -march=c hello.bc" > (Of course, I downloaded the latest version of LLVM

It is, if only because it's the version I use, but 2005 is supposed to work also. That being said, I wouldn't be surprised to learn that it doesn't due to recent STL issues. Versions prior to 2003 won't work. Seung Jae Lee wrote: > I just wonder that Visual Studio .NET 2003 is the most compatible one among various MS Visual Studio versions for LLVM. > > Thank you >

Thanks--I was offline when I wrote it, couldn't Google. Found it in about 5 seconds once I was back online. Second question: I'm getting various build errors relating (it seems) to configuration: can't find windows.h and so forth. Where (or to whom) is the best place to report these and iterate until we fix them? Ted Neward Java, .NET, XML Services Consulting, Teaching, Speaking,

Hola Seung, I don't know if 2.1 in particular worked. I updated the 2.2 win32 vstudio 2k5 files right before lockdown, so they should be building. You will need appropriate versions of flex and bison installed. I used the ones from getgnuwin32 on my machine. Good luck. Chuck. -----Original Message----- From: llvmdev-bounces at cs.uiuc.edu [mailto:llvmdev-bounces at cs.uiuc.edu] On Behalf

I just wonder that Visual Studio .NET 2003 is the most compatible one among various MS Visual Studio versions for LLVM. Thank you Seung Jae Lee

If you are using the Express versions of Visual Studio, the Platform SDK(windows.h) is a seperate install that you have to download. Kevin Tew Ted Neward wrote: > Thanks--I was offline when I wrote it, couldn't Google. Found it in about 5 > seconds once I was back online. > > Second question: I'm getting various build errors relating (it seems) to > configuration:

Hello. I wonder how I can use the options of LLVM commands in Visual Studio Debugging mode. For example, If I want to follow the pass on 'llc -march=x86 hello.bc' in the Visual Studio's debuggin mode, how can I let it know the options such as '-march=x86 hello.bc'? I can set the breakpoint in main() in llc.cpp but I can't let it cognize that I want X86 assembly code from

>I have flex and bison from Cygwin installed: WinGNU32 Flex and Bison are the ones to use with LLVM and Visual Studio. http://gnuwin32.sourceforge.net/ The LLVM Visual Studio .sln file is for Visual Studio 2003 so will require conversion and some minor modification. Aaron > Should that work, assuming they're on the PATH? When I ran the build from > inside VS, I get some

I followed the steps in "Getting Started with the LLVM System using Microsoft Visual Studio" in the document in LLVM page. I made hello.c file exactly same shown in the page. I made hello.bc on UNIX and transferred it to my Windows computer. And I typed "llc -march=c hello.bc" (Of course, I downloaded the latest version of LLVM and compiled with VS before this.) But my command

I have always built it with flex and bison installed, though I believe Chris removed our last dependence on flex a little while back, so you may not need that. I'm using bison 2.1 which I got from the getgnuwin32 folks. I imagine that if you have cygwin or the like, you probably already have everything. You will need to have the executables in your path. I build with VisualStudio 2k5

I simply found it at: http://getgnuwin32.sourceforge.net/ Seung ---- Original message ---- >Date: Tue, 12 Feb 2008 21:11:04 -0800 >From: "Ted Neward" <ted at tedneward.com> >Subject: Re: [LLVMdev] Is there someone tried LLVM 2.1 on Visual Studio 2005? >To: "'LLVM Developers Mailing List'" <llvmdev at cs.uiuc.edu> > >I'm sorry,

I have flex and bison from Cygwin installed: $ flex --version flex version 2.5.4 $ bison --version bison (GNU Bison) 2.3 Written by Robert Corbett and Richard Stallman. Copyright (C) 2006 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. Should that work,

OK, a couple of things aren't parsing here. > When config.h.in is hit in the build of configure the configure > project, > the configure.h file from the win32 directory is copied to main > llvm\Config\Config.h. The script in the sln file is: > There is no "configure.h" file from the win32 directory; there is a config.h, and it's 600 bytes long, compared to the

More on this: Walking through the projects slowly: (*) "Configure" builds with no problem. (*) "support" fails: C:\Prg\llvm-2.2\llvm-2.2\win32>msbuild llvm.sln /t:Build Microsoft (R) Build Engine Version 2.0.50727.1433 [Microsoft .NET Framework, Version 2.0.50727.1433] Copyright (C) Microsoft Corporation 2005. All rights reserved. Build started 2/18/2008 12:07:45 AM.

By the way, somebody (I think it was Chuck, but I don't remember for certain) was asking for the BuildLog.htm from building the llvm.sln file under VS 2005 SP1 for diagnostic purposes; right now the SLN is configured to produce a new BuildLog for each and every one of the projects inside the solution. I don't know who's responsible for this guy, but that's probably not the best way

I use VS2005/Vista, which works well... Thx, Seung ---- Original message ---- >Date: Wed, 20 Feb 2008 12:02:29 +0800 >From: "Xi Wang" <xi.wang at gmail.com> >Subject: Re: [LLVMdev] Is there someone tried LLVM 2.1 on Visual Studio 2005? >To: "LLVM Developers Mailing List" <llvmdev at cs.uiuc.edu> > >Hi there, > >Did anyone try