similar to: [LLVMdev] doxygen docs - tools dir not included

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

On Tue, 15 Nov 2005, Sameer D. Sahasrabuddhe wrote: > The docs available on illuvium.com are different from the one's present in > the doxygen tarball on the same page ... can the tarball be generated from > the same docs as the browseable version? I considered crawling the > illuvium.com site, but it would be better to simply have a tarball available. Agreed. I have been

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;

Hi, I'm working on making llvmgcc emit line info for debugging, and found it convenient to generate doxygen docs for the whole c frontend. If anyone else finds this useful, it's up here: http://michael-mccracken.net/llvm-gcc-doxygen/ -mike

Hi, The docs available on illuvium.com are different from the one's present in the doxygen tarball on the same page ... can the tarball be generated from the same docs as the browseable version? I considered crawling the illuvium.com site, but it would be better to simply have a tarball available. I tried generating the docs myself ... doxygen simply refuses to create pages for classes

# 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

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.

Latest git [3b41451197f2cc7afb13753caaccbadaa74eca32] cross compiles perfect without patches (this is the first time I've seen this with any flac tree). Install fails with --disable-doxygen-docs; it's probably easy to fix, but here's the problem: make[5]: Entering directory `/home/avuton/src/mpd-release-utils/src/flac.git/doc/html/images/hw' make[5]: Nothing to be done for

Hi All, I am going to clean up those doxygen links on LLVM Programmer’s Manual [1], some are lost and some are too old. However, I am confused on which doxygen link I should pick up. I see there are mutiple links exist on LLVM web site for LLVM classes. Take class Statistic as example, there are: - http://llvm.org/doxygen/Statistic_8h-source.html (the oldest one, I believe it's

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

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

Hi I've tried to get doxygen documentation by configuring with --enable-doxygen. Then 'make install' has been interrupted with message "error: configuration file /media/data/virtual/share/gsoc/build/docs/doxygen.cfg not found!". mikem, why did you remove a line "AC_CONFIG_FILES([docs/doxygen.cfg])" in autoconf/configure.ac [1] ? I've restored this line. Now

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:

Hi folks, I noticed that llvm.org currently hosts two instances of the doxygen API docs, [1] and [2]. Is that intentional or by accident? What's a bit vexing about this is that googling specific APIs always ends up on [2]. However, [2] hasn't been updated for a year now and [1] would be the correct hit. But /doxygen is Disallowed through robots.txt. Best, Philip [1]

One thing that would be handy for driver developers (or for myself, at the very least) would be having some API documentation for the core NUT functions. Here is an example of Doxygen's output: http://www.ghz.cc/~clepple/libhid/doc/html/hid_8h.html The two main categories of API documentation that I see are the internal NUT functions needed for writing drivers, etc., and the external

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

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

I am using the precompiled binaries for LLVM-3.0. When I use the release documentation and download the doxygen.tar file it points to the latest version of doxygen instead of the release version. I was wondering if there was anyway I could get the doxygen output for llvm-3.0 without having to build from source. -- Bharath -------------- next part -------------- A non-text attachment was

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

At the bottom of < http://llvm.org/docs/doxygen/html/classllvm_1_1Function.html>, it says "Generated on Sat Nov 16 2013", but the hasPrefixData/getPrefixData functions don't seem to be there (I just happened to notice those being missing). Even going directly to the header source code at < http://llvm.org/docs/doxygen/html/Function_8h_source.html> doesn't seem to