From: LIU Hao <lh_mouse@126.com>
To: xclaesse@gmail.com, gcc@gcc.gnu.org
Subject: Re: Issue with dllexport/dllimport inline function
Date: Wed, 2 Nov 2022 12:44:49 +0800 [thread overview]
Message-ID: <303829cc-5ed6-9799-d1f8-fd49c3c06135@126.com> (raw)
In-Reply-To: <c983a7387c3bd0736ef12161669bca3619bc53f5.camel@gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1272 bytes --]
在 2022/11/2 02:11, xclaesse@gmail.com 写道:
> Oh, that seems to be working now.
>
> Still got a small issue, glib compiles with -Werror=missing-
> prototypes:
>
> ../foo.h:7:5: error: no previous prototype for ‘g_strcmp0’ [-
> Werror=missing-prototypes]
>
> I'm a bit lost with what the prototype would look like in this case.
>
> I think `__attribute__((__dllexport__))` will be needed when building
> with MSVC at least. Seems gcc, clang and msvc each wants a different
> trick :/
>
>
GCC accepts a plain declaration (no `extern`, no `__attribute` whatsoever), but Clang usually warns
about the inconsistency, and sometimes rejects it, so my suggestion is to copy the declaration from
its definition verbatim.
It might look unnecessarily verbose, however, should be safe in practice. I don't know much about
how MSVC handles such inconsistency, though.
```
#ifndef INSIDE_FOO_C
__attribute__((__gnu_inline__)) __inline__
#endif
extern
int g_strcmp0(const char*str1, const char*str2);
#ifndef INSIDE_FOO_C
__attribute__((__gnu_inline__)) __inline__
#endif
extern
int g_strcmp0(const char*str1, const char*str2) {
...
```
--
Best regards,
LIU Hao
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 840 bytes --]
next prev parent reply other threads:[~2022-11-02 4:44 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-10 16:39 xclaesse
2022-10-11 5:00 ` LIU Hao
2022-10-11 13:10 ` xclaesse
2022-10-11 13:28 ` LIU Hao
2022-10-11 13:35 ` LIU Hao
2022-10-11 14:26 ` xclaesse
2022-10-11 17:42 ` LIU Hao
2022-10-11 18:37 ` xclaesse
2022-10-12 3:03 ` LIU Hao
2022-11-01 15:38 ` xclaesse
2022-11-01 16:06 ` LIU Hao
2022-11-01 18:11 ` xclaesse
2022-11-02 4:44 ` LIU Hao [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-10-10 16:32 xclaesse
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=303829cc-5ed6-9799-d1f8-fd49c3c06135@126.com \
--to=lh_mouse@126.com \
--cc=gcc@gcc.gnu.org \
--cc=xclaesse@gmail.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).