Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT sourceware DOT cygnus DOT com>
List-Archive: <http://sourceware.cygnus.com/ml/cygwin/>
List-Post: <mailto:cygwin AT sourceware DOT cygnus DOT com>
List-Help: <mailto:cygwin-help AT sourceware DOT cygnus DOT com>, <http://sourceware.cygnus.com/ml/#faqs>
Sender: cygwin-owner AT sourceware DOT cygnus DOT com
Delivered-To: mailing list cygwin AT sourceware DOT cygnus DOT com
Message-Id: <200003280422.WAA18041@hp2.xraylith.wisc.edu>
To: "vandana yesoda" <vandana DOT yesoda AT wipro DOT com>
cc: cygwin AT sourceware DOT cygnus DOT com
Subject: Re: [Fwd: DLL] 
In-reply-to: Your message of "Tue, 28 Mar 2000 08:58:19 +0530."
             <38E026D2 DOT E64292E0 AT wipro DOT com> 
Date: Mon, 27 Mar 2000 22:22:22 -0600
From: Mumit Khan <khan AT NanoTech DOT Wisc DOT EDU>

"vandana yesoda" <vandana DOT yesoda AT wipro DOT com> writes:
> 
> A DLL(with MFC) is created using Microsoft Visual Studio's VC++. How to
> link this DLL to create an exe. using the GNU GCC compiler.

The issue of MFC and GCC has been discussed here many many times, and
the answer is still no. 

Unless someone can build MFC *with* GCC, the answer will remain "no".

> How to create .def file from the obj files which is created by VC++?

  $ dlltool --output-def foo.def foo.obj [foo2.obj foo3.obj ...]

will export the symbols that were explicitly exported; if you want to
export all symbols:

  $ dlltool --export-all --output-def foo.def foo.obj [...]

> When a .def file is created using dlltool --output-def , the symbols in
> the .def file is not recognized by dlltool when used to create the .exp,
> .a , .dll files.
> 
> how to work with GCC along with VC++.

Don't know what you mean, sorry. You'll have to help us understand by 
providing more information. I assume the issue of leading underscore
(or the lack thereof).

> Is all WIN API's are supported ? ( CreateEvent, CreateThread,
> ResumeThread etc.)

All of Win32 API is supported, yes. There are missing pieces, but that's a
function of the headers/import libraries, and easily fixed. There are some
issues that are thorny, and won't work -- Structured Exception Handling
(SEH) is one of those.

Regards,
Mumit


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