From: Ross Johnson <Ross.Johnson@homemail.com.au>
To: pthreads-win32@sourceware.org
Subject: Re: feature request: not need to specify PTW32_STATIC_LIB for static usage possible ?
Date: Tue, 19 Feb 2013 01:03:00 -0000 [thread overview]
Message-ID: <5122CF4E.1050301@homemail.com.au> (raw)
In-Reply-To: <CAL1QdWdtDy3zNY0hrGiyhj_Kk1aHdnJJFJinATB0Y0KECCnmdg@mail.gmail.com>
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-
next prev parent reply other threads:[~2013-02-19 1:03 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 [this message]
[not found] ` <CAL1QdWcyU76396H_RzXNBMAf7QFrmtC_Ab7ajC=TzG43QJm7fQ@mail.gmail.com>
[not found] ` <51242375.1070904@homemail.com.au>
2013-02-20 17:01 ` Roger Pack
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:
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=5122CF4E.1050301@homemail.com.au \
--to=ross.johnson@homemail.com.au \
--cc=pthreads-win32@sourceware.org \
/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).