From: Ross Johnson <Ross.Johnson@homemail.com.au>
To: pthreads-win32@sourceware.org
Subject: Re: pthreadVC2.dll dependency on MSVCR100.dll
Date: Mon, 26 Nov 2012 01:31:00 -0000 [thread overview]
Message-ID: <50B2C636.2050501@homemail.com.au> (raw)
In-Reply-To: <50B2B1A1.30906@cran.org.uk>
On 26/11/2012 11:02 AM, Bruce Cran wrote:
> On 25/11/2012 23:09, Ross Johnson wrote:
>> Not deliberate. I assume this is a default and one reference I found
>> claims it is linked to by msvcrt.lib in VS 2010. I'm looking but I
>> haven't found a solution yet that I like (assuming it's correct the
>> same reference suggests either linking statically or building with an
>> old environment - both unacceptable ).
>
> If both those are unacceptable then the only solution will be to
> document the dependency. The last toolset which allowed linking to
> msvcrt.dll was WDK 7.1, and that has now been superseded by WDK 8.0,
> which uses VS 2012 instead of an ancient set of compilers. I
> confirmed with Doron at Microsoft earlier this year that it's now a
> requirement to link against VS's CRT
> (http://www.osronline.com/showthread.cfm?link=221792).
>
> Why is statically linking the CRT unacceptable?
>
At the moment this only affects "errno" AFAIK.
The next release will allow a #define PTW32_USES_SEPARATE_CRT switch to
support static linking the CRT into the library but requires application
code changes to replace use of "errno" in some cases. But the prebuilt
dlls won't be compiled with that switch.
next prev parent reply other threads:[~2012-11-26 1:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-23 20:23 Bruce Cran
2012-11-25 23:09 ` Ross Johnson
2012-11-26 0:02 ` Bruce Cran
2012-11-26 1:31 ` Ross Johnson [this message]
2012-11-26 14:14 ` Bruce Cran
2012-11-26 22:55 ` 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=50B2C636.2050501@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).