search for: build_thi

Displaying 4 results from an estimated 4 matches for "build_thi".

Did you mean: build_this
2013 May 27
2
[LLVMdev] [cfe-dev] [3.3 Release] Release Candidate 2 Available
...ence). >> > > Hi Sean, > > I've created ReleaseProcess.rst, how can I force generation of HTML on the > rst file without rebuilding the whole thing? > > The following incantation should work (invoked from docs/): sphinx-build -b html -d _build/doctrees . _build/html $BUILD_THIS.rst Basically, this is the command that the makefile executes by default, with $BUILD_THIS.rst appended. Trailing filenames given to sphinx-build are interpreted to mean that it should build just those; if given no filenames (as when invoked by the Makefile), it defaults to building all of them (...
2013 May 28
0
[LLVMdev] [cfe-dev] [3.3 Release] Release Candidate 2 Available
...>> >> I've created ReleaseProcess.rst, how can I force generation of HTML on >> the rst file without rebuilding the whole thing? >> >> > The following incantation should work (invoked from docs/): > > sphinx-build -b html -d _build/doctrees . _build/html $BUILD_THIS.rst > > Basically, this is the command that the makefile executes by default, with > $BUILD_THIS.rst appended. Trailing filenames given to sphinx-build are > interpreted to mean that it should build just those; if given no filenames > (as when invoked by the Makefile), it defaults t...
2013 May 26
0
[LLVMdev] [cfe-dev] [3.3 Release] Release Candidate 2 Available
On 26 May 2013 03:03, Sean Silva <silvas at purdue.edu> wrote: > AFAIK, the closest we have is <http://llvm.org/docs/HowToReleaseLLVM.html>, > which details basically what the release manager has to do (i.e., the > audience is LLVM developers, and release managers in particular). I really > liked the article you linked because it seemed to be targeted at an > audience
2013 May 26
2
[LLVMdev] [cfe-dev] [3.3 Release] Release Candidate 2 Available
On Sat, May 25, 2013 at 1:52 PM, Renato Golin <renato.golin at linaro.org>wrote: > On 25 May 2013 20:42, Sean Silva <silvas at purdue.edu> wrote: > >> Could you please incorporate this useful document into LLVM's official >> documentation? I think that this is good content for encouraging greater >> external/downstream involvement in the release process.