[AUCTeX-devel] ./configure output on Windows, preview-latex/gswin32c/MiKTeX

[Christian Schlauer]

Hello,

I found the time to try a snapshot from Reiner's page, here is the
output of ./configure on Windows (with Cygwin and MiKTeX). Uwe (Siart)
wrote that ./configure didn't find the texmf tree but it found the
executables, see
<URL:http://article.gmane.org/gmane.emacs.auctex.general/111> -- I
believe it has always been like this. Has there ever been something
about the texmf tree in what ./configure prints on the screen? As the
installation stuff has changed, I include the screen output of
./configure. AUCTeX works fine, I have (require 'tex-mik) in .emacs as
before and `C-c C-v' opens Yap, as expected.

,----[ $ ./configure --prefix=e:/emacs --disable-preview ]
| checking whether make sets $(MAKE)... yes
| checking for a BSD-compatible install... /usr/bin/install -c
| checking for date in ChangeLog... 2005-05-12
| checking for release in ChangeLog... not found, using 2005-05-12 instead
| checking for emacs... e:/emacs/bin/emacs
| checking if e:/emacs/bin/emacs is XEmacs... no
| checking for Emacs prefix... "e:/emacs"
| checking if Emacs is recent enough... yes
| checking for mule support... yes
| checking if build directory is valid... yes
| checking where lisp files go... e:/emacs/site-lisp
| checking what file to use for auctex startup... e:/emacs/site-lisp/auctex.el
| checking where the package lisp files go... e:/emacs/site-lisp/auctex
| checking where the data files go... e:/emacs/site-lisp/auctex
| checking where the info files go... ${prefix}/info
| checking where automatically generated global style hooks go... 
${localstatedir}
| /auctex
| checking for tex... /cygdrive/f/miktex/texmf/miktex/bin/tex
| checking for pdftex... /cygdrive/f/miktex/texmf/miktex/bin/pdftex
| checking for dvips... /cygdrive/f/miktex/texmf/miktex/bin/dvips
| checking for makeinfo... /usr/bin/makeinfo
| checking for texi2html... :
| checking for texi2dvi... /usr/bin/texi2dvi
| checking for texi2pdf... /usr/bin/texi2pdf
| checking for makeinfo... (cached) /usr/bin/makeinfo
| checking if /usr/bin/makeinfo understands @acronym{}... yes
| checking if /usr/bin/makeinfo understands @env{}... yes
| checking if /usr/bin/makeinfo understands @option{}... yes
| checking if /usr/bin/makeinfo understands @command{}... yes
| checking for install-info... /usr/bin/install-info
| configure: creating ./config.status
| config.status: creating Makefile
| config.status: creating tex-site.el.out
| config.status: creating doc/Makefile
| config.status: creating auctex.el
| 
| Congratulations!  Configuration is complete.
| 
| Type "make" at the prompt to build AUCTeX
`----

So far, so good. I have only one feature request: could ${prefix} and
${localstatedir} be replaced with their actual values, so that one can
see where the stuff goes? It was like that before.

Now, configure even preview-latex:

,----[ $ ./configure --prefix=e:/emacs ]

[ AUCTeX configuration ]

| configure: configuring in preview
| configure: running /bin/bash './configure' --prefix=e:/emacs  
'--prefix=e:/emacs
| ' --cache-file=/dev/null --srcdir=.
| checking whether make sets $(MAKE)... yes
| checking for a BSD-compatible install... /usr/bin/install -c
| checking for emacs... e:/emacs/bin/emacs
| checking if e:/emacs/bin/emacs is XEmacs... no
| checking for Emacs prefix... "e:/emacs"
| checking if Emacs is recent enough... yes
| checking if build directory is valid... yes
| checking where lisp files go... e:/emacs/site-lisp
| checking what file to use for preview startup... 
e:/emacs/site-lisp/preview-late
| x.el
| checking where the package lisp files go... e:/emacs/site-lisp/auctex
| checking where the data files go... e:/emacs/site-lisp/auctex
| checking where the info files go... ${prefix}/info
| checking for the location of AUCTeX's tex-site.el... ..
| checking for gs... no
| checking for GSWIN32C.EXE... no
| configure: error: Ghostscript not found!  Aborting!
| You need Ghostscript in your PATH for preview to work.
| configure: error: /bin/bash './configure' failed for preview
`----

Configure is looking for gswin32c.exe, but if one uses MiKTeX,
Ghostscript is already installed and in PATH: MiKTeX brings its own
Ghostscript (since at least a year or so, I believe) as Yap needs it,
but the executable is renamed so that it doesn't conflict with other
Ghostscripts on the system.

,----[ Shell output in directory `texmf/miktex/bin/' ]
| $ ls *gs*
| gsf2pk.exe  gssetgs.bat  gssetgs.exe  mgs.exe
| 
| $ mgs --help
| MiKTeX GPL Ghostscript 8.15 (2004-09-22)
| Copyright (C) 2004 artofcode LLC, Benicia, CA.  All rights reserved.
| Usage: gs [switches] [file1.ps file2.ps ...]
`----

Maybe you should check for mgs.exe, too? The MiKTeX bin/ directories
are always on the search path, as MiKTeX adds them to PATH during
installation. I checked this right now, I can call mgs.exe from my
home directory.

-- 
Christian Schlauer