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, 12 Oct 2022 11:03:35 +0800 [thread overview]
Message-ID: <f361fd85-26d5-aa97-73bb-0cf6d5c3315e@126.com> (raw)
In-Reply-To: <6c5778d2edfaa8b5196ef142ad0339ac6233b641.camel@gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 977 bytes --]
在 2022/10/12 02:37, xclaesse@gmail.com 写道:
>
> Build it with:
> meson setup builddir --cross-file cross_file_mingw64.txt
> ninja -C builddir/
>
> And it fails with:
That's because you compiled it as C. I used g++ to compile these, and there was no such error.
For C, this inline issue is going to be much more messy due to lack of COMDAT support about
`inline`. Your will need a dedicated macro for each translation unit. A dirty solution looks like this:
```
#ifndef INSIDE_FOO_C
__attribute__((__dllexport__)) inline
#endif
extern
int
g_strcmp0(const char*str1, const char*str2)
...
```
and in 'foo.c':
```
#define INSIDE_FOO_C 1
#include "foo.h"
extern int g_strcmp0 (const char *str1, const char *str2);
```
Further reading:
https://github.com/lhmouse/mcfgthread/wiki/Differences-between-GNU,-C99-and-C---%60inline%60
--
Best regards,
LIU Hao
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 840 bytes --]
next prev parent reply other threads:[~2022-10-12 3:03 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 [this message]
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
-- 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=f361fd85-26d5-aa97-73bb-0cf6d5c3315e@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).