From: "Phil Frisbie, Jr." <phil@hawksoft.com>
To: Magnus Zakrisson <magnus@orcsoftware.com>
Cc: "Pthreads-Win32@Sources.Redhat.Com" <pthreads-win32@sources.redhat.com>
Subject: Re: What's the suggested way to build pthreads?
Date: Thu, 13 Dec 2001 07:30:00 -0000 [thread overview]
Message-ID: <3C18C95A.C163BFB5@hawksoft.com> (raw)
Message-ID: <20011213073000.-zOraezFIaWlfYAD9PPWGfV4VZYViu2esNpMTpYe3J4@z> (raw)
In-Reply-To: <PIEPLNNHOHEHGLCJFFHEGEENCBAA.magnus@orcsoftware.com>
I have always built the library with MSVC 5.0, so 6.0 should also work
fine.
> Magnus Zakrisson wrote:
>
> I've read in the FAQ that the suggested way to build pthreads is using
> Mingw32 with the MSVCRT library. But all the links to Mingw32 seems
> very old (from the previous millenium) and some links doesn't even
> exist anylonger.
>
> So what is the answer today, how should I build pthreads?
> And if the answer still is that I should use Mingw32 from where do I
> get it and the other stuff that I may need?
>
> I have Cygwin 1.0 and VC++ 6.0 on Win2000. I also have a collegue who
> have the same environment as I do except for VC++ which he doesn't
> want to install if doesn't have to (he's working in another project
> and they don't use VC++).
>
> Thanks,
> Magnus
Phil Frisbie, Jr.
Hawk Software
http://www.hawksoft.com
next prev parent reply other threads:[~2001-12-13 7:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-01 23:21 Magnus Zakrisson
2001-01-01 23:27 ` Phil Frisbie, Jr. [this message]
2001-12-13 7:30 ` Phil Frisbie, Jr.
2001-01-02 10:24 ` Ross Johnson
2001-01-02 16:31 ` CVS repository Ross Johnson
2001-12-13 22:28 ` Ross Johnson
2001-12-13 20:21 ` What's the suggested way to build pthreads? Ross Johnson
2001-12-13 2:37 ` Magnus Zakrisson
2001-01-02 7:27 Mike Kinghan
2001-12-13 7:58 ` Mike Kinghan
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=3C18C95A.C163BFB5@hawksoft.com \
--to=phil@hawksoft.com \
--cc=magnus@orcsoftware.com \
--cc=pthreads-win32@sources.redhat.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).