GNOME Bugzilla – Bug 629485
pdflatex Makefile uses unix command under Windows
Last modified: 2011-01-03 19:01:12 UTC
The Makefile generated in the latex output directory for running pdflatex uses the "rm" command in the rule for the "clean" target. Under Windows, this should be "del" instead, otherwise the Makefile assumes that mingw, cygwin or something similar is installed. If the command used was "del" then the Makefile could be processed with nmake.
Yes, makes sense. Should be corrected in the next release.
This bug was previously marked ASSIGNED, which means it should be fixed in doxygen version 1.7.2. Please verify if this is indeed the case. Reopen the bug if you think it is not fixed and please include any additional information that you think can be relevant.
This seems to introduce a new problem. Here is the latex/Makefile I get on Windows: <quote> all: clean refman.pdf pdf: refman.pdf refman.pdf: refman.tex pdflatex refman.tex makeindex refman.idx pdflatex refman.tex latex_count=5 ; \ while egrep -s 'Rerun (LaTeX|to get cross-references right)' refman.log && [ $$latex_count -gt 0 ] ;\ do \ echo "Rerunning latex...." ;\ pdflatex refman.tex ;\ latex_count=`expr $$latex_count - 1` ;\ done clean: del *.ps *.dvi *.aux *.toc *.idx *.ind *.ilg *.log *.out refman.pdf </quote> As far as I tell, other parts of the makefile still assume a Cygwin environment. At least, nmake can't run this for me. I get the following: latex_count=5 ; while egrep -s 'Rerun (LaTeX|to get cross-references ri ght)' refman.log && [ $latex_count -gt 0 ] ; do echo "Rerunning latex...." ; pd flatex refman.tex ; latex_count=`expr $latex_count - 1` ; done 'latex_count' is not recognized as an internal or external command, operable program or batch file. NMAKE : fatal error U1077: 'latex_count=5' : return code '0xff' Worse, within my Cygwin environment, the shell doesn't have access to "del", so I can't run the makefile using GNU make either.
Ok, then I'll just revert the change and require the use of cygwin for latex compilation, unless someone posts a proper solution using only the crappy stuff that comes with a dos box and visual studio.
This bug was previously marked ASSIGNED, which means it should be fixed in doxygen version 1.7.3. Please verify if this is indeed the case. Reopen the bug if you think it is not fixed and please include any additional information that you think can be relevant.