From: Ross Johnson <rpj@ise.canberra.edu.au>
To: vc <vcotirlea@hotmail.com>
Cc: pthreads-win32@sources.redhat.com
Subject: Re: pthread Win32 - runtime lib VC++ setting
Date: Fri, 09 May 2003 00:52:00 -0000 [thread overview]
Message-ID: <3EBAFBEA.70403@ise.canberra.edu.au> (raw)
In-Reply-To: <LAW12-OE648aK38o2om000011c0@hotmail.com>
Hi,
vc wrote:
>Hi all,
>
>I'm working on Win2k with VC++ 7.1 (VS .NET beta).
>I have to port a Unix app on Windows, so I'm using the pthread lib for
>Win32 (http://sources.redhat.com/pthreads-win32/).
>
>I've downloaded the sources, as I want to build them myself, and
>looking at the VC++ settings, I discovered that in Debug
>configuration, the /MDd flag is used (which means: "multithread- and
>DLL-specific versions of the run-time") and in Release configuration
>the /MT flag is used (even if the release version of the /MDd flag is
>/MD).
>
>Questions:
>1) Why is not used in the project settings the same flag for both
>configuration(i.e /MDd - debug; /MD - release or /MTd - debug; /MT -
>release)? Is there a reason, or it was just by mistake?
>Note: MS recommended for DLLs to use /MD (/MDd)
>
Re the /MT flag, I can't say now because I don't really know.
>2) If for this is actually no reason, is it ok if I build the sources
>using the /MD flag for release?
>
>3) I donwloaded the sources from
>ftp://sources.redhat.com/pub/pthreads-win32/sources/ and there is a
>pthreads-snap-2002-11-04 directory. Is this a release version? Is it
>ok if I'm using this version, or this is just a version between 2
>releases?
>
>
Since you wan't to build the library yourself, you should get the source
via anonymous CVS (see the web page for details -
http://sources.redhat.com/pthreads-win32/). It has the latest bug fixes,
and currently bug fixes are the only changes from the latest versions
available from ftp. I will update the ftp versions ASAP.
>4) When I downloaded just binaries some time ago, there were 3
>versions of the binaries: VC, VSE, VCE. The sources that I downloaded
>now seems to be for the VC version. Am I correct? (because this is the
>version that interests me)
>
>
See the FAQ file, answer to Q2. For VC you don't need to do anything
because it is the default. The others can be used if you add the
appropriate compile flags when you build your application code, and when
you build the library if you don't use the prebuilt dlls.
>
>
>Thanks a lot in advance,
>Viv
>
Regards.
Ross
>
>
next prev parent reply other threads:[~2003-05-09 0:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-08 11:10 vc
2003-05-09 0:52 ` Ross Johnson [this message]
2003-05-09 12:43 ` vc
2003-05-09 16:20 ` vc
2003-05-09 1:17 Simon Gerblich
2003-05-13 16:14 vc
2003-05-14 3:32 ` 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=3EBAFBEA.70403@ise.canberra.edu.au \
--to=rpj@ise.canberra.edu.au \
--cc=pthreads-win32@sources.redhat.com \
--cc=vcotirlea@hotmail.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).