Mailing-List:	contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT sources DOT redhat DOT com>
List-Help:	<mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-owner AT sources DOT redhat DOT com
Delivered-To:	mailing list cygwin AT sources DOT redhat DOT com
Message-ID:	<2C08D4EECBDED41184BB00D0B74733420473F031@cf-bay-exch-03.cacheflow.com>
From:	"Karr, David" <david DOT karr AT cacheflow DOT com>
To:	"'cygwin AT cygwin DOT com'" <cygwin AT cygwin DOT com>
Subject:	Confusion about building dlls, g++ seems to do it right, but do I
	need "dlltool"?
Date:	Thu, 6 Sep 2001 14:26:43 -0700
MIME-Version:	1.0
X-Mailer:	Internet Mail Service (5.5.2653.19)

I'm a little confused about the process of building and using dlls in
Cygwin, as opposed to Linux.  Most of my C/C++ experience has been on
Solaris.

I have a little test application and Makefile.  It builds a "shared object",
and then links an executable which references the shared object.  This
builds and runs on Linux and Cygwin.  The only difference between the two is
some minor conditional code in the Makefile which needs to know the file
extent of "shared objects" and "executables".  Otherwise, the "g++" lines
are identical.  I let "g++" worry about the details of building a shared
library.

All I produce on Cygwin is the dll and the exe.  I don't produce a ".def",
".exp", or ".lib", which I might create with "dlltool".  The executable
referencing my dll (seemingly) has no trouble loading the dll at runtime and
using the code in the dll.

So in what circumstances would I need to use "dlltool" to build these other
things?

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

- Raw text -