Displaying 20 results from an estimated 10000 matches similar to: "[LLVMdev] Anybody translating the LLVM FAQ from HTML to Sphinx?"
2012 Jun 13
5
[LLVMdev] Anybody translating the LLVM FAQ from HTML to Sphinx?
That reminds me: Do the web documents reside in a repository somewhere or
should I just grab them using wget?
2012/6/14 Michael Spencer <bigcheesegs at gmail.com>
> On Wed, Jun 13, 2012 at 4:02 PM, Mikael Lyngvig <mikael at lyngvig.org>
> wrote:
> > If nobody else is doing it, I can translate the FAQ into Sphinx as I'd
> like
> > to begin gradually extending
2012 Jun 13
0
[LLVMdev] Anybody translating the LLVM FAQ from HTML to Sphinx?
On Wed, Jun 13, 2012 at 4:02 PM, Mikael Lyngvig <mikael at lyngvig.org> wrote:
> If nobody else is doing it, I can translate the FAQ into Sphinx as I'd like
> to begin gradually extending it so that it some day becomes more than just
> bare metal. I figure that extending the FAQ is one way to reduce the
> "noise" on the various mailing lists.
>
>
> Cheers,
2012 Jun 13
0
[LLVMdev] Anybody translating the LLVM FAQ from HTML to Sphinx?
On Wed, Jun 13, 2012 at 4:47 PM, Mikael Lyngvig <mikael at lyngvig.org> wrote:
> That reminds me: Do the web documents reside in a repository somewhere or
> should I just grab them using wget?
The website is at http://llvm.org/viewvc/llvm-project/www/trunk/ . The
llvm docs are in llvm/docs.
Which actually makes me wonder if the LLVM-project FAQ (in reference
to Chandler's post in
2012 Jun 13
0
[LLVMdev] Anybody translating the LLVM FAQ from HTML to Sphinx?
On Jun 13, 2012, at 4:47 PM, Mikael Lyngvig wrote:
> 2012/6/14 Michael Spencer <bigcheesegs at gmail.com>
> On Wed, Jun 13, 2012 at 4:02 PM, Mikael Lyngvig <mikael at lyngvig.org> wrote:
> > If nobody else is doing it, I can translate the FAQ into Sphinx as I'd like
> > to begin gradually extending it so that it some day becomes more than just
> > bare
2012 Jun 14
4
[LLVMdev] Develop on trunk.
As I read, I'm writing stuff here things come to me:
1. Don't indent the list. Some of the other RST files do this, but it is
incorrect since it indents the list! The list is semantically "at the top
level" of indentation (it's not a sub-element of anything).
2. don't have that mini "table of contents" list at the beginning. sphinx
will generate that itself
2012 Jun 13
2
[LLVMdev] Develop on trunk.
On Wed, Jun 13, 2012 at 4:37 PM, Mikael Lyngvig <mikael at lyngvig.org> wrote:
> I think the best way that I can currently contribute to the project is
> through technical writing. So I see myself as doing a serious, long-term
> project of extending the FAQ. So, I can affirm that I want to really start
> working :)
Awesome.
I was myself thinking of a number of FAQs:
>
2012 Jun 14
0
[LLVMdev] Develop on trunk.
Done. Do you want to see it again or should I simply ship it off to
llvm-commits? The only thing I've changed from the original HTML is that
I've changed a few missing code pieces into using code markup. And now
I've made the changes you requested and I think it looks really good: Each
question being a subsection of its own works very well in my opinon.
Oh, heck, I might as well
2012 Jun 13
0
[LLVMdev] Develop on trunk.
Okay with the manual versus FAQ strategy. I just have to mention that
languages like C++ has many FAQs all over the net, altogether totalling
perhaps thousands of questions and I see C++ as simple compared to LLVM.
But I have plenty to do now. If nothing else, I could try reading the
manuals ;-)
2012/6/14 Chandler Carruth <chandlerc at google.com>
> On Wed, Jun 13, 2012 at 4:37 PM,
2012 Jun 14
2
[LLVMdev] Default to "reply all" for mailing list messages?
The irony of this reply is killing me :)
On Wed, Jun 13, 2012 at 7:54 PM, Mikael Lyngvig <mikael at lyngvig.org> wrote:
> You're not alone :) Don't let it bug you.
>
> I finally decided to install a GMail extension that enables reply-all for
> all messages, because I kept forgetting. Perhaps you can find such an
> extension or simply enable reply-all by default?
2012 Jun 14
2
[LLVMdev] Develop on trunk.
> 8. A Technical Writer FAQ (should include the Sphinx documentation from
the lld docs).
I'm working on the Sphinx stuff; if you have any questions about writing
Sphinx docs feel free to ask.
--Sean Silva
On Wed, Jun 13, 2012 at 4:37 PM, Mikael Lyngvig <mikael at lyngvig.org> wrote:
> I think the best way that I can currently contribute to the project is
> through technical
2012 Jun 14
0
[LLVMdev] Develop on trunk.
All sounds good to me. I actually did try to follow the Python style when
I used the ^^^ thingies for the questions (they're called subsubsections).
4. I'm not sure exactly how to markup the questions. The sphinx FAQ (
> http://sphinx.pocoo.org/faq.html) marks it up as a definition list
> (ctrl-f "definition list" http://sphinx.pocoo.org/rest.html). On the
> other
2012 Jun 14
0
[LLVMdev] Develop on trunk.
I just finished up the first draft of the FAQ translated verbatim from HTML
to Sphinx. Sphinx did puzzle me a few times but I got used to its
approximate error messages and figured out what the problems were.
Perhaps you could take a quick glance at this file and tell me if I am
doing something wrong? Otherwise I'll send it off to llvm-commits and see
what they say.
Thanks,
Mikael
2012 Jun 09
2
[LLVMdev] Final Windows MinGW buildbot slave document...
Hi,
Here's the final, confirmed working version of my Windows guide for how to
set up a MinGW buildbot slave. Please consider to include it in the
documentation on the LLVM website.
Basically, it saves the newcoming Windows user about two or three days of
experimentation to get it all working. I think those days are important as
many people balk at spending days on figuring out how to get
2012 Jun 14
0
[LLVMdev] Default to "reply all" for mailing list messages?
Hehe, I intentionally left out the group because I just wanted to cheer you
up and let you know that there's more than one "retard" on the list.
2012/6/14 Sean Silva <silvas at purdue.edu>
> The irony of this reply is killing me :)
>
>
> On Wed, Jun 13, 2012 at 7:54 PM, Mikael Lyngvig <mikael at lyngvig.org>wrote:
>
>> You're not alone :)
2012 May 27
2
[LLVMdev] Linking times
Hi,
Just a brief follow-up on my link time issue: It was caused by excessive
trashing; I tried rebuilding on a box with 8 gigs of RAM and observed the
memory load while linking clang.exe: It peaked at 5 gigabytes memory, so
now I've written this piece of info into the LLVM/Windows document that I
posted earlier (I have already made a substantial number of corrections in
the document). All in
2012 Jun 11
0
[LLVMdev] Final Windows MinGW buildbot slave document...
On Sat, Jun 9, 2012 at 12:40 AM, Mikael Lyngvig <mikael at lyngvig.org> wrote:
> Hi,
>
> Here's the final, confirmed working version of my Windows guide for how to
> set up a MinGW buildbot slave. Please consider to include it in the
> documentation on the LLVM website.
>
> Basically, it saves the newcoming Windows user about two or three days of
>
2012 Jun 14
1
[LLVMdev] Default to "reply all" for mailing list messages?
btw, the "default reply-to-all" extension for gmail works great!
On Wed, Jun 13, 2012 at 8:11 PM, Mikael Lyngvig <mikael at lyngvig.org> wrote:
> Hehe, I intentionally left out the group because I just wanted to cheer
> you up and let you know that there's more than one "retard" on the list.
>
>
> 2012/6/14 Sean Silva <silvas at purdue.edu>
>
2012 Jun 15
4
[LLVMdev] LLVM Sphinx intro buried in lld doc?
Am I the only one who thinks that it is impractical that the Sphinx intro
is buried deep within the lld documentation? I suggest moving it to the
Programming Documentation document.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20120616/2cb7356d/attachment.html>
2012 May 27
0
[LLVMdev] Linking times
Do you specify CMAKE_BUILD_TYPE
if you are using cmake?
2012/05/27 18:21 "Mikael Lyngvig" <mikael at lyngvig.org>:
> Hi,
>
> Just a brief follow-up on my link time issue: It was caused by excessive
> trashing; I tried rebuilding on a box with 8 gigs of RAM and observed the
> memory load while linking clang.exe: It peaked at 5 gigabytes memory, so
> now I've
2012 May 28
3
[LLVMdev] liblibclang.dll?
Hi,
I accidentally noticed the following line when building LLVM and Clang on
Windows 7 x64 using Mingw64:
Linking CXX shared library ..\..\..\..\bin\liblibclang.dll
"Liblib" seems a bit overkill. FYI.
BTW, for those who happen to search on LLVM, Clang, Windows, and Mingw64:
The v3.1 release does NOT build with Mingw64. I believe this has been
fixed in the Subversion sources as