similar to: Doxygen API documentation

On 10/15/06, Peter Selinger <selinger@mathstat.dal.ca> wrote: > I have converted NUT's build system to Automake/Libtool. Right now, > the new build system is contained in the "automake" branch, at: Wow... this is really nice. Thanks for taking the time to do the conversion. > drivers/Doxyfile - this seems to belong to Charles. Perhaps >

Hello nut-upsdev ! It's me again ! Since my last email about the new formalism for NUT configuration files, no objection was drawn. I propose then to make official this new formalism. Here can be find the grammar of the formalism : http://opensource.mgeups.com/projects/nut-config/grammar.od I made a parser for the new formalism and put sample files and a test program on my branch (JD-NewConf

Hi everyone, I'm new in the upsdev team, nice to meet you ! I'm currently doing an internship at MGE UPS, working with Arnaud Quette for the NUT project. I'll work for 2 months on the reworking of the configuration files for NUT and creation of libupsconfig and upsconfig libraries. (task 280 and 281 of the NUT project) My planning is as follow : Week 27 : Become used with the

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:

All, I've upgraded our doxygen to 1.5.6. Please let me know if you see any problems. Thanks, Tanya

> I'd like to support users dynamically adding and using functions > (plus structs, globals etc) to a Module, JIT compiling to an > ExecutionEngine, in an interleaved fashion. That is, declare & define > a function, run it through a FunctionPassManager, add it to an > ExecutionEngine, use it, go ahead and repeat for a different function > with the same Module,

Hi ups-dev ! I bring you some news about my work : it works ^_^ you can now try out the new configuration formalism. I modified upsd, the drivers and upsmon to use the new formalism and the new parser (via the libupsconfig library) The SVN link : svn co svn://svn.debian.org/nut/branches/JD-NewConf How to use it : To test it, I propose that you execute the following commands : Go to the

Thanks, that helps. I saw the possibility to redefine function bodies in the Kaleidoscope tutorial. What's not so clear to me yet, is how to support multiple Modules, but it's getting clearer now. Can I run a potential case past you just to be sure that it is/isn't possible? I'd like to support users dynamically adding and using functions (plus structs, globals etc) to a

John, you are right. I 'browsed' the doxygen's inheritance diagram. Shouldn't I then be able to cast Constant * to Value*? Plugging the retrieved Constant* (from ConstantExpr::getGetElementPtr) into Instruction->setOperand compiles, but gives me an assertion failure at runtime. I have no access to the code at the moment. I will gather more information possibly tomorrow.

?Hello everybody, just a few notes to the doxygen X man issue: 1/ AFAIK doxygen can generate man pages, so why don't we just generate them and decide then whether they are ill fitted or usable... 2/ I'd definitely use doxygen when possible; I mean I don't know any alternative that's able to do (at least partial) validation of the documentation with the source 3/ I

Hi All, I've compiled Qt 4.7.3 (yes, its an older version but 4.8 has a few issues) with clang + libc++. When I compile one of my resource files using Qt's moc, it reports: > ...x86_64-centos-linux-clang-libcxx/include/QtCore/QObjec:0: Warning: No relevant classes found. No output generated. I traced it to the presence of libc++ include path in the compilation: >

We need version 1.2.21 for DOxygen and I cannot find a path to that version on the website.. Can I get a link to that version so I can download and we can get this DOxygen thing done... Thank you.. David C...

# 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

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

> 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

> Both of these issues are fixed. It will be regenerated tonight. > A lot of this stuff is automated and occasionally we have snags in the > system. I appreciate you bringing it to my attention. One more that might also be regenerated(?), but I noticed today that the live demo at http://llvm.org/demo/index.cgi now returns errors if you check the "Show LLVM C++ API code" box.

Hi, since a week or so, the images generated by doxygen on llvm.org have their font size increased a bit, such that the text doesn't fit in the boxes anymore (and is overlapping and such). This makes the diagrams a bit hard to read. Any chance of fixing this? Gr. Matthijs -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type:

Hi all, > since a week or so, the images generated by doxygen on llvm.org have their > font size increased a bit, such that the text doesn't fit in the boxes anymore > (and is overlapping and such). This makes the diagrams a bit hard to read. Any > chance of fixing this? Nobody to fix this? Gr. Matthijs

>> since a week or so, the images generated by doxygen on llvm.org have their >> font size increased a bit, such that the text doesn't fit in the boxes anymore >> (and is overlapping and such). This makes the diagrams a bit hard to read. Any >> chance of fixing this? > Nobody to fix this? Unfortunately, I am the only one who can fix this :) That will happen when I

The LLVM tools are not includeed in the online Doxygen documentation. Only docs. include and lib are there. Could somone correct this if at all possible please :) Thanks, Aaron -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20090315/bd1e364d/attachment.html>