X-Recipient: archive-cygwin@delorie.com X-Spam-Check-By: sourceware.org Message-ID: <48610F07.20308@users.sourceforge.net> Date: Tue, 24 Jun 2008 10:13:11 -0500 From: "Yaakov (Cygwin Ports)" User-Agent: Thunderbird 2.0.0.14 (Windows/20080421) MIME-Version: 1.0 To: cygwin@cygwin.com Subject: Re: pangp References: <20080623173202.2572@blackhawk> <004001c8d50d$0be88ca0$2708a8c0@CAM.ARTIMI.COM> <20080623212037.2088@blackhawk> <006101c8d52d$d22761a0$2708a8c0@CAM.ARTIMI.COM> <485FEED6.5000504@users.sourceforge.net> <20080624161151.2436@blackhawk> In-Reply-To: <20080624161151.2436@blackhawk> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 d.henman wrote: | Yes, Dave is right here. His idea gives a way to building a multi-capable pango. Pango is always multi-capable, but cairo (and hence PangoCairo) cannot be both Win32 and X11. Simple as that. | YO, the configuration result is: | Cairo is configured and built with: --with-x | | So is Pango, in which its configuration script upon completion outputs: | configuration: backends: Cairo Win32 FreeType X | | Note, that is has Cairo, Win32, FreeType, and Win32 as backends. Yes, so do my pango builds. The question here is solely which *cairo* you are using. | So what you probably meant, when you said "was cairo built, explicitly exluding win32"... Which is probably neceesaary right? That's the only way to build an X11 cairo on Cygwin. | Well, the YO, is wrong here.... | "pango-1.21.3" was not gotten fron SVN's trunk. | Is is a newly released version. Not a release candidate, but a public release. GNOME uses the linux-kernel versioning system; odd-numbered minor versions are *development* releases, and is hence a snapshot from trunk. ~ The fact that it's been released as a tarball is irrelevant. The release announcement for 1.21 mentions this all quite clearly. Yaakov -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (Cygwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEAREIAAYFAkhhDwcACgkQpiWmPGlmQSMYuwCg+2lfOpYWIZNODmesPmlNLS8s ZAwAn29LlIne4veaYGnoZcr8sZMdpjSK =PUK7 -----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/