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
X-Authentication-Warning: mercury.xraylith.wisc.edu: khan owned process doing -bs
Date: Mon, 21 Jun 1999 13:20:46 -0500 (CDT)
From: Mumit Khan <khan AT xraylith DOT wisc DOT EDU>
To: Alan Patterson <alan DOT patterson AT nexan DOT com>
cc: cygwin AT sourceware DOT cygnus DOT com
Subject: Re: exporting DLLs
In-Reply-To: <376E0EA5.B05F01C2@nexan.com>
Message-ID: <Pine.LNX.3.96.990621131852.21184A-100000@mercury.xraylith.wisc.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

On Mon, 21 Jun 1999, Alan Patterson wrote:

> Hi All,
>     I am not completely clear on making DLLs. I have read the userguide
> but am not sure on one point. The user guide discusses creating DLLs for
> use within a cygwin program. Will these DLLs also work for other
> compilers.

See http://www.xraylith.wisc.edu/~khan/software/gnu-win32/ for info
on making DLLs. There are two entries you should look at:

  "How to make DLLs ..." -- for and by Cygwin applications.
  "How to make JNI ..."  -- shows how to make Cygwin DLLs that will be
  loaded by "foreign" applications such as MSVC execs/dlls.

Regards,
Mumit




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