We didn't test with C projects at all. However, we also have nearly all documentation in the .cpp files and not in the headers. Robin doesn't actually care about that at all, as long as doxygen correctly finds the documentation. Check your XML output if everything is included there. Just run doxygen as usual, if you see it in the HTML output, then it should be also present in the XML.
If the stuff is documented there, but not in robin, feel free to file a bug. Cheers Am 12.07.2012 00:47, schrieb dleach: > Yes I did try it and it basically worked. > > But I do have a question, in your announcement you indicated that your > project was a large C++ project. My project is C based and I find that > most of the docxygen strings are in my C modules instead of the header > files. But your bridge tool doesn't seem to extract from there? Am I > missing something? > > > On Sunday, July 8, 2012 3:32:25 PM UTC-5, Anteru wrote: > > Hi, > > we've added the generated files to the repository so you can run it out > of the box instead of downloading TinyXML and having to run doxygen on > it. Moreover, with a different Doxygen version than we used (1.8.1), > things might get broken. This is for the sake of simplicity, in a real > world use case you would of course generate the Doxygen XML first. > > Did the example help? Could you get it running? > > Cheers > > Am 05.07.2012 23:17, schrieb David Leach: > > A minor suggestion then. From a project perspective, you probably > wouldn't want to check in to your source archive something that is > the output of a process (like running doxygen). I would think you > would have a documentation build process that would make a doxygen > pass over your code base to generate the intermediate files before > running the make via sphinx. > > > > At least this is what I'm trying to do with a large project I have > that is using a mix of languages (C, C++, python, etc)... Hence my > interest in this tool. > > > > On Jul 5, 2012, at 1:06 PM, Anteru > <newsgro...@catchall.shelter13.net > <mailto:newsgro...@catchall.shelter13.net>> wrote: > > > >> Yes, the XML stuff is the Doxygen output. You can get it with > >> GENERATE_XML set to YES in your Doxyfile. > >> > >> Am 05.07.2012 16:47, schrieb dleach: > >>> Folks, > >>> > >>> I see that you have added a "hello world" type of example. In > the doc > >>> directory there is an XML directory that is already populated. > Where did > >>> this come from? Is this output from Doxygen that you have > decided to add > >>> to the example? > >>> > >>> > >>> > >>> On Friday, June 29, 2012 12:49:33 PM UTC-5, dleach wrote: > >>> > >>> I'm giving this a try but I'm slightly confused. I'm new to both > >>> Doxygen and Sphinx but I've been able to create content for > both. > >>> Now I'm trying to settle on using Sphinx throughout my > project and > >>> use some tool to bridge Doxygen content to the Sphinx world. > I've > >>> tried breathe and then ran across this tool. > >>> > >>> Does this tool support files section yet? > >>> > >>> It would be useful if the example included a bit more stuff like > >>> file .c/.cpp/.h stuff and some sort of simple "hello world" > type of > >>> program... maybe even start with c/cpp code as the example > with the > >>> doxygen configuration file so that the users can go end to > end on > >>> the process (run doxygen, then run your tools...). > >>> > >>> > >>> > >> > >> > > > > > -- > You received this message because you are subscribed to the Google > Groups "sphinx-dev" group. > To view this discussion on the web visit > https://groups.google.com/d/msg/sphinx-dev/-/rUgHB1m-BeMJ. > To post to this group, send email to sphinx-dev@googlegroups.com. > To unsubscribe from this group, send email to > sphinx-dev+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/sphinx-dev?hl=en. -- You received this message because you are subscribed to the Google Groups "sphinx-dev" group. To post to this group, send email to sphinx-dev@googlegroups.com. To unsubscribe from this group, send email to sphinx-dev+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/sphinx-dev?hl=en.
