Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
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
To:	cygwin AT cygwin DOT com
From:	Oliver <oliver DOT schoenborn AT utoronto DOT ca>
Subject:	questions about DLL's: .a, .def, and .dll
Date:	Fri, 27 Aug 2004 15:43:32 +0000 (UTC)
Lines:	18
Message-ID:	<loom.20040827T173827-426@post.gmane.org>
Mime-Version:	1.0
X-Complaints-To:	usenet AT sea DOT gmane DOT org
X-Gmane-NNTP-Posting-Host:	main.gmane.org
User-Agent:	Loom/3.14 (http://gmane.org/)
X-Loom-IP:	132.246.8.44 (Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0))
X-IsSubscribed:	yes

Hi folks, I'm confused about the files that dllwrap 
creates. On Unix (where I've been programming forever) all you 
have to do is create a .so shared library. But dllwrap ends up 
creating a .a file, a .def file, and a .dll file, yet I can 
build a program that links to, e.g., mylib.dll, with only "-L. -lmylib",
*wihtout* having the .def or .a available. So where and when are the .a and 
.def files needed?

Also, I read in the various docs (dllhelpers etc) that you have to 
compile the file that has DllMain using either "extern 'C'" around the 
DllMain function, or make it a C file rather than a c++ file and compile 
with gcc, yet it worked for me as a c++ file without the extern, is this 
new behavior or is something going to blow up on me later?

Thanks,
Oliver




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