From: Mumit Khan <khan@xraylith.wisc.EDU>
To: egcs@cygnus.com
Cc: cygwin@sourceware.cygnus.com
Subject: Re: Can I create a DLL with g++?
Date: Wed, 31 Mar 1999 19:45:00 -0000 [thread overview]
Message-ID: <199903132155.PAA01288@modi.xraylith.wisc.edu> (raw)
Message-ID: <19990331194500.XiH0DeBo3jhyrPTSgeKYralQab9VUMMv56x237ZSuKU@z> (raw)
In-Reply-To: <36EA94C928A.789BKENTARO-HAYASHI@bea.hi-ho.ne.jp>
=?ISO-2022-JP?B?GyRCTlMbKEIgGyRCN3JCQE86GyhCIA==?=<kentaro-hayashi@bea.hi-ho.ne
.jp> writes:
>
> I just started to use cygwin development tools.
> I appreciate the developers provided these tools working well.
> But I have a question about DLL, how can I create a DLL
> with g++? How to use the DLL which consists of c++ objects from
> main program.
See http://www.xraylith.wisc.edu/~khan/software/gnu-win32/ and scan
for "How to make DLLs using EGCS". I've just updated my dllhelpers
package to version 0.2.5 that provides examples for C, C++ and F77
DLLs (sorry, not ObjC yet).
Be warned however that the design of MS DLLs makes it extremely hard
to create DLLs from C++ code in some cases (especially when you're
using exceptions, RTTI and a few other recent C++ features in a DLL).
For most "normal" code, it should work just fine. Cygwin runtime itself
is a C++ DLL.
Regards,
Mumit
--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com
next prev parent reply other threads:[~1999-03-31 19:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-03-13 8:41 林 健太郎
[not found] ` < 36EA94C928A.789BKENTARO-HAYASHI@bea.hi-ho.ne.jp >
1999-03-13 13:55 ` Mumit Khan [this message]
1999-03-31 19:45 ` Mumit Khan
1999-03-31 19:45 ` cygwin-unsubscribe
1999-03-13 11:21 Jim.Totten
[not found] ` < 1DB6D0B30846D111B4860000F8D02CB517C78F@tucmex01.barco.com >
1999-03-13 11:47 ` Richard Stanton
1999-03-31 19:45 ` Richard Stanton
1999-03-31 19:45 ` Jim.Totten
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=199903132155.PAA01288@modi.xraylith.wisc.edu \
--to=khan@xraylith.wisc.edu \
--cc=cygwin@sourceware.cygnus.com \
--cc=egcs@cygnus.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).