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: Re: questions about DLL's: .a, .def, and .dll
Date: Fri, 27 Aug 2004 20:36:32 +0000 (UTC)
Lines: 57
Message-ID: <loom.20040827T221407-94@post.gmane.org>
References: <loom DOT 20040827T173827-426 AT post DOT gmane DOT org> <Pine DOT GSO DOT 4 DOT 61 DOT 0408271423560 DOT 6181 AT slinky DOT cs DOT nyu DOT edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
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

Igor Pechtchanski <pechtcha <at> cs.nyu.edu> writes:

> The newer versions of gcc apparently allow you to link directly to a .dll
> file.  The .def and .a are needed for older versions of gcc, and possibly
> for some other tools.
> 
> [...]
>
> The reason you want an 'extern "C"' for DLL functions in general is that
> g++ and the Windows C++ compilers (notably VC++) use different name
> munging schemes, so a DLL built with C++ symbols won't be usable from
> other applications that try to call those functions.  The reason you want
> it for DllMain is that the Windows loader will be looking for the unmunged
> name "DllMain".  Are you sure that it's really invoked when the DLL is
> loaded?

Actually I found something quite interesting on a "Tcl extensions in Windows" 
wiki website, where a poster says that DllMain, __decl... import export, 
windows.h etc are no longer needed with g++. Sure enough, the following example 
works:

1) create a dll.h file that contains a class definition, just like you would on 
Unix (i.e. no __decl... macros, no extern etc)
2) create a dll.cc file that contains some of your class definition methods
3) then create the dll with  

   g++ -c dll.o
   g++ -shared dll.o -otestdll.dll

4) create a testMain.cc file with a main() that #includes dll.h and uses some 
things defined in dll.cc
5) build with 

   g++ -o testMain testMain.cc -L. -ltestdll

6) run testMain.exe to make sure it works

Note that extern, gcc, import/export macros and declarations, DllMain etc were 
NOT needed. Gcc seems to export everything, like it would on *nix (except, 
presumably, functions declared static and things in anonymous namespace -- 
exercise left to the reader ;). 

You can tell the linker to generate a .def file by adding "-Wl,--output-
def=testdll.def" when creating the testdll.dll. This shows all symbols 
exported. Running nm on testdll.dll also shows 

67488220 T _DllMain AT 12
67481000 T _DllMainCRTStartup AT 12

which means that gcc auto-generated it, and did not mangle for C++ use. 

Does anyone know if testdll.dll, created this way, would be linkable from a 
VC++ program? I don't have access to VC++.

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/