Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/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
From: "Ralf Habacker" <Ralf DOT Habacker AT freenet DOT de>
To: <cygwin AT cygwin DOT com>
Subject: RE: idea for mixed import/static libraries and linking with DLLs
Date: Tue, 18 Mar 2003 19:04:16 +0100
Message-ID: <006501c2ed78$ca0ca540$0a1c440a@BRAMSCHE>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400
Importance: Normal
In-Reply-To: <20030318035151.GA12616@redhat.com>

> I just realized that libc.so on linux is just a linker script and
> that it is used to link both the shared and static parts of libc.
>
> So, in a similar vein, you could conceivably do something like this
> on cygwin:
>
> /* GNU ld script
>    Use the shared library, but some functions are only in
>    the static library, so try that secondarily.  */
> GROUP ( /bin/cygwin1.dll /usr/lib/libcygwin_static.a )
>
> I just renamed my libcygwin.a to libcygwin_static.a and copied
> the above to libcygwin.a.  It worked fine.
>
> So, if I wanted, I could just produce this script, generate only
> a libcygwin_static.a and everything would work ok without any
> changes to gcc's spec file.
>
This seems to me a good way to deal with hybrid libraries libke cygwin. Isn't it
?

Ralf




--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/