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=509940
Richard W.M. Jones <rjones(a)redhat.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |rjones(a)redhat.com
--- Comment #4 from Richard W.M. Jones <rjones(a)redhat.com> 2009-07-26 14:00:36 EDT ---
(In reply to comment #3)
> Actually, I'd bet that cmake does not look for i686-pc-mingw32-pkg-config (only
> pkg-config), so even fixing 513925 would not help you; you would have to hack
> something to use cross-compilation search paths (as hinted in bug 513925).
> Call it the revenge of the autotools. ;-)
No, cmake works perfectly well. We build several packages using
cmake just fine.
--
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
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
--- Comment #5 from Richard W.M. Jones <rjones(a)redhat.com> 2009-07-26 13:57:18 EDT ---
> This is a problem when running programs that use those libraries (including
> configure scripts that detect the libraries!).
We build many packages that depend on previously built packages
(several layers deep), all using autoconf, and it all works fine.
I would agree with Erik, that this is not a bug.
Also Wine should never be used when compiling packages. Any
package that needs runtime tests using Wine is clearly broken
(read the autoconf info file "6.6 Checking Runtime Behavior").
--
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
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(a)vanpienbroek.nl> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |fedora-mingw(a)lists.fedorapr
| |oject.org
--- Comment #4 from Erik van Pienbroek <erik-fedora(a)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.
--
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
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=509940
Paolo Bonzini <pbonzini(a)redhat.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |pbonzini(a)redhat.com
--- Comment #3 from Paolo Bonzini <pbonzini(a)redhat.com> 2009-07-26 10:47:55 EDT ---
You should use FindPkgConfig.cmake. However, you will hit bugs 513924 and
513925.
Actually, I'd bet that cmake does not look for i686-pc-mingw32-pkg-config (only
pkg-config), so even fixing 513925 would not help you; you would have to hack
something to use cross-compilation search paths (as hinted in bug 513925).
Call it the revenge of the autotools. ;-)
--
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.