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
To:	cygwin AT cygwin DOT com
From:	Yaakov S <yselkowitz AT netscape DOT net>
Subject:	Building DLLs from libs
Date:	Thu, 01 Jan 2004 03:59:41 -0500
Lines:	25
Message-ID:	<bt0nhu$6de$1@sea.gmane.org>
Mime-Version:	1.0
X-Complaints-To:	usenet AT sea DOT gmane DOT org
User-Agent:	Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.6b) Gecko/20031205 Thunderbird/0.4

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

OK, I googled for this one but I didn't find a clear answer, so forgive 
me if this is already "known" to the list.

I'm trying now to package some programs which include libs and includes. 
  The preferred way AFAIK is to make three packages, foo with 
executables and docs, libfooABI with just the DLL, and libfoo-devel with 
libs and includes.  The problem is, make doesn't build the dll by default.

- From my googling it appears that there are two ways to make the DLL, 
through a mkdll.sh (which some apparently opposed) or through 
re-libtoolizing.  Which is preferred and *exactly* how would I go about 
doing this?  Thanks in advance!


Yaakov
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (MingW32) - WinPT 0.7.96

iD4DBQE/8+FzpiWmPGlmQSMRAp1nAJ4271rCYTfzQPkeFhbyKrw0NMz3fACY4p7F
ip3QrmhqykecxtAfkWNGkw==
=qxNI
-----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/

- Raw text -