Re: [Doxygen-users] Doxygen can't find dot

[Marinna L. <ma...@vi...>]

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
>
>