Hi

I compile new copies of Dosbox for Linux quite regularly in order to make use of any new features or add any patches that I may need for specific games. I have very few problems doing that to date. However, there is a recent set of patches that I have applied that would be useful to other people in a specific gaming community. Unfortunately most of them do not use Linux, so I need to compile a Windows copy from the same source.

This is where my problems begin as I'm unfamiliar with compiling anything I didn't write under Windows. I tried to follow the guide available at this website http://dosbox.sourceforge.net/wiki/index.php? … =BuildingDOSBox, but I ran into problems on step 5 (I didn't compile SDL on step 4 because I planned to use the Dosbox version). The problem is that under Linux, I would run the autogen.sh file to generate the files neccessary to run ./configure next. Unfortunately, things aren't so easy under Windows. I get the following output after running ./autogen.sh

--- Start of output ---

Generating build information using aclocal, autoheader, automake, autoconf
This may take a while ...

./autogen.sh: aclocal: command not found
./autogen.sh: autoheader: command not found
./autogen.sh: automake: command not found
./autogen.sh: autoconf: command not found

Now you are ready to run ./configure
You can also run ./configure --help for extra features to enable/disable.

--- End of output ---

It doesn't take much of a genius to diagnose the problem here. But resolving it is more complex. I obviously need to install an autoconf package for Windows, but which one. More to the point, how do I integrate it into the MSys environment so I can compile Dosbox? I guess I might be able to compile a Windows copy from within Linux, but I know nothing about cross-compiling presently 😀

Any ideas on this one?

Thanks