From: Jim.Totten@barco.com
To: 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: <1DB6D0B30846D111B4860000F8D02CB517C78F@tucmex01.barco.com> (raw)
Message-ID: <19990331194500.VkM5ZRu5JySNgFAj-5jypFL2qi9W4X5kLXMHvOEqD4Q@z> (raw)
Do what the rest of us did - give up using the cygwin stuff and go to
MS. The sooner you do it, the better off you'll be......
-----Original Message-----
From: kentaro-hayashi@bea.hi-ho.ne.jp
[SMTP:kentaro-hayashi@bea.hi-ho.ne.jp]
Sent: Saturday, March 13, 1999 11:40 AM
To: cygwin@sourceware.cygnus.com
Subject: Can I create a DLL with g++?
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.
I succeeded to make the DLL except for core dumping when the
main program accessed to the DLL. I consulted the User's
manual and the FAQs, but could not find any solutions.
Could anyone tell me what should I do?
Regards,
Kentaro Hayashi
--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com
--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com
next 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 11:21 Jim.Totten [this message]
[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
-- strict thread matches above, loose matches on Subject: below --
1999-03-13 8:41 林 健太郎
[not found] ` < 36EA94C928A.789BKENTARO-HAYASHI@bea.hi-ho.ne.jp >
1999-03-13 13:55 ` Mumit Khan
1999-03-31 19:45 ` Mumit Khan
1999-03-31 19:45 ` cygwin-unsubscribe
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=1DB6D0B30846D111B4860000F8D02CB517C78F@tucmex01.barco.com \
--to=jim.totten@barco.com \
--cc=cygwin@sourceware.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).