Hi, Here is my first try to document, how to build the llvm suite for MinGW. 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/ ============================================================ _________________________________________________________________ F� alle de nye og sjove ikoner med MSN Messenger http://messenger.msn.dk/ -------------- next part -------------- A non-text attachment was scrubbed... Name: diff.zip Type: application/x-zip-compressed Size: 3091 bytes Desc: not available URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20050209/5622f212/attachment.bin>
On Wed, 9 Feb 2005, Henrik Bach wrote:> Here is my first try to document, how to build the llvm suite for MinGW.The GettingStarted patch looks fine to me, and I've applied it here: http://mail.cs.uiuc.edu/pipermail/llvm-commits/Week-of-Mon-20050207/023986.html The other patch does not look ok. In particular, it would be much better to submit patches to make MinGW work as much like other platforms as possible. In particular, instead of telling the user to patch their sources and pass funny flags into make, it would be better to apply the patch to mainline CVS and fix the makefiles. :) Thanks, -Chris -- http://nondot.org/sabre/ http://llvm.cs.uiuc.edu/
On Wed, Feb 09, 2005 at 09:10:03PM +0100, Henrik Bach wrote:> Here is my first try to document, how to build the llvm suite for MinGW.Chris already committed your patch, but I changed it as follows: http://mail.cs.uiuc.edu/pipermail/llvm-commits/Week-of-Mon-20050207/023987.html Your patch is good for a text file, but since you submitted a patch for HTML documentation, links should use <a href="">, lists should be in a <ul> or <ol> with <li> tags, and code or command lines should be in <tt>. For large blocks of code or command-line interaction, we have <div class="doc_code">, grep for it in the docs and see what it looks like. -- Misha Brukman :: http://misha.brukman.net :: http://llvm.cs.uiuc.edu
On Wed, 9 Feb 2005, Chris Lattner wrote:> On Wed, 9 Feb 2005, Henrik Bach wrote: > >> Here is my first try to document, how to build the llvm suite for MinGW. > > The GettingStarted patch looks fine to me, and I've applied it here: > http://mail.cs.uiuc.edu/pipermail/llvm-commits/Week-of-Mon-20050207/023986.html > > The other patch does not look ok. In particular, it would be much better to > submit patches to make MinGW work as much like other platforms as possible. > In particular, instead of telling the user to patch their sources and pass > funny flags into make, it would be better to apply the patch to mainline CVS > and fix the makefiles. :)Actually, looking closer, I think that some of the content added to the GettingStarted.html file should be moved to the HowToBuildTheCFE document. Specifically I'm thinking of: "If you want to compile the C/C++ frontend, then upgrade to texinfo-4.5+ from source." ... so I removed it. Also, I'm not sure what this is needed for: "If you need to create a library for an MS DLL, do the following: 1. pexports /C/WINNT/SYSTEM32/file.dll | sed "s/^_//" > /C/MinGW/lib/file.def 2. Edit file and append @<ordinal> to the missing function name 3. dlltool.exe -k -d /C/MinGW/lib/file.def -l /C/MinGW/lib/libfile.a." Henrik, can you elaborate on this? If this really is needed in this document, it would be good to move it somewhere other than a footnote... -Chris -- http://nondot.org/sabre/ http://llvm.cs.uiuc.edu/