public inbox for
 help / color / mirror / Atom feed
From: Roger Pack <>
To: Ross Johnson <>
Subject: Re: feature request: not need to specify PTW32_STATIC_LIB for static usage possible ?
Date: Wed, 20 Feb 2013 17:01:00 -0000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

> Sounds like you wanted to address this to the list but I think you
> replied only to me.

oops, moving back on list...suggest the ML be modified so the default
reply-to is the ML :)

> In Linux, the usual 'static' qualifier on declarations controls
> visibility, regardless of dynamic or static linking but is restricted to
> a file (or perhaps more accurately a compilation unit). If this isn't
> convenient then GCC 4 and above recognise __attribute__
> ((visibility("hidden"))), and also "#pragma GCC visibility
> push(hidden)/#pragma GCC visibility pop" for block coverage in e.g.
> header files. Otherwise everything is visible by default.
> So I believe GNU can build a Windows dynamic or static library using the
> merged pthread.c after adding 'static' qualifiers where necessary, but I
> don't know off-hand if this works for MSVS. If it does, i.e. replace the
> need for _declspec(export/import), then we probably have a solution.

Yeah I know for FFmpeg they ended up basically "having" to use
_declspec at least for shared constants (for the rest I guess there
was some way around it, using their av_export symbol, but I'm no pro
here :)
I suppose the status quo is all right for now, thanks.

  parent reply	other threads:[~2013-02-20 17:01 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-15 18:36 Roger Pack
2013-02-19  1:03 ` Ross Johnson
     [not found]   ` <>
     [not found]     ` <>
2013-02-20 17:01       ` Roger Pack [this message]
2013-10-31 19:46         ` Roger Pack
2013-11-01  0:56           ` Ross Johnson

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

* 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).