From: Ross Johnson <rpj@callisto.canberra.edu.au>
To: Pthreads-Win32 list <pthreads-win32@sources.redhat.com>
Subject: Re: pthread for WinCE
Date: Wed, 02 Mar 2005 11:10:00 -0000 [thread overview]
Message-ID: <1109761848.11333.18.camel@desk.home> (raw)
In-Reply-To: <BAY103-DAV181976E142BF9EB53061CD835A0@phx.gbl>
It was ported several years back (1999) by Tristan Savatier. See
README.WinCE in the package and the WinCE-Port file for Tristan's notes.
It needs someone to try to build with the current snapshot and send me
changes if any. I don't have the tools for WinCE builds.
All of Tristan's patches are still in the source, but I have no way to
check that subsequent changes in either the library or WinCE have broken
it.
I think any changes needed to update will be small.
Ross
On Wed, 2005-03-02 at 11:32 +0100, Viv wrote:
> Somehow I didn't receive my own post (from yesterday) on
> pthreads-win32@sources.redhat.com
> I am not sure why, so I will resend my original email ...
>
> Hi,
>
> I am using the pthread lib in my Windows application succesfully for some
> time (btw, thx for this useful lib!) and now my company would like to port
> our product on WinCE systems.(which now seems to be called 'mangento').
> As I read from some docs, there is already support in the pthread libs for
> WinCE, but I would like to double check this ... So:
> - is there full support of pthread lib on WinCE?
> - is there something special that I should know about (for instance when
> building the sources) specific to WinCE?
> - where can I find some docu about pthread on WinCE systems?
>
> Thanks in advance,
> Viv
>
prev parent reply other threads:[~2005-03-02 11:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-02 23:17 New snapshot 2005-01-03 Ross Johnson
2005-03-02 10:32 ` pthread for WinCE Viv
2005-03-02 11:10 ` Ross Johnson [this message]
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=1109761848.11333.18.camel@desk.home \
--to=rpj@callisto.canberra.edu.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).