Hi LLVM'ers, Here is my second try to document, how to build the llvm system for MinGW on Windows. Henrik. ============================================================Henrik Bach LLVM Open Source Developer e-mail: henrik_bach_llvm at hotmail.com ============================================================'Nothing is impossible; The impossible just takes longer time :)' - Inventor of a new energy saver light bulp from Denmark. No software patents - Thank you Poland: http://www.nosoftwarepatents.com/en/m/intro/app0411.html Got Freedom? Software Freedom Day - 28th of August http://www.softwarefreedomday.org/ ============================================================ _________________________________________________________________ Del din verden med MSN Spaces http://spaces.msn.com -------------- next part -------------- A non-text attachment was scrubbed... Name: GettingStartedMinGWWindows.zip Type: application/x-zip-compressed Size: 4438 bytes Desc: not available URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20050310/0725c2d4/attachment.bin> -------------- next part -------------- A non-text attachment was scrubbed... Name: index.html.zip Type: application/x-zip-compressed Size: 521 bytes Desc: not available URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20050310/0725c2d4/attachment-0001.bin>
On Thu, Mar 10, 2005 at 01:59:12PM +0100, Henrik Bach wrote:> Here is my second try to document, how to build the llvm system for > MinGW on Windows.Thanks, Henrik! Here are some comments on your document:> OverviewDoes not mention the status of the CFE on MinGW.> Software on WindowsIf something is a list, use the HTML <ol> or <ul> tags and make it into a real list. Otherwise, it needs to be written as prose (i.e., paragraphs with full sentences). In particular:> Rename or move old perl utils. > > Update your path to perl\bin and perl\bin\arch after mingw in the > path. > > copy pod2man.bat to pod2man and remove dos specific lines in the file. > > configure, make and install binutils. > > move old binutils from c:\mingw\mingw32\bin to > c:\mingw\mingw32\bin\binutils_old even though your environment reaches > the new binutils.This is a list of things to do. They need to be in an HTML list. Perhaps that whole section needs to be a list, as they are all "required steps".> 2. Copy the tools to your --prefix=/some/path/you/can/install/to and add > it to your PATH."make install" is the proper way of doing this, does this not work on MinGW?> 5. make CFLAGS=-O LIBCFLAGS+=-g LIBCFLAGS+=-O2 LIBCXXFLAGS+=-g LIBCXXFLAGS+=-O2Why CFLAGS=-O? Why not -O2? Can the other flags be combined like this: LIBCFLAGS+="-O2 -g" LIBCXXFLAGS+="-O2 -g" for brevity?> 8. make TOOLLINKOPTSB+=-ldbghelp TOOLLINKOPTSB+=-lpsapiSame issue as above.> 10. Not all is working yet: Test the newly-installed C frontend by one > or more of the following means:This isn't clear. What works and what doesn't? What's the status of the CFE on MinGW?> An Example Using the LLVM Tool ChainThis is not changed from the standard Getting Started guide, as I understand it, except for the two sentences in bold: "Note: while you cannot do this step on Windows, you can do it on a Unix system and transfer hello.bc to Windows." and "Not currently possible, but eventually will use NASMW." As such, one cannot really "get started" using ONLY MinGW as their platform, so this entire section should be replaced with a paragraph to that effect, pointing the reader to the standard Getting Started guide for more info. -- Misha Brukman :: http://misha.brukman.net :: http://llvm.cs.uiuc.edu
Misha Brukman wrote:> This is not changed from the standard Getting Started guide, as I > >understand it, except for the two sentences in bold: > >"Note: while you cannot do this step on Windows, you can do it on a Unix >system and transfer hello.bc to Windows." > >and > >"Not currently possible, but eventually will use NASMW." > >As such, one cannot really "get started" using ONLY MinGW as their >platform, so this entire section should be replaced with a paragraph to >that effect, pointing the reader to the standard Getting Started guide >for more info. > >Sounds like these were copied from my Visual Studio guide. It is not obvious they are correct for MinGW. One can build the CFE with MinGW, unlike with VS, and MinGW is basically the GNU tool chain so there's no reason to avoid the GNU assembler.
Hi, Thanks for your comments. I'll make the suggested changes. Henrik ============================================================Henrik Bach LLVM Open Source Developer e-mail: henrik_bach_llvm at hotmail.com ============================================================'Nothing is impossible; The impossible just takes longer time :)' - Inventor of a new energy saver light bulp from Denmark. No software patents Got Freedom? Software Freedom Day - 28th of August http://www.softwarefreedomday.org/ ============================================================ _________________________________________________________________ Del din verden med MSN Spaces http://spaces.msn.com