From: Erik Hensema <erik.hensema@group2000.nl>
To: 'Pthreads-win32' <pthreads-win32@sourceware.cygnus.com>
Subject: The makefile for nmake
Date: Wed, 05 Jan 2000 03:18:00 -0000 [thread overview]
Message-ID: <A01E735D4940D311A3850090275559330BA9DA@NTSRV02> (raw)
Hi,
I see my version of the makefile for MS nmake is to be included in the new
snapshot, but it contains an error:
[...]
pthread.dll: $(OBJ) pthread.def
cl /LDd /Zi *.obj /Fepthread.dll \
pthread.def \
/link /nodefaultlib:libcmt \
msvcrt.lib
This links the DLL to msvcrt.lib. The last two lines can be replaced by the
/MD switch, which does the same.
.c.obj::
cl /W3 /MT /nologo /Yd /Zi /I. \
/D_WIN32_WINNT=0x400 \
/DSTDCALL=_stdcall \
-c $<
This links to libcmt.lib using /MT (yes, AFAIK even during a compile! in any
case, the /MT switch is inconsistent which the link command above).
Libcmt is the statically linked thread-safe c-lib, and msvcrt.lib is the
dynamically linked thread-safe c-lib. Since using a DLL will save memory (it
can be shared between processes static libs CAN'T be shared), i suggest
using msvcrt. I've been using it with pthreads-win32 for some months now
without any glich.
Also, the link command includes "*.obj" which should be "$(OBJ)".
Here's the diff:
46,49c46
< cl /LDd /Zi *.obj /Fepthread.dll \
< pthread.def \
< /link /nodefaultlib:libcmt \
< msvcrt.lib
---
> cl /LDd /Zi /MD $(OBJ) /Fepthread.dll pthread.def
52c49
< cl /W3 /MT /nologo /Yd /Zi /I. \
---
> cl /W3 /MD /nologo /Yd /Zi /I. \
--
Erik Hensema
Work: erik.hensema@group2000.nl
Home: erik@hensema.xs4all.nl
reply other threads:[~2000-01-05 3:18 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=A01E735D4940D311A3850090275559330BA9DA@NTSRV02 \
--to=erik.hensema@group2000.nl \
--cc=pthreads-win32@sourceware.cygnus.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).