Paul Eggert wrote: > As I understand it hey can either run the autotools on some other > platform and then copy the files to an MSVC host, or run the autotools > in MSVC (see <http://www.mingw.org/category/wiki/autotools>).
Basically you need a development environment and an execution environment. The execution environment is on a Windows machine and needs bash, make, gawk, grep, and similar. You have two choices: - Cygwin - MSYS I used Cygwin only, after noticing severe defects in the design of MSYS and the lack of bug-fix updates of MSYS. The development environment is where you run 'automake', 'autoreconf', and similar commands. It can be e.g. Cygwin or Linux, on the same or on a different machine. MSYS is *not* an adequate development environment. If the development environment is on a different machine than the execution environment, you need a way to transfer files. I used scp (using a Cygwin sshd); another option is a shared Samba file system. The way you work is: run the autotools in the development environment, tar up the result, transfer it to the execution environment, unpack it there, run ~/configure-msvc 2>&1 | tee log1 make 2>&1 | tee log2 make check 2>&1 | tee log3 Then you can analyze failures in details, with all the log files. In the execution environment you need a couple of environment variables set for MSVC. For MSVC 9, I used this script, to be executed through . ~/msvc.sh You find the relevant scripts attached. msvc.sh and configure-msvc must be adjusted to account for your filenames. Bruno
msvc.sh
Description: application/shellscript
configure-msvc
Description: application/shellscript
ar-lib
Description: application/shellscript
compile
Description: application/shellscript
