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

Yeah I can't think of any easyway, either, except perhaps making
static linking the default way and "make those DLL guys use a
preprocessor flag" (which may not be the best way).
Does anybody know what other libraries do in this case? Typically do
they all require some preprocessor macro to express if the library is
static or not? (I guess in linux they don't somehow, but maybe
windows/MSVC require it?)

On 2/18/13, Ross Johnson <> wrote:
> Hi Roger,
> Happy to receive suggestions that work for both MSVS and GNU toolchains.
> It must be possible (although I haven't found a way, but I'm probably
> overestimating the problem and just can't see the obvious).
> PTW32_STATIC_LIB is there during app builds because the headers
> (pthread.h, sched.h, semaphore.h) are used both in building the library
> and building apps but simply controls the export/import of symbols or not.
> On 16/02/2013 5:36 AM, Roger Pack wrote:
>> would it be possible to somehow modify pthreads-win32 so that, if
>> compiled as static, and used as static, there is no need for the
>> "using" program to have to specify PTW32_STATIC_LIB ?  It seems a bit
>> odd to me to have to, for instance, configure ffmpeg like
>> ./configure --extra-cflags=-DPTW32_STATIC_LIB
>> in order to be able to use it.
>> Anyway just thinking out loud.
>> Thanks!
>> -roger-

                 reply	other threads:[~2013-02-20 16:59 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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