From: Marcel Ruff <mr@marcelruff.info>
To: Philip Van Hoof <spam@pvanhoof.be>, pthreads-win32@sources.redhat.com
Subject: Re: Trying to get pthread-win32 compiling for WinCE
Date: Thu, 28 Dec 2006 21:40:00 -0000 [thread overview]
Message-ID: <45943A27.9090009@marcelruff.info> (raw)
In-Reply-To: <1167339870.4875.15.camel@lort>
Hi Philip,
i have compiled the patched pthreads successfully for Windows CE with
ARM processor.
Download the patch for Windows CE from
http://www.xmlBlaster.org/wince/pthreads-2006-11-29.patch
and apply it on pthreads 2.7.0 or better the cvs checkout from 2006-11-29.
I'm not sure if the patch was integrated to the current release 2.8.0
as i didn't get any feedback.
Compile pthread.c, pthread.h and config.h with the compiler defines
/DWINCE and /D_ARM_.
(all other files are automatically added by pthread.c)
My compiler was from VC++ 2005,
regards
Marcel
next prev parent reply other threads:[~2006-12-28 21:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-28 21:04 Philip Van Hoof
2006-12-28 21:40 ` Marcel Ruff [this message]
2006-12-28 21:47 ` Philip Van Hoof
2006-12-28 22:02 ` Philip Van Hoof
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=45943A27.9090009@marcelruff.info \
--to=mr@marcelruff.info \
--cc=pthreads-win32@sources.redhat.com \
--cc=spam@pvanhoof.be \
/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).