public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: xclaesse@gmail.com
To: LIU Hao <lh_mouse@126.com>, gcc@gcc.gnu.org
Subject: Re: Issue with dllexport/dllimport inline function
Date: Tue, 11 Oct 2022 09:10:15 -0400	[thread overview]
Message-ID: <845fde640ac4cd51c8bb50373f146987b3d26893.camel@gmail.com> (raw)
In-Reply-To: <fcb4070d-c0b4-0f00-991c-a9b18ecf2a4b@126.com>

Le mardi 11 octobre 2022 à 13:00 +0800, LIU Hao a écrit :
> you may try
> 
>    ```
>    __attribute__((__gnu_inline__))
>    extern inline
>    int g_strcmp0(const char*, const char*)
>      { ...
>    ```

Thanks, I gave that a try but I get many: multiple definition of
`g_strcmp0'. But at least the warning about dllimport is now gone.

> In contrast to C, you don't need the `extern` in C++.
> 
> When this function is being defined in a DLL, `__dllexport__` should
> be used in place of 
> `__gnu_inline__`. This may require another macro, similar to
> `GLIB_API`.



  reply	other threads:[~2022-10-11 13:10 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 [this message]
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
  -- 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=845fde640ac4cd51c8bb50373f146987b3d26893.camel@gmail.com \
    --to=xclaesse@gmail.com \
    --cc=gcc@gcc.gnu.org \
    --cc=lh_mouse@126.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).