Hello, Jon> What threw me was the projects inclusion of 2 of the 3 other pieces that make up a typical manual install of mingw or http://www.tdragon.net/recentgcc/ I saw the runtime and w32api stuff in my very quick scan of the llvm-gcc dir and didn't bother to confirm binutils :(Well, binutils are quite different: 1. It's GPL-licensed, thus we need to provide sources as well, which is bit inconvenient 2. You need to have headers & libs in predefined dirs to let gcc / llvm-gcc pick them w/o any additional options, this is not case of binutils - you just need stuff in path> Take me up on my offer to submit a doc patch...point me to the proper html source and I'll send you a diff for review.Just grab the GettingStarted.html page, seems to be pretty convenient place. Thanks! -- With best regards, Anton Korobeynikov Faculty of Mathematics and Mechanics, Saint Petersburg State University
On Dec 16, 2009, at 8:34 AM, Anton Korobeynikov wrote:> Hello, Jon > >> What threw me was the projects inclusion of 2 of the 3 other pieces >> that make up a typical manual install of mingw or http://www.tdragon.net/recentgcc/ >> I saw the runtime and w32api stuff in my very quick scan of the >> llvm-gcc dir and didn't bother to confirm binutils :( > Well, binutils are quite different: > 1. It's GPL-licensed, thus we need to provide sources as well, which > is bit inconvenient > 2. You need to have headers & libs in predefined dirs to let gcc / > llvm-gcc pick them w/o any additional options, this is not case of > binutils - you just need stuff in path > >> Take me up on my offer to submit a doc patch...point me to the >> proper html source and I'll send you a diff for review. > Just grab the GettingStarted.html page, seems to be pretty > convenient place. >Hi Jon, Just in case it's not clear, the svn for that page is part of the llvmCore project. Specifically, https://llvm.org/svn/llvm-project/llvm/trunk/docs/GettingStarted.html Thanks for offering to help with the documentation. Making things clearer for new users is always a good thing. Regards, Jim
> Just in case it's not clear, the svn for that page is part of the > llvmCore project. Specifically, > > https://llvm.org/svn/llvm-project/llvm/trunk/docs/GettingStarted.html > > Thanks for offering to help with the documentation. Making things > clearer for new users is always a good thing. > > Regards, > JimIf I do a sparse checkout like>svn co http://llvm.org/svn/llvm-project/llvm/trunk llvm-trunk --depth empty >cd llvm-trunk >svn up --depth files docsand send you mods via an "svn diff" as an attachment using GTK+ based http://sylpheed.sraoss.jp/en/ will that work? Note the doc/* files came in to my local repo as CRLF based. I'm guessing their LF on your systems. Anything special I need to do for edit/diffing for the patch so you don't have to deal with EOL nonsense? Jon
> > What threw me was the projects inclusion of 2 of the 3 other pieces that make up a typical manual install of mingw or http://www.tdragon.net/recentgcc/ I saw the runtime and w32api stuff in my very quick scan of the llvm-gcc dir and didn't bother to confirm binutils :( > Well, binutils are quite different: > 1. It's GPL-licensed, thus we need to provide sources as well, which > is bit inconvenientTo make it easier to use the LLVM-GCC MinGW32 binary and meet your GPL licensing requirements, could you embed the MinGW binutils binary as-is in the LLVM-GCC MinGW32 and update the LLVM docs to point to the MinGW SourceForge download site for those wanting the MinGW binutils source? Is the GPL the only reason why binutils isn't currently included in the LLVM-GCC MinGW32 binary? http://www.gnu.org/licenses/gpl-faq.html#SourceAndBinaryOnDifferentSites Jon
Hello, Jon> To make it easier to use the LLVM-GCC MinGW32 binary and meet your GPL licensing requirements, could you embed the MinGW binutils binary as-is in the LLVM-GCC MinGW32 and update the LLVM docs to point to the MinGW SourceForge download site for those wanting the MinGW binutils source?I still don't think it's good idea. binutils will add something like 10Mb to package download size. Also, in almost all cases llvm-gcc user is mingw user as well, which will lead to two different sets of linkers (possible) located in the PATH... -- With best regards, Anton Korobeynikov Faculty of Mathematics and Mechanics, Saint Petersburg State University