cross-configure.sh && cross-make.sh && cross-make.sh install(Note 2004-10-12: If compiling fails, try cross-configure.sh --disable-nasm)
The same steps should now work for your SDL project (perhaps you don't want to install it, though), and you will either get a binary with .exe extension or without, it seems to change every now and then... make sure the type is right:
$ file mass.exe mass.exe: MS Windows PE Intel 80386 GUI executable not relocatableThis one you'll have to strip yourself. For consistency you might want my cross-strip.sh, but this works too:
$ ls -sSh mass.exe 468K mass.exe $ /usr/local/cross-tools/bin/i386-mingw32msvc-strip mass.exe $ ls -sSh mass.exe 68K mass.exeThat's it, try it! And if you are one of the sort who can't be bothered starting Windows, tell someone else to try it. He'll have to copy SDL.dll (and others, for mass eg SDL_net.dll) into the same directory.
If you feel like being nice, zip them up into a single file.
$ cp README README.txt $ cp COPYING COPYING.txt $ unix2dos *.txt $ zip mass-0.2.6.zip mass.exe SDL.dll SDL_net.dll README.txt COPYING.txt adding: mass.exe (deflated 49%) adding: SDL.dll (deflated 58%) adding: SDL_net.dll (deflated 82%) adding: README.txt (deflated 46%) adding: COPYING.txt (deflated 62%)This should be automated somehow (a script), and I do not yet know how I would do it with binary files (bitmaps...) that have to be distributed. Something with "make install" might be a solution, or better seperate them in a data/ directory and add this to the .zip.
You can remove your build directories (the cross-compiler, and the libraries
too if you want), which was alltogether 283M huge for me.