Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm
Sender: cygwin-owner@sourceware.cygnus.com
From: "Kevin Wright" <kwright@aspectdv.com>
To: <cygwin@sourceware.cygnus.com>
Subject: How to build static lib's
Date: Fri, 24 Sep 1999 16:27:21 -0700
Message-ID: <002801bf06e4$5aa62010$8f88f726@holstein.ASPECTDV.COM>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Importance: Normal

Hello,

I've been using cygwin for about a year and have 
always had some problems building static only 
versions of libraries such as glib and gtk+.

Here's the configure options I've tried:

./configure --disable-shared --disable-shm --disable-nls --no-recursion

However, I still end up building the .lo & subsequent .la files. 
I tried hacking the libtool files but that was useless because it gets
created during the configure process. The problem is that certain lib's
programs fail with messages such as:

gdk_imlib ERROR: Cannot load image: 
/usr/local/share/pixmaps/gnome-question.png
All fallbacks failed.

WARNING: previous dlopen of 
E:\usr\local\lib\libimlib-png.so wasn't correctly performed


Is there a way to make these libs truly static? 

I'm using gcc 2.95 and cygwin b20.1. Perhaps this is fixed in a 
newer snapshot of the cygwin1.dll but I am waiting for the 
complete installation package to be released.

TIA,

Kevin Wright
Aspect Development
Mountain View, CA 

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com