Mailing-List:	contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
Sender:	cygwin-owner AT sourceware DOT cygnus DOT com
Delivered-To:	mailing list cygwin AT sourceware DOT cygnus DOT com
Message-Id:	<199904141343.IAA10862@modi.xraylith.wisc.edu>
X-Authentication-Warning:	modi.xraylith.wisc.edu: localhost.xraylith.wisc.edu [127.0.0.1] didn't use HELO protocol
To:	"Joost Kraaijeveld" <JKraaijeveld AT askesis DOT nl>
cc:	"Cygwin AT Sourceware. Cygnus. Com" <cygwin AT sourceware DOT cygnus DOT com>
Subject:	Re: Problem with DllWrap tool
In-reply-to:	Your message of "Wed, 14 Apr 1999 14:23:35 +0200."
	<000101be8671$9dd263b0$0300a8c0 AT abraracourcix DOT askesis DOT nl>
Date:	Wed, 14 Apr 1999 08:43:53 -0500
From:	Mumit Khan <khan AT xraylith DOT wisc DOT EDU>

"Joost Kraaijeveld" <JKraaijeveld AT askesis DOT nl> writes:
> Dit is een meerdelig bericht in MIME-indeling.
> 
> ------=_NextPart_000_0002_01BE8682.615B33B0
> Content-Type: text/plain;
> 	charset="iso-8859-1"
> Content-Transfer-Encoding: 7bit
> 
> Sorry for sending this twice: with and without attachement.
> 
> Hi,
> 
> I am having problems with creating a C++ dll with EGCS 1.1.2 in Windows.
> Attached is a zip file that, if unzipped, contains an example (with make
> file and it's output). Is this known or is there a sollution?

There are quite a few unresolved issues in making DLLs with C++ code that
makes use of inline functions and exceptions in DLLs. 

Avoid inline functions in DLLs. Even if it were supported, there are
pitfalls to worry about (which is one is being used -- DLL one or the
local copy? how does that change the import semantics? etc). I believe
MSDN has some info on this as well.

Regards,
Mumit


--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com

- Raw text -