Re: pango solution

[d.henman]

Yaakov (Cygwin Ports) [EMAIL PROTECTED] wrote:
 Dave Korn wrote:
 |   So, they're in the DLL itself, but for some reason not marked as exports
 | in the DEF file, and hence no available stubs for them in the import .a
 | library.
 
 It's because of the -export-symbols-regex ^pango_.* flag, hence
 _pango_* internal symbols aren't being exported.  This isn't supposed to
 be used when building a Win32 Pango, as you'll see from the configure.in
 where this flag is declared; now you know why.

Even when built with --disable-win32  it still required win32 libs be built

 ...
 I can attest that there are no issues building pango with the X11 cairo.
Your attestation is wrong for pango-1.21.3.

I found the problem.

It is in the configuration file. After making two slight changes it build fine.
It's possible that only one change was necessary, but I'm tired now and will 
leave it
to go on to build gtk+-2.12.10.

For those interesting in building pango-1.21.3, the changes necesaary where 
both of the same type simply involves deleting |*-*cygwin** from the two case 
statements.

configure file line # 20052
   line # 22054


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.


Regards,
  Henman




--
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/

Re: 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/