doxygen-users Mailing List for Doxygen (Page 56)
Brought to you by:
dimitri
You can subscribe to this list here.
2001 |
Jan
|
Feb
|
Mar
|
Apr
(1) |
May
(118) |
Jun
(150) |
Jul
(115) |
Aug
(75) |
Sep
(92) |
Oct
(102) |
Nov
(139) |
Dec
(87) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2002 |
Jan
(131) |
Feb
(60) |
Mar
(114) |
Apr
(83) |
May
(125) |
Jun
(82) |
Jul
(95) |
Aug
(98) |
Sep
(109) |
Oct
(97) |
Nov
(72) |
Dec
(70) |
2003 |
Jan
(117) |
Feb
(122) |
Mar
(187) |
Apr
(114) |
May
(154) |
Jun
(131) |
Jul
(130) |
Aug
(98) |
Sep
(121) |
Oct
(107) |
Nov
(80) |
Dec
(54) |
2004 |
Jan
(78) |
Feb
(71) |
Mar
(118) |
Apr
(56) |
May
(56) |
Jun
(64) |
Jul
(164) |
Aug
(104) |
Sep
(101) |
Oct
(69) |
Nov
(107) |
Dec
(98) |
2005 |
Jan
(75) |
Feb
(77) |
Mar
(107) |
Apr
(114) |
May
(142) |
Jun
(106) |
Jul
(79) |
Aug
(108) |
Sep
(115) |
Oct
(140) |
Nov
(128) |
Dec
(63) |
2006 |
Jan
(86) |
Feb
(71) |
Mar
(125) |
Apr
(55) |
May
(48) |
Jun
(143) |
Jul
(99) |
Aug
(91) |
Sep
(93) |
Oct
(82) |
Nov
(46) |
Dec
(45) |
2007 |
Jan
(69) |
Feb
(97) |
Mar
(125) |
Apr
(112) |
May
(65) |
Jun
(80) |
Jul
(82) |
Aug
(84) |
Sep
(56) |
Oct
(74) |
Nov
(63) |
Dec
(74) |
2008 |
Jan
(161) |
Feb
(115) |
Mar
(58) |
Apr
(73) |
May
(58) |
Jun
(79) |
Jul
(57) |
Aug
(115) |
Sep
(79) |
Oct
(62) |
Nov
(93) |
Dec
(37) |
2009 |
Jan
(69) |
Feb
(115) |
Mar
(77) |
Apr
(85) |
May
(124) |
Jun
(58) |
Jul
(44) |
Aug
(85) |
Sep
(90) |
Oct
(80) |
Nov
(87) |
Dec
(48) |
2010 |
Jan
(52) |
Feb
(71) |
Mar
(54) |
Apr
(37) |
May
(66) |
Jun
(86) |
Jul
(84) |
Aug
(68) |
Sep
(94) |
Oct
(66) |
Nov
(36) |
Dec
(53) |
2011 |
Jan
(59) |
Feb
(77) |
Mar
(59) |
Apr
(67) |
May
(76) |
Jun
(54) |
Jul
(95) |
Aug
(92) |
Sep
(84) |
Oct
(72) |
Nov
(46) |
Dec
(60) |
2012 |
Jan
(43) |
Feb
(77) |
Mar
(88) |
Apr
(121) |
May
(81) |
Jun
(69) |
Jul
(97) |
Aug
(64) |
Sep
(55) |
Oct
(55) |
Nov
(38) |
Dec
(60) |
2013 |
Jan
(85) |
Feb
(70) |
Mar
(81) |
Apr
(83) |
May
(51) |
Jun
(65) |
Jul
(71) |
Aug
(39) |
Sep
(47) |
Oct
(32) |
Nov
(43) |
Dec
(28) |
2014 |
Jan
(64) |
Feb
(22) |
Mar
(54) |
Apr
(20) |
May
(59) |
Jun
(20) |
Jul
(50) |
Aug
(17) |
Sep
(37) |
Oct
(56) |
Nov
(40) |
Dec
(24) |
2015 |
Jan
(51) |
Feb
(29) |
Mar
(57) |
Apr
(31) |
May
(23) |
Jun
(50) |
Jul
(30) |
Aug
(66) |
Sep
(59) |
Oct
(21) |
Nov
(29) |
Dec
(12) |
2016 |
Jan
(33) |
Feb
(30) |
Mar
(19) |
Apr
(23) |
May
(16) |
Jun
(31) |
Jul
(17) |
Aug
(19) |
Sep
(21) |
Oct
(20) |
Nov
(15) |
Dec
(6) |
2017 |
Jan
(16) |
Feb
(13) |
Mar
(16) |
Apr
(23) |
May
(16) |
Jun
(5) |
Jul
(14) |
Aug
(13) |
Sep
(12) |
Oct
(11) |
Nov
(3) |
Dec
(6) |
2018 |
Jan
(4) |
Feb
(6) |
Mar
(5) |
Apr
(11) |
May
(26) |
Jun
(5) |
Jul
(10) |
Aug
(7) |
Sep
(3) |
Oct
|
Nov
(3) |
Dec
(7) |
2019 |
Jan
(17) |
Feb
(18) |
Mar
(5) |
Apr
(6) |
May
(3) |
Jun
|
Jul
(9) |
Aug
(19) |
Sep
(3) |
Oct
(1) |
Nov
(23) |
Dec
(5) |
2020 |
Jan
(7) |
Feb
(1) |
Mar
(7) |
Apr
(11) |
May
(8) |
Jun
(7) |
Jul
(10) |
Aug
(3) |
Sep
(4) |
Oct
(7) |
Nov
(6) |
Dec
|
2021 |
Jan
(3) |
Feb
|
Mar
(4) |
Apr
(4) |
May
|
Jun
|
Jul
(1) |
Aug
(3) |
Sep
|
Oct
|
Nov
(8) |
Dec
(3) |
2022 |
Jan
(2) |
Feb
|
Mar
(1) |
Apr
|
May
(3) |
Jun
(1) |
Jul
|
Aug
(3) |
Sep
(9) |
Oct
(2) |
Nov
|
Dec
(2) |
2023 |
Jan
(2) |
Feb
(5) |
Mar
(3) |
Apr
(7) |
May
(6) |
Jun
(2) |
Jul
(5) |
Aug
|
Sep
(4) |
Oct
(1) |
Nov
(5) |
Dec
(5) |
2024 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(3) |
Jun
(4) |
Jul
|
Aug
(3) |
Sep
|
Oct
|
Nov
(1) |
Dec
|
From: Jeffrey M. <jme...@mi...> - 2014-08-28 20:30:56
|
Dimitri, On 8/28/2014 2:03 PM, Dimitri van Heesch wrote: > Hi Jeffrey, > > On 27 Aug 2014, at 17:59 , Jeffrey Melville <jme...@mi...> wrote: > >> All, >> >> I'm working on two closely related source trees that generate Doxygen >> separately. To cross-link the Doxygen HTML, we just started using >> GENERATE_TAGFILE and TAGFILES for ProjectA and Project B respectively. >> >> I noticed that some functions are missing from the tag file in 1.8.6, >> 1.8.8, and the current git head. The tag file is complete when I >> generate it with 1.8.2. The was a similar thread >> (http://doxygen.10944.n7.nabble.com/Tag-files-and-linking-to-variables-td5788.html) >> that referenced this bug: >> (https://bugzilla.gnome.org/show_bug.cgi?id=694376). The bug was >> supposed to be fixed in 1.8.4 but I am still seeing my issue. >> >> It seems to involve hierarchies similar to the one below. In the actual >> codebase, all members are documented but I ommitted the documentation >> here for brevity. >> >> The tag file only includes private members of class A (i.e. foo is not >> listed). In one case, >> the tag file for a B-style class even includes the function ~A(). >> >> This is problematic because the ProjectB documentation for class C does >> not properly link to the overridden function in ProjectA. >> >> If I generate the tag file for ProjectA using Doxygen 1.8.2, then build >> the Doxygen for ProjectB with Doxygen 1.8.6 using that tag file, >> everything is fine. We have some compatibility issues with the rest of >> the Doxyfile with 1.8.2. >> >> Unfortunately, I haven't been able to replicate the problem with a >> simple test case like this one. It only occurs with the full codebase, >> which I am unable to provide. >> >> Is this enough for anyone to have an idea? I'm not opposed to hacking on >> the Doxygen source code to find a patch but I could use a tip on where >> to start looking. > > I'm afraid it is not enough to directly pinpoint the problem. > Some questions: > - does the issue occur with just one tag file, and one project using it, or is there > a chain of tag files, where also projectA imports tag files? No, ProjectA does not import any tag files. It does declare BUILTIN_STL_SUPPORT. ProjectB is the only consumer of ProjectA's tag file. It only imports the single tag file. > - is a symbol with the same name as the one that is not correctly appearing > in projectA's tag file (i.e. foo), also in some other tag file? No, since project A does not import any other tag flies. I don't know if this matters, but another source file forward declares one of the affected classes. > > If you want to see places in the code where information is written to the tag file, > look for "Doxygen::tagFile" in the source code. For member information look in > src/memberdef.cpp Ok. I'll poke around. Have there been any significant changes since 1.8.2 in the way tag files are generated? > > Regards, > Dimitri > Thanks, Jeff P.S. Sorry for the double send, I forgot to include the list. >> >> Cheers, >> Jeff >> >> >> // Class A and B are in ProjectA >> class A >> { >> public: >> virtual ~A() {} >> virtual void foo() {} >> protected: >> A() {} >> private: >> int a_private; >> }; >> >> class B : public A >> { >> public: >> virtual ~B() {} >> virtual void bar() = 0; >> protected: >> B() {} >> private: >> int b_private; >> }; >> >> // Class C is in ProjectB >> class C : public B >> { >> public: >> void foo() { /* Do something */ } >> void bar() { /* Do something */ } >> }; >> >> ------------------------------------------------------------------------------ >> Slashdot TV. >> Video for Nerds. Stuff that matters. >> http://tv.slashdot.org/ >> _______________________________________________ >> Doxygen-users mailing list >> Dox...@li... >> https://lists.sourceforge.net/lists/listinfo/doxygen-users > |
From: Dimitri v. H. <do...@gm...> - 2014-08-28 18:04:09
|
Hi Jeffrey, On 27 Aug 2014, at 17:59 , Jeffrey Melville <jme...@mi...> wrote: > All, > > I'm working on two closely related source trees that generate Doxygen > separately. To cross-link the Doxygen HTML, we just started using > GENERATE_TAGFILE and TAGFILES for ProjectA and Project B respectively. > > I noticed that some functions are missing from the tag file in 1.8.6, > 1.8.8, and the current git head. The tag file is complete when I > generate it with 1.8.2. The was a similar thread > (http://doxygen.10944.n7.nabble.com/Tag-files-and-linking-to-variables-td5788.html) > that referenced this bug: > (https://bugzilla.gnome.org/show_bug.cgi?id=694376). The bug was > supposed to be fixed in 1.8.4 but I am still seeing my issue. > > It seems to involve hierarchies similar to the one below. In the actual > codebase, all members are documented but I ommitted the documentation > here for brevity. > > The tag file only includes private members of class A (i.e. foo is not > listed). In one case, > the tag file for a B-style class even includes the function ~A(). > > This is problematic because the ProjectB documentation for class C does > not properly link to the overridden function in ProjectA. > > If I generate the tag file for ProjectA using Doxygen 1.8.2, then build > the Doxygen for ProjectB with Doxygen 1.8.6 using that tag file, > everything is fine. We have some compatibility issues with the rest of > the Doxyfile with 1.8.2. > > Unfortunately, I haven't been able to replicate the problem with a > simple test case like this one. It only occurs with the full codebase, > which I am unable to provide. > > Is this enough for anyone to have an idea? I'm not opposed to hacking on > the Doxygen source code to find a patch but I could use a tip on where > to start looking. I'm afraid it is not enough to directly pinpoint the problem. Some questions: - does the issue occur with just one tag file, and one project using it, or is there a chain of tag files, where also projectA imports tag files? - is a symbol with the same name as the one that is not correctly appearing in projectA's tag file (i.e. foo), also in some other tag file? If you want to see places in the code where information is written to the tag file, look for "Doxygen::tagFile" in the source code. For member information look in src/memberdef.cpp Regards, Dimitri > > Cheers, > Jeff > > > // Class A and B are in ProjectA > class A > { > public: > virtual ~A() {} > virtual void foo() {} > protected: > A() {} > private: > int a_private; > }; > > class B : public A > { > public: > virtual ~B() {} > virtual void bar() = 0; > protected: > B() {} > private: > int b_private; > }; > > // Class C is in ProjectB > class C : public B > { > public: > void foo() { /* Do something */ } > void bar() { /* Do something */ } > }; > > ------------------------------------------------------------------------------ > Slashdot TV. > Video for Nerds. Stuff that matters. > http://tv.slashdot.org/ > _______________________________________________ > Doxygen-users mailing list > Dox...@li... > https://lists.sourceforge.net/lists/listinfo/doxygen-users |
From: Jeffrey M. <jme...@mi...> - 2014-08-27 15:59:56
|
All, I'm working on two closely related source trees that generate Doxygen separately. To cross-link the Doxygen HTML, we just started using GENERATE_TAGFILE and TAGFILES for ProjectA and Project B respectively. I noticed that some functions are missing from the tag file in 1.8.6, 1.8.8, and the current git head. The tag file is complete when I generate it with 1.8.2. The was a similar thread (http://doxygen.10944.n7.nabble.com/Tag-files-and-linking-to-variables-td5788.html) that referenced this bug: (https://bugzilla.gnome.org/show_bug.cgi?id=694376). The bug was supposed to be fixed in 1.8.4 but I am still seeing my issue. It seems to involve hierarchies similar to the one below. In the actual codebase, all members are documented but I ommitted the documentation here for brevity. The tag file only includes private members of class A (i.e. foo is not listed). In one case, the tag file for a B-style class even includes the function ~A(). This is problematic because the ProjectB documentation for class C does not properly link to the overridden function in ProjectA. If I generate the tag file for ProjectA using Doxygen 1.8.2, then build the Doxygen for ProjectB with Doxygen 1.8.6 using that tag file, everything is fine. We have some compatibility issues with the rest of the Doxyfile with 1.8.2. Unfortunately, I haven't been able to replicate the problem with a simple test case like this one. It only occurs with the full codebase, which I am unable to provide. Is this enough for anyone to have an idea? I'm not opposed to hacking on the Doxygen source code to find a patch but I could use a tip on where to start looking. Cheers, Jeff // Class A and B are in ProjectA class A { public: virtual ~A() {} virtual void foo() {} protected: A() {} private: int a_private; }; class B : public A { public: virtual ~B() {} virtual void bar() = 0; protected: B() {} private: int b_private; }; // Class C is in ProjectB class C : public B { public: void foo() { /* Do something */ } void bar() { /* Do something */ } }; |
From: Kevin N. <kne...@si...> - 2014-08-24 22:14:17
|
Hello Dimitri. I am working on a project that the C++ API of Doxygen is coming in very handy. I started by looking at the DoxyApp project and by running Doxygen on itself. This has allowed me to get to a proof of concept state, but to get to the next stage, I am going to need more details. I have noticed that quite a bit of Doxygen itself isn't documented, or it is out of date. I wanted to find out if you have any supporting documentation that can help me better understand the API. Thanks, Kevin |
From: Bosler, P. A. <pa...@sa...> - 2014-08-15 18:08:54
|
Good morning, I'm a new Doxygen user trying to use the bibtex citation feature from Fortran source code with DoxyWizard and doxygen 1.8.7 on Mac OS X 10.9.4. I have a proper .bib file in my source directory and the html output from Doxygen includes a bibliography page, but it is empty. I have the following in a Fortran source file : !> Provides and object-oriented interface into the stripack.f module @cite STRIPACK with a corresponding entry in my .bib file of @article{STRIPACK, author="R. Renka", title="{Algorithm 772: STRIPACK : Delaunay triangulation and Voronoi diagram on the surface of a sphere}", journal="ACM Transactions on Mathematical Software", volume="23", year="1997", pages="416-434" }. I get the following output from doxygen: Generating citations page... error opening bib8262.bbl: No such file or directory bibtex command failed: No such file or directory which leads me to believe that bibtex is not in the Doxygen search path, but I am not sure how to edit this parameter. The location is /usr/texbin/bibtex, same as the latex path. Thanks for your time. Pete |
From: Chris1234 <chr...@ma...> - 2014-08-14 19:04:23
|
How can I get a legend into the LaTeX files. I convert the LaTeX file to a PDF file. Thank you, -- View this message in context: http://doxygen.10944.n7.nabble.com/How-can-I-get-a-legend-into-LaTeX-tp6770.html Sent from the Doxygen - Users mailing list archive at Nabble.com. |
From: Chris1234 <chr...@ma...> - 2014-08-14 18:55:02
|
I have many functions in my source code. I noticed that some of these are given call and caller graphs while others get none. Why is that? Can you tell me how I can make all routines get at least a call graph. -- View this message in context: http://doxygen.10944.n7.nabble.com/Why-are-some-functions-not-getting-any-graphs-call-caller-etc-tp6769.html Sent from the Doxygen - Users mailing list archive at Nabble.com. |
From: Mike Y. <ne...@fo...> - 2014-08-11 10:35:14
|
Just repeating my request to anyone who knows what work may have been done already in this field. Hopefully Mike Yates |
From: André G. <and...@bi...> - 2014-08-11 10:00:40
|
Hello Chris1234, your problem is a missing package -- xcolor.sty <http://www.ctan.org/pkg/xcolor> -- all you need to do is install it and then "run the makefile" again. In fact, MiKteX should have displayed a dialogue requesting your permission for installing the missing package ( see here <http://docs.miktex.org/2.9/manual/autoinstall.html> ), so you probably can adjust some MiKteX settings to have that behaviour. Best regards, André On 06-08-2014 16:15, Chris1234 wrote: > Briefly: > > With administrator privaleges, I installed MikTex on my computer, but when I > ran Doxygen on Java source code, I do not get a refman.pdf file! That's my > main problem. > > My question is how do I create a PDF version of my HTML files. What am I > doing wrong. > > Details: > > I mentioned refman.pdf above because, I guess, that file is what I should be > looking for. > > I do have the "pdflatex" command installed. I know this because I ran > "pdflatex -help" and this gave me output. > > Again, I want to create a PDF version of my Doxygen HTML files. The HTML > looks fine, but I'd like to get a PDF version. > > I looked on the Internet and this led me to believe that I should run the > makefile in the latex folder. > > (1) When I run the Makefile, I get the following error: > > LaTeX Error: File 'xcolor.sty' not found. > > Type X to quit or (RETURN) to proceed, or enter new name (Default extension: > sty) > > Enter file name: > ... > > (2) I tried setting the following two commands to "NO" in the configuration > file, but that solved nothing. > > CALL_GRAPH > CALLER_GRAPH > > (3) I tried to install MikTex in a different location but that did not help. > > Does anyone have any ideas. > > Thank you, > > > > > > > -- > View this message in context: http://doxygen.10944.n7.nabble.com/Running-make-in-latex-folder-yields-tex-latex-xcolor-xcolor-sty-is-missing-tp6761.html > Sent from the Doxygen - Users mailing list archive at Nabble.com. > > ------------------------------------------------------------------------------ > Infragistics Professional > Build stunning WinForms apps today! > Reboot your WinForms applications with our WinForms controls. > Build a bridge from your legacy apps to the future. > http://pubads.g.doubleclick.net/gampad/clk?id=153845071&iu=/4140/ostg.clktrk > _______________________________________________ > Doxygen-users mailing list > Dox...@li... > https://lists.sourceforge.net/lists/listinfo/doxygen-users -- *André Glória* Embedded Systems Developer ------------------------------------------------------------------------ *Bithium ® S.A.* • Av. Miguel Bombarda, 129 R/C • 1050-154 Lisboa • Portugal *Phone* +351 21 3304224 • *Fax* +351 21 3304225 • *Web* http://www.bithium.com • *Skype* /bithium_agloria/ ------------------------------------------------------------------------ |
From: Chris1234 <chr...@ma...> - 2014-08-08 14:48:50
|
Does the Doxygen license have any restrictions in its use etc. Thanks -- View this message in context: http://doxygen.10944.n7.nabble.com/Doxygen-License-Restrictions-tp6762.html Sent from the Doxygen - Users mailing list archive at Nabble.com. |
From: Chris1234 <chr...@ma...> - 2014-08-06 15:15:28
|
Briefly: With administrator privaleges, I installed MikTex on my computer, but when I ran Doxygen on Java source code, I do not get a refman.pdf file! That's my main problem. My question is how do I create a PDF version of my HTML files. What am I doing wrong. Details: I mentioned refman.pdf above because, I guess, that file is what I should be looking for. I do have the "pdflatex" command installed. I know this because I ran "pdflatex -help" and this gave me output. Again, I want to create a PDF version of my Doxygen HTML files. The HTML looks fine, but I'd like to get a PDF version. I looked on the Internet and this led me to believe that I should run the makefile in the latex folder. (1) When I run the Makefile, I get the following error: LaTeX Error: File 'xcolor.sty' not found. Type X to quit or (RETURN) to proceed, or enter new name (Default extension: sty) Enter file name: ... (2) I tried setting the following two commands to "NO" in the configuration file, but that solved nothing. CALL_GRAPH CALLER_GRAPH (3) I tried to install MikTex in a different location but that did not help. Does anyone have any ideas. Thank you, -- View this message in context: http://doxygen.10944.n7.nabble.com/Running-make-in-latex-folder-yields-tex-latex-xcolor-xcolor-sty-is-missing-tp6761.html Sent from the Doxygen - Users mailing list archive at Nabble.com. |
From: Tom U. <to...@io...> - 2014-08-06 13:36:47
|
Hi Dimitri, >> I am using doxygen 1.8.7 to document our embedded firmware repository. >> There are a number of individual projects there each with its own main >> function. > > In that case I typically suggest to do a doxygen run for each project separately. I really having it all together in one place. I set up a decent amount of related pages that steer the user through it all and it is nice to have the overview of all the projects - particularly since many of them are master-slave type devices that share protocol files and in general go together. I tried messing with tags somewhat but that did not work out very well for me. > >> >> How do I \ref a specific one? Obviously simply using \ref main picks >> the first one doxygen finds. I tried something like >> >> \ref deviceA_main.c#main >> >> but that did not work. >> >> Is there a way to do this? >> > > No there is not. Wouldn't work correctly with automatic links. That is a shame. It seems like it might be possible to make some assumptions that would allow automatic link creation in most cases. For example a prime one would be that void foo(); in \dir\bar.h goes with the void foo(){} in \dir\bar.c not the one in \dir2\bar.c. Obviously there are plenty of ways for that to fall apart, but it is not a bad assumption. A somewhat workable solution to this that does not require much trickery is: #ifdef DOXY_BUILD #define main this_particular_project_main #endif void main() { } Then of course you define DOXY_BUILD in doxygen. This way you can at least \ref to a particular main from your related pages to get the reader to the root of it all easily. I would not want to do it if I had a significant pattern that involved like-named static functions for example, but it works ok for this. All the best, Tom PS I am noticing that my posts to doxygen-users are no longer being echoed back to my email. My earlier ones were. Now I only see the replies. Is there some setting for that in my account? |
From: Dimitri v. H. <do...@gm...> - 2014-08-05 11:23:18
|
Hi Susanne, On 05 Aug 2014, at 12:50 , <Sus...@dl...> <Sus...@dl...> wrote: > Is there a documentation of the doxygen special command “msc” ? > > I found some examples but no documentation/tutorial/… that describes what that keywords (“g”, “box”,…) are standing for and if there are restriction in use. You are probably looking for this: http://www.mcternan.me.uk/mscgen/ Regards, Dimitri |
From: <Sus...@dl...> - 2014-08-05 10:50:47
|
Is there a documentation of the doxygen special command "msc" ? I found some examples but no documentation/tutorial/... that describes what that keywords ("g", "box",...) are standing for and if there are restriction in use. |
From: Chris1234 <chr...@ma...> - 2014-08-01 19:44:15
|
Here is some additional information. I compared the system messages from both cases. Case one put the /mainpage directly in a java file, and case two put the /mainpage in a mainpage.dox file. Case two : (1) didn't read the java files. (2) didn't parse the java files. (3) didn't have messages stating "Generating docs for". (4) didn't have messages stating "Running dot for graph". (5) didn't have messages stating "Patching output file". (6) At the very end, had output such as, lookup cache used 0/... hits=0 misses=0. Thank you, -- View this message in context: http://doxygen.10944.n7.nabble.com/ref-in-mainpage-dox-not-working-tp6756p6757.html Sent from the Doxygen - Users mailing list archive at Nabble.com. |
From: Pradyumna P. <pra...@gm...> - 2014-08-01 07:15:10
|
Hi All, I started using Doxygen-1.8.7. I noticed call graphs are missing when the called function is located deeper in a file. In the below example, the call graph for function1() is absent. Is there any dependency on the parsing level? void function1(int cmd, int arg) { int ret = 0; switch (cmd) { case 1: if(arg == 10) { ret = function2(); } break; case 2: if(arg == 10) { ret = function3(); } break; case 3: if(arg == 10) { ret = function4(); } break; default: ret = function5(); break; } return; } Thanks, Pradyumna |
From: Tom G. <ger...@gm...> - 2014-07-30 10:47:30
|
Hi, We have almost completed our Doxygen project for our 1 MLOC archive (and are very happy with the result!!!), but unfortunately members of structs in our archive are not linked. We submitted a PR for this ( https://bugzilla.gnome.org/show_bug.cgi?id=733968), but we were wondering if there is any known workaround to this problem. A short recap of the problem: *This bug is a continuation of bug 333931 <show_bug.cgi?id=333931> ( support for smart pointers (dereference operator in template) ) which was fixed earlier. Doxygen appears to understand dereference operators (->) in a templatised smart pointer class only if the smart pointer instance is a local variable in the file and not when the smartpointer is defined as a global variable in another file.* Best regards, Tom & Sankar |
From: Petr P. <Pr...@sk...> - 2014-07-29 08:26:10
|
Hi, If interested, you can download the doxygen binaries compiled for MS Windows from http://sourceforge.net/projects/doxygen/files/snapshots/doxygen-1.8-svn/windows This is the place where you should find also the next releases. Name of the archive file is doxygenw20140729_1_8_7.zip The related translator report can be found inside the directory http://sourceforge.net/projects/doxygen/files/snapshots/doxygen-1.8-svn/translator_reports/ Name of the archive file is tr20140729_1_8_7.zip The binaries are NOT created automatically, so it may happen that some newer sources were not compiled because I am not present to do that or I forgot... ;) Regards, Petr -- Petr Prikryl (prikryl at atlas dot cz) |
From: <vic...@gm...> - 2014-07-28 14:42:15
|
Hi All, Is it possible to preserve formatting of Doxygen comments without enclosing the content in \verbatim \endverbatim when generating XML output? I want to format the comments using Sphinx <http://sphinx-doc.org/>/reStructuredText <http://docutils.sourceforge.net/rst.html> via Breathe <https://github.com/michaeljones/breathe>, a reStructuredText and Sphinx bridge to Doxygen, but using \verbatim (or its equivalent) all the time is not very convenient. Best regards, Victor |
From: Tom U. <to...@io...> - 2014-07-24 19:54:33
|
Hi Dimitri, >> >> I am using doxygen 1.8.7 to document our embedded firmware repository. >> There are a number of individual projects there each with its own main >> function. > > In that case I typically suggest to do a doxygen run for each project separately. I see. Is there a nice way to tie them all together into one website that does not require significant outside HTML coding? >> How do I \ref a specific one? Obviously simply using \ref main picks >> the first one doxygen finds. I tried something like >> >> \ref deviceA_main.c#main >> >> but that did not work. >> >> Is there a way to do this? >> > > No there is not. Wouldn't work correctly with automatic links. That is too bad. All the best, Tom |
From: Dimitri v. H. <do...@gm...> - 2014-07-24 18:40:12
|
Hi Tom, On 23 Jul 2014, at 18:12 , Tom Udale <to...@io...> wrote: > Hi All, > > I am using doxygen 1.8.7 to document our embedded firmware repository. > There are a number of individual projects there each with its own main > function. In that case I typically suggest to do a doxygen run for each project separately. > > How do I \ref a specific one? Obviously simply using \ref main picks > the first one doxygen finds. I tried something like > > \ref deviceA_main.c#main > > but that did not work. > > Is there a way to do this? > No there is not. Wouldn't work correctly with automatic links. Regards, Dimitri |
From: Russell E. O. <ro...@uw...> - 2014-07-24 18:10:11
|
We have a complex project build of many packages. We use a common Doxygen config for all of them. We would like to put the detailed description at the top, which needs a layout file (alas), and I'd like a single file that is used for all of these packages. The path to each package is set by environment variables, and so is not necessarily fixed. Any suggestion for how to make this work? So far nothing I have tried works. The include path is apparently not used to search for the layout file, and I don't see any other path variable that would work, instead. -- Russell |
From: Mike Y. <ne...@fo...> - 2014-07-23 18:44:30
|
Hi Guys It would be great to document MV source code automatically. I've used Doxygen for C++ but only just thought of applying it to DataBasic. What work has been done on this? Mike Y |
From: Tom U. <to...@io...> - 2014-07-23 17:04:31
|
Damon, > For C++, we use the class name > > \ref myClassName::foo() Right, I do that too for C++. Do you know a way for C? I can only think of the filename as a differentiating element there but I cannot find a way to tell doxygen that. Cheers, Tom > > - Damon > > Inactive hide details for Tom Udale ---07/23/2014 12:39:25 PM---Hi All, > I am using doxygen 1.8.7 to document our embedded firmwTom Udale > ---07/23/2014 12:39:25 PM---Hi All, I am using doxygen 1.8.7 to document > our embedded firmware repository. > > > From: > > > Tom Udale <to...@io...> > > To: > > > dox...@li..., > > Date: > > > 07/23/2014 12:39 PM > > Subject: > > > [Doxygen-users] Multiple functions with same name-how to reference? > > ------------------------------------------------------------------------ > > > > Hi All, > > I am using doxygen 1.8.7 to document our embedded firmware repository. > There are a number of individual projects there each with its own main > function. > > How do I \ref a specific one? Obviously simply using \ref main picks > the first one doxygen finds. I tried something like > > \ref deviceA_main.c#main > > but that did not work. > > Is there a way to do this? > > > > Indeed I notice that doxygen in general gets a little confused here. > Does it not have some level of locality when dealing with multiple > programs in different directories? That is, a way to notice that > > void foo(); in \devicea\file1.h goes with the void foo(){} in > \devicea\file1.c not the one in in \deviceb\file1.c? > > > > All the best, > > Tom > > > > ------------------------------------------------------------------------------ > Want fast and easy access to all the code in your enterprise? Index and > search up to 200,000 lines of code with a free copy of Black Duck > Code Sight - the same software that powers the world's largest code > search on Ohloh, the Black Duck Open Hub! Try it now. > http://p.sf.net/sfu/bds > _______________________________________________ > Doxygen-users mailing list > Dox...@li... > https://lists.sourceforge.net/lists/listinfo/doxygen-users > > |
From: Tom U. <to...@io...> - 2014-07-23 16:38:48
|
Hi All, I am using doxygen 1.8.7 to document our embedded firmware repository. There are a number of individual projects there each with its own main function. How do I \ref a specific one? Obviously simply using \ref main picks the first one doxygen finds. I tried something like \ref deviceA_main.c#main but that did not work. Is there a way to do this? Indeed I notice that doxygen in general gets a little confused here. Does it not have some level of locality when dealing with multiple programs in different directories? That is, a way to notice that void foo(); in \devicea\file1.h goes with the void foo(){} in \devicea\file1.c not the one in in \deviceb\file1.c? All the best, Tom |