public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: "Jörg Schaible" <joerg.schaible@gmx.de>
To: cygwin@cygwin.com
Subject: Re: Trying to link an MSVC DLL with a Cygwin Application
Date: Wed, 05 May 2004 16:58:00 -0000	[thread overview]
Message-ID: <200405051857.47338.joerg.schaible@gmx.de> (raw)
In-Reply-To: <4098984F.8010505@luukku.com>

Please keep replies on the list!

On Wednesday 05 May 2004 09:31, you wrote:
Jt> Jörg Schaible wrote:
Jt>
Jt> > john george wrote:
Jt> >
Jt> >
Jt> >>Can i resolve the name mangling issue by adding the
Jt> >>extern "C" declaration for every function that I'm
Jt> >>exporting in the MSVC created DLL.
Jt> >>I tried this but doesn't seem to work.Is there any
Jt> >>other way to do this.
Jt> >
Jt> >
Jt> > Be aware, that there is more than just a compatible call. You have to
Jt> > recognize, that you have two different RT-libs and therefore also two
Jt> > memory managers. Said that, you cannot allocate memory from the first
 one Jt> > and set it free on the second. While this is quite obvious with
 malloc and Jt> > friends, you have also to take care of strdup or fopen or
 ...
Jt>
Jt> Aren't cygwin given pointers and msvcrt given pointers interchangeable..?
Jt>
Jt> Well I'm not going to try it but it could be handy to know...

This has nothing to do with Cygwin itself, but is true for any combination of 
different RT-Libs (Cygwin, MS, Borland, ...)

Regards,
Jörg

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

  parent reply	other threads:[~2004-05-05 16:58 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-04  5:23 Billinghurst, David (CALCRTS)
2004-05-04  5:57 ` john george
2004-05-04 13:47   ` Igor Pechtchanski
2004-05-04 18:10   ` Jörg Schaible
     [not found]     ` <4098984F.8010505@luukku.com>
2004-05-05 16:58       ` Jörg Schaible [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-05-04  9:07 Arash Partow
2004-05-04  5:07 john george

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=200405051857.47338.joerg.schaible@gmx.de \
    --to=joerg.schaible@gmx.de \
    --cc=cygwin@cygwin.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).