From: Simon Gerblich <sgerblich@daronmont.com.au>
To: pthreads-win32@sources.redhat.com
Subject: RE: pthread Win32 - runtime lib VC++ setting
Date: Fri, 09 May 2003 01:17:00 -0000 [thread overview]
Message-ID: <8179ED123ECCD611A5490000F822E6EA197477@pd001649.daronmont.com.au> (raw)
Hi Viv,
I'm working with pthreads-win32 on Win2K with VC++6 SP5.
1)
I think the pthreads-snap-2002-11-04 was build by Ross using the command
line Makefile. The pthread.dsp will build a slightly different version of
pthreadVC.dll. I now use a slightly modified version of the pthread.dsp to
integrate in with my development environment.
2)
I build the Release build of pthreadVC.dll and use the /MD Multithreaded
DLL. I use the Release build of pthreadVC.dll in the Debug and Release
build of my applications. I have no need to build a Debug build of
pthreadsVC.dll because it works :-)
3)
If you go to the pthreads win32 CVS webpage interface, and sort by date you
can see that 4 pthread_mutex_XXX.c functions have been updated since the
pthreads-snap-2002-11-04 version. I downloaded the pthreads_snap-2002-11-04
and then downloaded the latest pthread_mutex_XXXXX.c functions from
http://sources.redhat.com/cgi-bin/cvsweb.cgi/pthreads/?cvsroot=pthreads-win3
2&sortby=date#dirlist
Regards,
Simon
next reply other threads:[~2003-05-09 1:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-09 1:17 Simon Gerblich [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-05-13 16:14 vc
2003-05-14 3:32 ` Ross Johnson
2003-05-08 11:10 vc
2003-05-09 0:52 ` Ross Johnson
2003-05-09 12:43 ` vc
2003-05-09 16:20 ` vc
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=8179ED123ECCD611A5490000F822E6EA197477@pd001649.daronmont.com.au \
--to=sgerblich@daronmont.com.au \
--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).