X-Recipient:	archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status:	No, hits=-2.4 required=5.0 tests=AWL,BAYES_00,SPF_PASS
X-Spam-Check-By:	sourceware.org
Message-ID:	<49CE39BF.4010505@gmail.com>
Date:	Sat, 28 Mar 2009 14:52:47 +0000
From:	Dave Korn <dave DOT korn DOT cygwin AT googlemail DOT com>
User-Agent:	Thunderbird 2.0.0.17 (Windows/20080914)
MIME-Version:	1.0
To:	cygwin AT cygwin DOT com
Subject:	Re: gtk with win32 backend (not X11)
References:	<18894 DOT 8065 DOT 678318 DOT 725526 AT gargle DOT gargle DOT HOWL>
In-Reply-To:	<18894.8065.678318.725526@gargle.gargle.HOWL>
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com

Kasper Peeters wrote:

> Has anyone had success compiling the gtk toolkit under cygwin using
> the Win32 backend? I am getting as far as building&installing glib,
> atk and cairo (the cairo tests run fine, too). After that, the pango
> configure script does pick up that it should build for "Cairo Win32"
> and it does say "enabled shared libraries: yes", but the build process
> never creates any dlls (there is no error either though, only the
> static ".a" libraries and the ".la" files get produced & installed).
> 
> I have tried various older versions and also tried a 'libtoolize' to
> refresh the libtool scripts, but none of that made any difference.

  Most common cause of this problem is that libtool doesn't build DLLs on
Cygwin by default, because an awful lot of *nix shared objects rely on
undefined symbols that get dynamically resolved at load-time, a facility that
is not (yet![*]) supported on windows platforms.

  To tell libtool that a library won't have any unresolved references left
over after linking and so it's ok to build it as a DLL, you need to add
"-no-undefined" to the LDFLAGS used when linking the library.  This is
generally in the form of a variable named xxxxxxx_la_LTLDFLAGS somewhere in
the Makefile.in template.

    cheers,
      DaveK

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

- Raw text -