Re: [Mingw-cross-env-list] Difficulty building project using mingw-cross-env

[Tony Theodore]

On 13 February 2010 05:00, David Bruce <address@hidden> wrote:
> Hi,
>
> I maintain a couple of OSS projects (tuxmath and tuxtype) and have
> been cross-building the Win32 packages on Linux using mingw32 with a
> build environment I set up by hand (built all needed libs from
> source).
>
> I'm trying to switch to mingw-cross-env as the basis of my crossbuild
> setup and have run into an obstacle.  Briefly, "./configure
> --host=i686-pc-mingw32" seems to find the crossbuild gcc OK, but
> subsequently fails at the first AC_CHECK_LIB test, saying it can't
> find SDL_image.  I don't have any build-related environmental
> variables set, and I was careful to add the
>
> Thanks for any help or suggestions.  I must be missing some step where
> I tell the build process how to locate the needed libraries.  Of note,
> in config.log, there are a lot of "undefined reference" errors
> originating from libSDL_image.a, indicating (I think) that the
> SDL_image library archive itself was found, but the linker doesn't
> know where to find the libs that SDL_image depends on.
>
> /usr/local/mingw-cross-env/usr/lib/gcc/i686-pc-mingw32/4.4.0/../../../../i686-pc-mingw32/lib/libSDL_image.a(IMG_tif.o):
> In function `IMG_InitTIF':
> /usr/local/mingw-cross-env/tmp-sdl_image/SDL_image-1.2.10/IMG_tif.c:107:
> undefined reference to `_TIFFClientOpen'
>
> Again, thanks for any suggestions,
>
> David Bruce

These lines:

SDL_CFLAGS='-I/usr/include/SDL -D_GNU_SOURCE=1 -D_REENTRANT'
SDL_CONFIG='/usr/bin/sdl-config'
SDL_LIBS='-L/usr/lib -lSDL'

should be something like:

SDL_CFLAGS='-I$PREFIX/i686-pc-mingw32/include/SDL -D_GNU_SOURCE=1
-Dmain=SDL_main'
SDL_CONFIG='$PREFIX/i686-pc-mingw32/bin/sdl-config'
SDL_LIBS='-L$PREFIX/i686-pc-mingw32/lib -lmingw32 -lSDLmain -lSDL
-lwinmm -mwindows -liconv -lm -luser32 -lgdi32 -lwinmm -ldxguid'

which is achieved by passing the
--with-sdl-prefix='$PREFIX/i686-pc-mingw32' to configure. However, it
still fails with the same error (here at least).

Regards,

Tony