From: "Seyran Avanesyan" <seyran.avanesyan@tanner.com>
To: <brian@dessent.net>
Cc: <gcc-help@gcc.gnu.org>
Subject: RE: extern "C" From command line
Date: Sat, 23 Aug 2008 01:38:00 -0000 [thread overview]
Message-ID: <D66102A43110FC488698F1C3B605E93108F962A7@exchange01.tanner.com> (raw)
In-Reply-To: <48AE1E8A.12ADDE12@dessent.net>
Brian Dessent wrote:
> Please don't hijack threads; start a new thread.
Thanks for correcting me.
> The mangling is there for a reason. If you exported a function with
> C++
> linkage but without its name mangled then it's very likely that you
> could call it from a compiler with a different C++ ABI, such as MSVC,
> and that would fail. Mangling prevents this, because it requires that
> to call the function you have a compiler with compatible ABI.
The functions are going to be exported from a Dll, which is going to be
done using MinGW. Is that still requires that client of that Dll be
compiled with MinGW?
> If your complaint is simply that you don't want to put mangled names
in
> the .def file, then I must ask: why use a .def file at all? It's
> usually not needed. The GNU linker has auto-export enabled by default
> which causes all symbols to be exported if __declspec(dllexport) is
not
> used anywhere. And if __declspec(dllexport) is used, then the source
> itself already controls what functions to be exported so the .def file
> is extraneous.
gcc -x c++ source.cpp -o source.o
gcc -shared -o source.dll my_source.o source.o
I'm exporting just two functions from "my_source.o" (which I have access
to, and they have __declspec(dllexport) and extern "C").
There are many other global functions in "my_source.o" which is used
from "source.o", but not need to be exported from the resulting Dll.
I needed .def file to export all global functions from "source.o" to not
use -export-all feature (because it will export all globals from both
modules regardless of __declspecs.)
And I'm getting this .def file by using dlltool (MinGW component.)
The problem is I need to MinGW compile a Dll as C++ not as C, and call
exported functions from MSVC compiled application.
Thanks,
Seyran
next prev parent reply other threads:[~2008-08-22 23:57 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-19 16:12 Restricting symbol binding within shared object Arindam
2008-08-19 16:58 ` special comments handling in the C compiler Tim Wang
2008-08-22 1:52 ` extern "C" From command line Seyran Avanesyan
2008-08-22 2:12 ` Brian Dessent
2008-08-23 1:38 ` Seyran Avanesyan [this message]
2008-08-23 2:37 ` Brian Dessent
2008-08-23 2:46 ` Seyran Avanesyan
2008-08-22 2:04 ` 64-bit gcc Seyran Avanesyan
2008-08-22 11:01 ` Brian Dessent
2008-08-22 20:09 ` Seyran Avanesyan
2008-08-22 22:32 ` Brian Dessent
2008-08-22 22:45 ` Seyran Avanesyan
2008-08-23 2:31 ` Brian Dessent
2008-08-23 2:45 ` NightStrike
2008-08-23 2:49 ` Seyran Avanesyan
2008-08-23 3:18 ` Brian Dessent
2008-08-23 2:00 ` NightStrike
2008-08-23 2:13 ` Seyran Avanesyan
2008-08-19 18:49 ` Restricting symbol binding within shared object Ian Lance Taylor
2008-08-20 19:36 ` Arindam
2008-08-21 4:43 ` Ian Lance Taylor
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=D66102A43110FC488698F1C3B605E93108F962A7@exchange01.tanner.com \
--to=seyran.avanesyan@tanner.com \
--cc=brian@dessent.net \
--cc=gcc-help@gcc.gnu.org \
/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).