Thread: [Doxygen-users] Doxygen can't find dot
Brought to you by:
dimitri
Menu
▾
▴
doxygen-users
|
From: Marinna L. <ma...@vi...> - 2006-06-07 21:02:45
|
When I run doxygen with HAVE_DOT = YES, I have issues. It says "Windows cannot find 'dot'. Make sure you typed the name correctly, and then try again. To search for a file, click the Start button, then click Search," then no matter how many times I click OK, the messsage pops back up. I have to use Task Manager to kill Doxygen to get rid of the error message. This problem happens with the wizard, Doxygen on the command line, and using Eclox (Eclipse Doxygen addon). I've just set up Doxygen in the last week, and I've been limping along without the dot graphs, but I'd really like to get dot working with Doxygen (or the other way around). I know that both dot and Doxygen work independent of each other. I've generated a few dot graphs and I've generated some basic Doxygen documentation. Both dot and Doxygen are reachable from the path. I've tried setting the DOT_PATH variable a few times (with and without quotes, backslash escapes, etc), and that doesn't seem to help. I just don't understand why Doxygen generates this error. I'm running Windows XP SP2, Graphviz 2.8 (for dot), and Doxygen 1.4.6. Also... my RTF output is screwed up. Pasted below is a sample of the output. Table of Contents Table of contents RTFDocVisitor::visitPre(DocRoot)RTFDocVisitor::visitPost(DocPara)RTFDocVisitor::visit(DocWord)VidiNavRTFDocVisitor::visit(DocWhiteSpace) RTFDocVisitor::visit(DocWord)SoftwareRTFDocVisitor::visit(DocWhiteSpace) RTFDocVisitor::visit(DocWord)DevelopmentRTFDocVisitor::visit(DocWhiteSpace) RTFDocVisitor::visit(DocWord)KitRTFDocVisitor::visit(DocWhiteSpace) RTFDocVisitor::visit(DocWord)DocumentationRTFDocVisitor::visit(DocWhiteSpace) RTFDocVisitor::visitPost(DocPara)RTFDocVisitor::visitPost(DocRoot) ~ Marinna |
|
From: Marinna L. <ma...@vi...> - 2006-06-13 00:57:12
|
I used the binary installer. I don't trust myself enough to try a source compile on Windows and not have to waste a day trying to figure out why it doesn't work, though I do most of my Linux installs via source--that isn't relevant anyway. :P When I run dot (or doxygen) from the command line, I generally go to the directory where my source files are (so where I store my *.dot or *.doxyfile) and run the program there. Yes, dot does work fine from any directory I am in. Before I generated my source files, I also tried the good ol' dot --help trick to see if I got output instead of an error, and in my "home" directory, that works quite well. Worse comes to worse, I'll just move the code base I want to document over to the Linux server and do the documentation there. ~ Marinna David Backeberg wrote: > How did you install your doxygen on Windows? Did you download separate > packages and bulid from source or did you download the monolithic > install file and run that? > > As for the unstoppable number of "dot not found" messages, one is > generated for each callgraph doxygen can't generate. The messages > probably seem interminable, but there is a finite number of them. If > you're running from the command line you might try Ctrl-C ing the app > when that starts happening. > > You say you have the PATH set up properly. So regardless of which > directory you're in at the command prompt dot is properly found? > > On 6/7/06, Marinna Lee <ma...@vi...> wrote: >> When I run doxygen with HAVE_DOT = YES, I have issues. It says >> "Windows cannot find 'dot'. Make sure you typed the name correctly, >> and then try again. To search for a file, click the Start button, >> then click Search," then no matter how many times I click OK, the >> messsage pops back up. I have to use Task Manager to kill Doxygen to >> get rid of the error message. This problem happens with the wizard, >> Doxygen on the command line, and using Eclox (Eclipse Doxygen addon). >> >> I've just set up Doxygen in the last week, and I've been limping >> along without the dot graphs, but I'd really like to get dot working >> with Doxygen (or the other way around). I know that both dot and >> Doxygen work independent of each other. I've generated a few dot >> graphs and I've generated some basic Doxygen documentation. Both dot >> and Doxygen are reachable from the path. I've tried setting the >> DOT_PATH variable a few times (with and without quotes, backslash >> escapes, etc), and that doesn't seem to help. I just don't >> understand why Doxygen generates >> this error. >> >> I'm running Windows XP SP2, Graphviz 2.8 (for dot), and Doxygen 1.4.6. >> >> >> >> Also... my RTF output is screwed up. Pasted below is a sample of the >> output. >> >> Table of Contents >> >> Table of contents >> >> RTFDocVisitor::visitPre(DocRoot)RTFDocVisitor::visitPost(DocPara)RTFDocVisitor::visit(DocWord)VidiNavRTFDocVisitor::visit(DocWhiteSpace) >> RTFDocVisitor::visit(DocWord)SoftwareRTFDocVisitor::visit(DocWhiteSpace) >> RTFDocVisitor::visit(DocWord)DevelopmentRTFDocVisitor::visit(DocWhiteSpace) >> RTFDocVisitor::visit(DocWord)KitRTFDocVisitor::visit(DocWhiteSpace) >> RTFDocVisitor::visit(DocWord)DocumentationRTFDocVisitor::visit(DocWhiteSpace) >> RTFDocVisitor::visitPost(DocPara)RTFDocVisitor::visitPost(DocRoot) >> >> ~ Marinna >> >> >> >> >> _______________________________________________ >> Doxygen-users mailing list >> Dox...@li... >> https://lists.sourceforge.net/lists/listinfo/doxygen-users >> > |
|
From: Marinna L. <ma...@vi...> - 2006-06-14 22:50:47
|
Bah. I have the basic GNU Unix tools installed on my Windows machine. I created a symbolic link to dot.exe in my C:\Winsows\System32 directory, and Windows finally found dot. (Which is really dumb.) I started to get a lot of error messages from Doxygen. Things like .eps files don't exist for all my class files (I'm generating HTML and PDF via LaTeX). Then I started getting "The parameter is incorrect." error windows. When it finally finishes, there's no dot generated images in my PDF or HTML directory. There are not .dot files in the HTML directory, but there are still .md5 files. In the PDF directory, there are both .dot and .md5 files. Ugh. ~ Marinna Marinna Lee wrote: > I used the binary installer. I don't trust myself enough to try a > source compile on Windows and not have to waste a day trying to figure > out why it doesn't work, though I do most of my Linux installs via > source--that isn't relevant anyway. :P When I run dot (or doxygen) from > the command line, I generally go to the directory where my source files > are (so where I store my *.dot or *.doxyfile) and run the program > there. Yes, dot does work fine from any directory I am in. Before I > generated my source files, I also tried the good ol' dot --help trick to > see if I got output instead of an error, and in my "home" directory, > that works quite well. > > Worse comes to worse, I'll just move the code base I want to document > over to the Linux server and do the documentation there. > > ~ Marinna > > David Backeberg wrote: > >> How did you install your doxygen on Windows? Did you download separate >> packages and bulid from source or did you download the monolithic >> install file and run that? >> >> As for the unstoppable number of "dot not found" messages, one is >> generated for each callgraph doxygen can't generate. The messages >> probably seem interminable, but there is a finite number of them. If >> you're running from the command line you might try Ctrl-C ing the app >> when that starts happening. >> >> You say you have the PATH set up properly. So regardless of which >> directory you're in at the command prompt dot is properly found? >> >> On 6/7/06, Marinna Lee <ma...@vi...> wrote: >> >>> When I run doxygen with HAVE_DOT = YES, I have issues. It says >>> "Windows cannot find 'dot'. Make sure you typed the name correctly, >>> and then try again. To search for a file, click the Start button, >>> then click Search," then no matter how many times I click OK, the >>> messsage pops back up. I have to use Task Manager to kill Doxygen to >>> get rid of the error message. This problem happens with the wizard, >>> Doxygen on the command line, and using Eclox (Eclipse Doxygen addon). >>> >>> I've just set up Doxygen in the last week, and I've been limping >>> along without the dot graphs, but I'd really like to get dot working >>> with Doxygen (or the other way around). I know that both dot and >>> Doxygen work independent of each other. I've generated a few dot >>> graphs and I've generated some basic Doxygen documentation. Both dot >>> and Doxygen are reachable from the path. I've tried setting the >>> DOT_PATH variable a few times (with and without quotes, backslash >>> escapes, etc), and that doesn't seem to help. I just don't >>> understand why Doxygen generates >>> this error. >>> >>> I'm running Windows XP SP2, Graphviz 2.8 (for dot), and Doxygen 1.4.6. >>> >>> >>> >>> Also... my RTF output is screwed up. Pasted below is a sample of the >>> output. >>> >>> Table of Contents >>> >>> Table of contents >>> >>> RTFDocVisitor::visitPre(DocRoot)RTFDocVisitor::visitPost(DocPara)RTFDocVisitor::visit(DocWord)VidiNavRTFDocVisitor::visit(DocWhiteSpace) >>> RTFDocVisitor::visit(DocWord)SoftwareRTFDocVisitor::visit(DocWhiteSpace) >>> RTFDocVisitor::visit(DocWord)DevelopmentRTFDocVisitor::visit(DocWhiteSpace) >>> RTFDocVisitor::visit(DocWord)KitRTFDocVisitor::visit(DocWhiteSpace) >>> RTFDocVisitor::visit(DocWord)DocumentationRTFDocVisitor::visit(DocWhiteSpace) >>> RTFDocVisitor::visitPost(DocPara)RTFDocVisitor::visitPost(DocRoot) >>> >>> ~ Marinna >>> >>> >>> >>> >>> _______________________________________________ >>> Doxygen-users mailing list >>> Dox...@li... >>> https://lists.sourceforge.net/lists/listinfo/doxygen-users >>> >>> > > > > > > _______________________________________________ > Doxygen-users mailing list > Dox...@li... > https://lists.sourceforge.net/lists/listinfo/doxygen-users > > |
|
From: Emil M. <mx...@se...> - 2006-06-15 07:58:29
Attachments:
smime.p7s
|
You probably didn't have set the PATH environment variable, and the installer obviously did'n set it too. There are many tools which path must be added to the PATH variable (e.g. Java Runtime Environment :), etc.), installers mostly didn't do it, although it can be done modifying win registry some way (they probably prefer not breaking user environment and leave the path modification on the user). The symbolic link into %windir%\system32 is also ok, the path %windir%\system32 is (should be) in the path. (you can see your PATH configuration running "path" from command line) The next errors, I don't have any experience with dot, but can be, that more utilities than "dot.exe" itself are needed, and the link into %windir%\system32 solves only "dot.exe", but maybe another tools (called from dot.exe) are not found. I would try to set the path to include the directory where you installed the tools (where dot.exe etc. is). (the PATH environment variable can be altered via This Computer\Properties, tab Advanced, button Environment Variables, and *append* the PATH for all users (system) or for your user only) Marinna Lee wrote: > Bah. I have the basic GNU Unix tools installed on my Windows machine. > I created a symbolic link to dot.exe in my C:\Winsows\System32 > directory, and Windows finally found dot. (Which is really dumb.) > > I started to get a lot of error messages from Doxygen. Things like .eps > files don't exist for all my class files (I'm generating HTML and PDF > via LaTeX). Then I started getting "The parameter is incorrect." error > windows. When it finally finishes, there's no dot generated images in > my PDF or HTML directory. There are not .dot files in the HTML > directory, but there are still .md5 files. In the PDF directory, there > are both .dot and .md5 files. Ugh. > > ~ Marinna > |
|
From: Marinna L. <ma...@vi...> - 2006-06-15 17:55:53
|
It is in the PATH. I checked the first time I had issues last week. It was at the end of the PATH, so I moved it to the front to give it priority. I enclosed the path in quotes, I removed the quotes. Like I said in my original post, my PATH is fine and points to the Graphviz bin directory. In fact, I have been able to run dot fine from the command line. Only Doxygen has issues. I actually have to use a script to compile the dot files that Doxygen generates because Doxygen produces them, but it doesn't manage to produce the images for some reason. ~ Marinna Lee Emil Maskovsky wrote: > > You probably didn't have set the PATH environment variable, and the > installer obviously did'n set it too. > There are many tools which path must be added to the PATH variable > (e.g. Java Runtime Environment :), etc.), installers mostly didn't do > it, although it can be done modifying win registry some way (they > probably prefer not breaking user environment and leave the path > modification on the user). > The symbolic link into %windir%\system32 is also ok, the path > %windir%\system32 is (should be) in the path. > (you can see your PATH configuration running "path" from command line) > > The next errors, I don't have any experience with dot, but can be, > that more utilities than "dot.exe" itself are needed, and the link > into %windir%\system32 solves only "dot.exe", but maybe another tools > (called from dot.exe) are not found. > > I would try to set the path to include the directory where you > installed the tools (where dot.exe etc. is). > (the PATH environment variable can be altered via This > Computer\Properties, tab Advanced, button Environment Variables, and > *append* the PATH for all users (system) or for your user only) > > > > Marinna Lee wrote: > >> Bah. I have the basic GNU Unix tools installed on my Windows machine. >> I created a symbolic link to dot.exe in my C:\Winsows\System32 >> directory, and Windows finally found dot. (Which is really dumb.) >> >> I started to get a lot of error messages from Doxygen. Things like .eps >> files don't exist for all my class files (I'm generating HTML and PDF >> via LaTeX). Then I started getting "The parameter is incorrect." error >> windows. When it finally finishes, there's no dot generated images in >> my PDF or HTML directory. There are not .dot files in the HTML >> directory, but there are still .md5 files. In the PDF directory, there >> are both .dot and .md5 files. Ugh. >> >> ~ Marinna >> > ------------------------------------------------------------------------ > > _______________________________________________ > Doxygen-users mailing list > Dox...@li... > https://lists.sourceforge.net/lists/listinfo/doxygen-users > |
|
From: Emil M. <mx...@se...> - 2006-06-16 07:29:26
Attachments:
smime.p7s
|
Then the behaviour you describe is very strange. I've just downloaded GraphViz from http://graphviz.org/Download_windows.php (version 2.8), installed and tried to generate inheritance diagrams using dot. And all is running fine. I even didn't need to update path manually, GraphViz installer does it by itself. (before I've installed the GraphViz and tried to generate the documentation, I've reached the error messages you describe, but after installed, all is running fine, I have correct inheritance diagrams) - I use Doxygen 1.4.6-NO. Marinna Lee wrote: > It is in the PATH. I checked the first time I had issues last week. > It was at the end of the PATH, so I moved it to the front to give it > priority. I enclosed the path in quotes, I removed the quotes. Like I > said in my original post, my PATH is fine and points to the Graphviz bin > directory. In fact, I have been able to run dot fine from the command > line. Only Doxygen has issues. I actually have to use a script to > compile the dot files that Doxygen generates because Doxygen produces > them, but it doesn't manage to produce the images for some reason. > > ~ Marinna Lee > |
|
From: Emil M. <mx...@se...> - 2006-06-16 15:57:26
|
One more idea ... from where do you run Doxygen? Do you run Doxygen from (Windows) command line directly or from another tool? E.g. Microsoft Visual Studio (I have version 6 installed) uses its own individual PATH processing, and changes made to the system PATH does not automatically update paths to executables inside Microsoft Visual Studio (I learned it after some similar path problems, when I tried to run some newly added tools in custom build step)... there might be some other developer environment etc., from which you can run Doxygen and which handles paths by itself ... => if you can run dot.exe from command line (without symlink in %windir%\system32 directly from path), then it would be very very strange if you then run doxygen from command line (in the same command line box) and doxygen couldn't find dot.exe ... Marinna Lee wrote: > It is in the PATH. I checked the first time I had issues last week. > It was at the end of the PATH, so I moved it to the front to give it > priority. I enclosed the path in quotes, I removed the quotes. Like I > said in my original post, my PATH is fine and points to the Graphviz bin > directory. In fact, I have been able to run dot fine from the command > line. Only Doxygen has issues. I actually have to use a script to > compile the dot files that Doxygen generates because Doxygen produces > them, but it doesn't manage to produce the images for some reason. > > ~ Marinna Lee > |
|
From: Marinna L. <ma...@vi...> - 2006-06-16 18:50:28
|
I have the most recent version of everything (Graphviz 2.8 and Doxygen 1.4.6-NO). The only thing I haven't tried is a reinstall, but I'm almost afraid to now that I've installed all this extra stuff to support my build. I was running Doxygen from Eclox, an Eclipse addon. Since I made a few of my own custom dot files, and I was having such serious issues with Doxygen finding dot properly, I decided to do some batch processing instead. Since I have a lot of GNU tools installed, I probably should have done it via a makefile or Shell script, but as this is Windows I was dumb and made a *gasp* Batch file. I regret that decision now. In any case, via the command line or via Eclipse/Eclox it does not work. Actually, for no apparent reason Ghostscript broke on me, so I can't use Imagemagick to do my .ps to .eps convert any more, so I do half of my dot compile on a remote Linux machine now any way. I will classify my documentation build environment as more complicated than my code build environment, and that's saying something for a half-assed and MacGyvered MIPS compilation environment. I think to fix it, I'd have to just move which machine I'm doing this on, but I don't have time. Deadlines suck. I really do appreciate the responses though. I have no idea what my programs are doing. Perhaps I just found a strain that's profoundly allergic to Windows, not that I blame them. PS. (SWEET! Now dot causes NTVDM.EXE to crash. This is not right.) ~ Marinna Lee Emil Maskovsky wrote: > One more idea ... from where do you run Doxygen? Do you run Doxygen from > (Windows) command line directly or from another tool? > > E.g. Microsoft Visual Studio (I have version 6 installed) uses its own > individual PATH processing, and changes made to the system PATH does not > automatically update paths to executables inside Microsoft Visual Studio > (I learned it after some similar path problems, when I tried to run some > newly added tools in custom build step)... there might be some other > developer environment etc., from which you can run Doxygen and which > handles paths by itself ... > > => if you can run dot.exe from command line (without symlink in > %windir%\system32 directly from path), then it would be very very > strange if you then run doxygen from command line (in the same command > line box) and doxygen couldn't find dot.exe ... > > > > Marinna Lee wrote: > > >> It is in the PATH. I checked the first time I had issues last week. >> It was at the end of the PATH, so I moved it to the front to give it >> priority. I enclosed the path in quotes, I removed the quotes. Like I >> said in my original post, my PATH is fine and points to the Graphviz bin >> directory. In fact, I have been able to run dot fine from the command >> line. Only Doxygen has issues. I actually have to use a script to >> compile the dot files that Doxygen generates because Doxygen produces >> them, but it doesn't manage to produce the images for some reason. >> >> ~ Marinna Lee >> >> > > > _______________________________________________ > Doxygen-users mailing list > Dox...@li... > https://lists.sourceforge.net/lists/listinfo/doxygen-users > > |
|
From: Emil M. <mx...@se...> - 2006-06-19 07:54:51
|
Marinna Lee wrote: > ... > > I was running Doxygen from Eclox, an Eclipse addon. ... I had some difficulties running external programs from Eclipse, I use it along with CDT for some of my C++ projects - Eclipse/CDT process paths by itself under some circumstances, I even had problems running e.g. nmake from Eclipse, when I made batch file for nmake (nmake.bat) and even if I insert only "nmake" command to Eclipse (build using makefile), Eclipse always looks for "nmake.exe", which was not in the path, but does not find "nmake.bat" which was on the path. It taked quite long time to figure out where the problem is :) However, if you said you tried it even from command line and it didn't work, it won't be Eclipse-only problem. > > ... > > PS. (SWEET! Now dot causes NTVDM.EXE to crash. This is not right.) > In this case, it seems your Windows installation is seriously broken, I would recommend Windows reinstallation (but, I know its is nightmare :-/ ). First I would try to reinstall GraphViz. But when you said you got more programs broken (Ghostcript), there can be problems with hard drive (bad sectors, imminent drive failure, ...), or in Windows itself (files damage), etc. |
|
From: David W. <dlw...@al...> - 2006-06-16 20:48:32
|
Friday, June 16, 2006, 2:49:54 PM, Marinna Lee wrote: > I was running Doxygen from Eclox, an Eclipse addon. Since I made a few > of my own custom dot files, and I was having such serious issues with > Doxygen finding dot properly, I decided to do some batch processing > instead. Since I have a lot of GNU tools installed, I probably should > have done it via a makefile or Shell script, but as this is Windows I > was dumb and made a *gasp* Batch file. I regret that decision now. In > any case, via the command line or via Eclipse/Eclox it does not work. > Actually, for no apparent reason Ghostscript broke on me, so I can't use > Imagemagick to do my .ps to .eps convert any more, so I do half of my > dot compile on a remote Linux machine now any way. Since you're in eclipse, why not use Ant, which is fully integrated with eclipse, and is portable, instead of a Windows batch file? -- Regards, David mailto:dlw...@al... |
|
From: Marinna L. <ma...@vi...> - 2006-06-16 21:55:46
|
Heh, I've never known what Ant was. For the initial quick hack I just wanted to run three commands, and on Windows I just thought, "Oh yeah, Batch files can do that." It just got infinitely more complicated from there. Who woulda thought? ;-) In any case, thing have been successively getting more broken on my Windows system since I installed Doxygen and dot, so I will move this over to the server. I can't work with crashing applications. It's all wonky. Not that I think Doxygen is the culprit, but most of these applications just weren't designed to work on Windows. ~ Marinna Lee David Whiteman wrote: > Friday, June 16, 2006, 2:49:54 PM, Marinna Lee wrote: > > >> I was running Doxygen from Eclox, an Eclipse addon. Since I made a few >> of my own custom dot files, and I was having such serious issues with >> Doxygen finding dot properly, I decided to do some batch processing >> instead. Since I have a lot of GNU tools installed, I probably should >> have done it via a makefile or Shell script, but as this is Windows I >> was dumb and made a *gasp* Batch file. I regret that decision now. In >> any case, via the command line or via Eclipse/Eclox it does not work. >> Actually, for no apparent reason Ghostscript broke on me, so I can't use >> Imagemagick to do my .ps to .eps convert any more, so I do half of my >> dot compile on a remote Linux machine now any way. >> > > Since you're in eclipse, why not use Ant, which is fully > integrated with eclipse, and is portable, instead of a > Windows batch file? > > |
|
From: David W. <dlw...@al...> - 2006-06-16 22:44:51
|
Friday, June 16, 2006, 5:55:18 PM, Marinna Lee wrote: > Heh, I've never known what Ant was. For the initial quick hack I just > wanted to run three commands, and on Windows I just thought, "Oh yeah, > Batch files can do that." It just got infinitely more complicated from > there. Who woulda thought? ;-) Time to learn Ant. It's an XML-based, cross-platform, build and batch file tool that is completely integrated with Eclipse and easy to use. Here's all the info you could ever want on it: http://ant.apache.org/manual/ All you do is create the build.xml file, put your commands in there, and then select Run Ant from the popup menu in Eclipse. I know this is a Doxygen list, so if you have more questions about Ant, please email me offline or ask on the Eclipse newsgroups on eclipse.org. -- Regards, David mailto:dlw...@al... |
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X