Upon further investigation

SDL Development
1

Ok, I was able to successfully “make”, but I had to manually edit the file
"libtool":

This:

# Compile-time system search path for libraries
sys_lib_search_path_spec="/lib /usr/lib /usr/local/lib"

Got changed to this:

# Compile-time system search path for libraries
sys_lib_search_path_spec="/usr/local/cross-tools/i386-mingw32/lib \
                          /lib /usr/lib /usr/local/lib"

It looks like it worked:

% ./playwave 
./playwave: ./playwave: cannot execute binary file

(ie, that’s a Win32 binary)

But:

  1. Why isn’t it called “playwave.exe”?
    There’s obviously something I didn’t send to “./configure” or "make"
    to let it know the target was Windows 32 binaries. (Even though
    when I ran configure, I said “–target=mingw32”!!!)

  2. OBVIOUSLY I did something wrong, or there’s a bug in the autoconf stuff,
    because manually editing “libtool” shouldn’t be necessary…

Thanks!

-bill!

2

But:

  1. Why isn’t it called “playwave.exe”?
    There’s obviously something I didn’t send to “./configure” or "make"
    to let it know the target was Windows 32 binaries. (Even though
    when I ran configure, I said “–target=mingw32”!!!)

Erm. I don’t know. Annoying isn’t it? I think that the cross-compiler
doesn’t know it needs to tack on “.exe” to the end of the output of -o.
Anyone know of a patch for this? I’m sure Muhmit has something that will
do the trick.

  1. OBVIOUSLY I did something wrong, or there’s a bug in the autoconf stuff,
    because manually editing “libtool” shouldn’t be necessary…

That’s true. I’ll check it later.
I’ll post a log of my cross-compile process so you can compare it with yours.

-Sam Lantinga				(slouken at devolution.com)

Lead Programmer, Loki Entertainment Software–
“Any sufficiently advanced bug is indistinguishable from a feature”
– Rich Kulawiec