similar to: [LLVMdev] Doxygen broken?

Displaying 20 results from an estimated 100000 matches similar to: "[LLVMdev] Doxygen broken?"

2012 Apr 25
0
[PATCH] docs: use "a4" not "a4wide" paper type for doxygen and latex
# HG changeset patch # User Ian Campbell <ian.campbell@citrix.com> # Date 1335345862 -3600 # Node ID 057516cb84336da09fe3163aeeb9039cf4d20c26 # Parent 5d796144e8a276ea843c5ad5ec4ae678194d50f3 docs: use "a4" not "a4wide" paper type for doxygen and latex a4wide is no longer shipped in texlive. Reported by Bastian Blank Signed-off-by: Ian Campbell
2020 Jun 07
1
Navbar for documentation is broken in Doxygen 1.8.18
Hi, Here is a patch to update documentation to Doxygen 1.8.18 as the navbar is broken trying to use the latest Doxygen. Also seems we are missing documentation for last releases here: https://www.opus-codec.org/docs/ Best Regards Marcus -------------- next part -------------- An HTML attachment was scrubbed... URL:
2011 Apr 11
0
[LLVMdev] [cfe-dev] LLVM/.Clang: 'make install'
Hi, Sorry, but I cant seem to repeat the issue anymore. 'make install' works fine now. I have no idea what went wrong the first time. Thanks for the effort, and sorry to have bothered you with this. On Mon, Apr 11, 2011 at 2:25 PM, John Myers <atomicdog.jwm at gmail.com> wrote: > Hi, > > make install works for me on Ubuntu. > Does the output of make install show
2011 Apr 11
1
[LLVMdev] [cfe-dev] LLVM/.Clang: 'make install'
Hi, *make install* works for me on Ubuntu. Does the output of *make install* show that it was successful? Was it setup to be installed in a PATH location of Fedora? --John -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20110411/8bab1522/attachment.html>
2009 Nov 02
0
[LLVMdev] llvm-mc build fails
John Myers <atomicdog.jwm at gmail.com> writes: > I'm looking for some pointers on how to troubleshoot this problem. I'm > trying to write a backend for the AVR. > There is an undefined reference at line 48 which is the line FrameInfo() is > on. I've tried to use the MSP430 and other targets as references so I'm not > sure > what changes I did would cause a
2012 Apr 20
3
[LLVMdev] llvm doxygen down?
John, it still doesn't work for me. I'm in upstate new york. And one of my friends in bay area couldn't see the webpage either. Xiaoming On Thu, Apr 19, 2012 at 8:27 PM, John Criswell <criswell at illinois.edu>wrote: > On 4/19/12 7:15 PM, xiaoming gu wrote: > > Hi, all. I find out that the doxygen website (http://llvm.org/docs/doxygen) > is not available now. Does
2010 May 06
0
[LLVMdev] doxygen redux
Excellent work, this greatly improves the clarity of the generated docs. I would love it if the inheritance diagrams were kept as they are and the collaboration diagrams were hidden under a knob. Thanks, John On Fri, Apr 30, 2010 at 8:54 AM, mike-m <mikem.llvm at gmail.com> wrote: > Hi, I'm working on a patch to overhaul docs+doxygen builds for both llvm > and clang source
2009 Nov 02
4
[LLVMdev] llvm-mc build fails
Hi, I'm looking for some pointers on how to troubleshoot this problem. I'm trying to write a backend for the AVR. There is an undefined reference at line 48 which is the line FrameInfo() is on. I've tried to use the MSP430 and other targets as references so I'm not sure what changes I did would cause a problem on this line? AVRTargetMachine::AVRTargetMachine(const Target &T,
2012 Apr 20
0
[LLVMdev] llvm doxygen down?
On 4/19/12 7:15 PM, xiaoming gu wrote: > Hi, all. I find out that the doxygen website > (http://llvm.org/docs/doxygen) is not available now. Does anyone know > when it will be back? Thanks. It works for me. Is it working for you now? -- John T. > > Xiaoming > > > _______________________________________________ > LLVM Developers mailing list > LLVMdev at
2008 Jun 09
3
[LLVMdev] Online doxygen out of date?
Hi all, I'm having a bit of trouble with the online doxygen documentation. As far is I know, it should reflect current svn trunk. However, it seems out of date. For example, the ExtractValueInst [1] is not a UnaryInstruction yet and still takes Value* as indices. To add to the confusing, the mainpage [2] says it is documentation version "2.1svn" which seems even more weird. What
2012 Dec 28
0
[PATCH] doc: fix out-of-tree build
When building outside of the source tree, the Doxyfile needs to be generated in the build tree and should point to the proper paths for include directories and html footer. The generated api files to install should also be taken from the build tree instead of the source tree. --- configure.ac | 1 + doc/Doxyfile | 1220 --------------------------------------------------
2012 Dec 28
3
[PATCH] doc: fix out-of-tree build
When building outside of the source tree, the Doxyfile needs to be generated in the build tree and should point to the proper paths for include directories and html footer. The generated api files to install should also be taken from the build tree instead of the source tree. --- configure.ac | 1 + doc/Doxyfile | 1220 --------------------------------------------------
2008 Jun 09
0
[LLVMdev] Online doxygen out of date?
> I'm having a bit of trouble with the online doxygen documentation. As far is I > know, it should reflect current svn trunk. However, it seems out of date. For > example, the ExtractValueInst [1] is not a UnaryInstruction yet and still > takes Value* as indices. > > To add to the confusing, the mainpage [2] says it is documentation version > "2.1svn" which seems
2012 Apr 20
0
[LLVMdev] llvm doxygen down?
On 4/19/12 7:40 PM, xiaoming gu wrote: > John, it still doesn't work for me. I'm in upstate new york. And one > of my friends in bay area couldn't see the webpage either. Try http://llvm.org/doxygen. That's the link from the llvm.org main page. The docs subdirectory is probably undergoing change due to Daniel Dunbar's work. -- John T. -------------- next part
2005 Nov 15
1
[LLVMdev] doxygen docs
Chris Lattner wrote: >> I tried generating the docs myself ... doxygen simply refuses to >> create pages for classes defined in anonymous namespaces in cpp files. >> I enabled options such as EXTRACT_ALL, EXTRACT_PRIVATE and >> EXTRACT_LOCAL, but no luck. How is the publicly available >> documentation generated? > > They are generated from the Makefile in
2012 Sep 29
0
[LLVMdev] doxygen tag files
Hi there. I did a quick Google search for this topic in the mailing lists - apologies if this has popped up before. I intend to use LLVM with one of my projects and I noticed that currently the LLVM build process doesn't generate doxygen tag files. My projects all generate tag files and refer to the tag files of projects they use. I've modified a recent revision (164864) to 1. group
2013 May 10
0
[LLVMdev] Help on making doxygen document
Dear Sir or Ms: My OS is ubuntu 12.04(AMD64). I have installed TexLive 2012, Graphviz 2.26.3, doxygen 1.7.6.1 without the dependence doxygen-latex.The version of LLVM I am working on is 3.2. My configure script is the following: ../llvm-3.2/configure --prefix=/home/me/mywork/sca/llvm/llvm-install2 --enable-targets=host-only --enable-debug-runtime --enable-assertions --enable-doxygen
2017 Apr 02
2
Which doxygen doc should I look into?
Thanks for the info, Philip. I will update the LLVM Programmer’s Manual first. Regards, chenwj Wei-Ren Chen (陳韋任) Homepage: https://people.cs.nctu.edu.tw/~chenwj 2017-04-02 18:11 GMT+08:00 Philip Pfaffe <philip.pfaffe at gmail.com>: > Hi chenwj, > > http://llvm.org/doxygen/Statistic_8h_source.html is the correct one. The > other two are remnants from older doxygen deployments.
2012 Jun 11
0
CEBA-2012:0718 CentOS 5 doxygen FASTTRACK Update
CentOS Errata and Bugfix Advisory 2012:0718 Upstream details at : http://rhn.redhat.com/errata/RHBA-2012-0718.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 72c425f77c5c39f7acf6e022521cc85b76c394784e93f04188e0681251e6c592 doxygen-1.4.7-2.i386.rpm 97ea811c40a83bf5c7f30efe5394769206c61deb045b41477e0f0f3d96762a42
2010 May 08
0
[LLVMdev] docs build (doxygen redux)
Need review on new docs build. The directory layout has changed, and the changes propagate through source, build, install and possible website levels. What follows is an overview of the changes and some reasoning behind them. [patch can be found under pr6613; you will need doxygen.sh, doxygen.patch, doxygen.txt] [read: doxygen.txt for full instructions] A build diagram is also available;