Please do not reply directly to this email. All additional comments should be made in the comments box of this bug.
https://bugzilla.redhat.com/show_bug.cgi?id=513819
Erik van Pienbroek erik-fedora@vanpienbroek.nl changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |fedora-mingw@lists.fedorapr | |oject.org
--- Comment #4 from Erik van Pienbroek erik-fedora@vanpienbroek.nl 2009-07-26 12:23:05 EDT --- I don't think of this as a real bug. The Fedora-MinGW SIG has created an environment where it is possible to cross-compile packages on a Fedora Linux host for Win32 targets. Wine isn't needed to cross-compile packages. Wine is just used to test the generated binaries (but most people perform the real tests on native Win32 environments).
When using the autotools to cross-compile packages the runtime-specific tests are skipped (in some cases you need to manually create a config.cache file like mentioned at http://library.gnome.org/devel/glib/stable/glib-cross-compiling.html). The same probably also applies to other build systems (I'm not really familiar with those..) so wine isn't needed to compile mingw packages.
Wine's behaviour when executing programs which depend on other (cross-compiled) libraries is the same as would happen on real Windows environments. That is: only the default paths and the current path are searched for libraries. For example, if you copy your a.exe to /usr/i686-pc-mingw32/sys-root/mingw/bin and execute 'wine ./a.exe' the program should run just fine.
Developers/packager who wish to create win32 installers containing cross-compiled binaries are adviced to bundle all the dependent binaries in the installer and install them all in the same path. In the past there have been attempts to install GTK in a generic location (like the Gladewin32 project: http://gladewin32.sourceforge.net/) but AFAIK pidgin is the only user of it and the gladewin32 packages are outdated anyway.