similar to: [LLVMdev] Building on windows

Hi I have a ModulePass in LLC that runs after most of codegen completes, right before OBJ emission. I want the ModulePass to iterate over all MachineFunctions, emulating them. I used to do this by iterating over all Module Function's, and using MachineFunction::get() to get the MachineFunction associated with said Function. In LLVM 2.6, MachineFunction::get() is gone. What is the new way

2008/12/30 srs <skaflotten at gmail.com> > Óscar Fuentes wrote: > > srs <skaflotten at gmail.com> writes: > > > > > >>>> While testing my compiler on win32 in JIT mode, I ran into a couple of > >>>> issues: > >>>> > >>>> 1. I linked the compiler with the lib files resulting from the cmake >

Hi all, The attached patch contains two small corrections to the Building LLVM with CMake document (CMake.html). BTW why it is not referenced from index.html? Is CMake support in LLVM not considered mature enough? Best regards, Victor -------------- next part -------------- An HTML attachment was scrubbed... URL:

Hi Takumi, THANK YOU for your excellent review! It makes all the work worthwhile in itself. It is getting "late" here (it is early morning) so I am about to call it a day. But I will contemplate and incorporate your suggestions tomorrow, and send you a full reply. I think I originally wrote a document where I addressed both Visual Studio and MinGW, but then decided that there were

Óscar Fuentes wrote: > srs <skaflotten at gmail.com> writes: > > >>>> While testing my compiler on win32 in JIT mode, I ran into a couple of >>>> issues: >>>> >>>> 1. I linked the compiler with the lib files resulting from the cmake >>>> created VS.NET build. While everything built just fine, the >>>>

Mikael, Thanks for working on. My gross comments... - Canonical URL of LLVM project is; http://llvm.org/ , not www.llvm.org. - "test-suite and cygwin" could be split out. It would be special thing. - Memory/storage requirements would be moved to "A.B Debugging". Less memory would be enough without debug build. - Python (x64 binary) is available, too. I am using. Python

I need to build LLVM on Win XP VM. Are there any detailed instructions for that? Thank you -Shad Ahmad | Release Manager, Adobe AIR | Adobe Systems, Inc | sahmad at adobe.com | 408.536.4101

As for Ninja, I'd like to wait until it is officially part of the released CMake. As I understand it, Windows support has been checked into the CMake repository but no offical release supporting Ninja has been made yet. I just retrieved Ninja from Github and this time it built without problems. 2012/6/16 NAKAMURA Takumi <geek4civic at gmail.com> > Mikael, > > Thanks for

On Sat, Jun 16, 2012 at 3:29 AM, Mikael Lyngvig <mikael at lyngvig.org> wrote: > Hi Takumi, > > THANK YOU for your excellent review! It makes all the work worthwhile in > itself. > > It is getting "late" here (it is early morning) so I am about to call it a > day. But I will contemplate and incorporate your suggestions tomorrow, and > send you a full

Oh, didn't realize that there already is a semi-official build of CMake with Ninja support. I am trying it out right now and it seems very promising. So I'll change the document to use Ninja instead of "MinGW Makefiles". No need to waste energy on MinGW and MSYS Makefiles when Ninja outdoes them both. I thought people would have to build CMake themselves, something I'd

Now I can't make CMake use "MSYS Makefiles". I get an error about GNU v4.7.0 being broken as it can't build a simple test program. Using "MinGW Makefiles", everything works out of the box. And I am trying to give the user the most Windowsy experience (to avoid Cygwin, GnuWin32, and MSYS, if I can). So I think I'll stick to my current angle - which is to let the

Hi, All, I follow the menu http://llvm.org/docs/GettingStartedVS.html , but still failed to build LLVM debug version. Here's error message: 7>C:\study\llvm\projects\compiler-rt\lib\asan\asan_win.cc(69): fatal error C1189: #error : Please build the runtime with a non-debug CRT: /MD or /MT Any idear? -- Best Regards, Amy -------------- next part -------------- An HTML attachment was

Duncan Sands <baldrick at free.fr> writes: > Hi, > >> CMake just requires one plain text file named CMakeLists.txt on every >> source directory, and the only maintenance is to keep up to date the >> list of source files of the directory. > > can it be kept up-to-date automagically? After all, you can query > subversion to get the list of all files in a

Hi again, The Visual Studio getting started guide ( http://llvm.org/docs/GettingStartedVS.html) mentions the "llvm-lit" tool, but fails to mention these things: 1. Either you need to run it from bash or a similar Unix shell, as Windows does not recognize the extensionless Python script that it is. 2. Alternatively, you can invoke it using Python like this: python bin/llvm-lit

Manuel Klimek <klimek at google.com> writes: >> >> CMake generates gigantic project files for IDEs like Visual Studio and >> >> Xcode, which causes those IDEs to behavior very poorly, with long >> >> project load times and sluggish overall performance. It's a significant >> >> productivity problem. >> > -- Douglas Gregor, On 26

done http://llvm.org/bugs/show_bug.cgi?id=5331 shrey On Wed, Oct 28, 2009 at 3:29 PM, Óscar Fuentes <ofv at wanadoo.es> wrote: > shreyas krishnan <shreyas76 at gmail.com> writes: > >>     I am running into bunch of windows build issues. Can someone >> please provide help on what might be going wrong >> >> >>

Mason Wheeler <masonwheeler at yahoo.com> writes: >>If the following statement is true, then which build system to choose >>is a no-brainer: > >>> cmake, while ugly, can be made to support all of our use cases. There >>> are some use cases that autoconf+make can't support >>-- Chandler Carruth, On 21 Jun 2012, at 01:19 > > Unfortunately, >

[Repost: The mailing list was down yesterday. Sorry if this is a duplicate] I'm evaluating CMake (1) primarily as an alternative build system for Visual Studio users, although it can easily be a replacement for `configure' and hand-made makefiles too, providing a single build system for all platforms. CMake is a tool that takes a project description and configures, generates makefiles,

IMHO, the CMake-based build system is almost complete enough to replace current MSVC++ project files (modulo some community review and bug-fixing). Is this enough for adding it to the LLVM repo? >From the point of view of a MSVC++ user, the new build system is trivial to maintain: you can add a new library or tool executable in less time that it takes to open the project file on MSVC++, it

How is the LLVM toolchain built for Windows? I'm working on VS integration. Like, in Xcode, the actual *.xctoolchain bundle is built using the regular cmake files, plus using the cmake build script in tools/xcode-toolchain, what is the windows equivalent? is it literally just the stuff in tools/msbuild, or is there more to it than that? -------------- next part -------------- An HTML