pango solution

[Yaakov (Cygwin Ports)]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

d.henman wrote:
| case "$host" in
| #  *-*-mingw*|*-*-cygwin*) have_win32=true ;;      changed from this
|   *-*-mingw*) have_win32=true ;;		   <--- to this
| esac
|
| otherwise it will require win32 code to be built, and cairo was not
build for it.

This is incorrect.  have_win32 does two things:
1) adds -lgdi32 to the PangoWin32 backend LIBADD, which builds fine on
cygwin, although it's practically unused;
2) checks for the Win32 Cairo backend, and if present, specifies that
Cairo is Win32-based and hence so should be PangoCairo.  But this fails
later due to the -export-symbols-regex flag, as you found out.

By making your change, pango would fail to detect cairo-win32.

But this all really begs the question, why are you trying to build a
*Win32* GTK+ on Cygwin?


Yaakov
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Cygwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEAREIAAYFAkhhCuYACgkQpiWmPGlmQSPPJwCfZUtYojFdETMkuJJ/Uf6WfXgs
rf8AoIgNOtcSsOTNT1Q1PekgG5gmwtge
=WiLx
-----END PGP SIGNATURE-----

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/