From: Ben Elliston <bje@redhat.com>
To: pthreads-win32@sources.redhat.com
Subject: [Fabrice Beauvir <fbeauvir@gerpi.fr>] Porting pThread under Windows CE
Date: Thu, 09 Jan 2003 20:23:00 -0000 [thread overview]
Message-ID: <m365sykrid.fsf@scooby.brisbane.redhat.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 62 bytes --]
Subject: Topics
Topics:
Porting pThread under Windows CE
[-- Attachment #2: Type: text/plain, Size: 685 bytes --]
Date: Thu, 09 Jan 2003 15:27:20 +0100
From: Fabrice Beauvir <fbeauvir@gerpi.fr>
To: bje@redhat.com
Subject: Porting pThread under Windows CE
Message-ID: <3E1D86C8.4020800@gerpi.fr>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-length: 422
Hi,
I am actually porting an application under Wince wich need pthread.
A port seem to be done in 1999.
But,
I haven't found source files "pthread-win32-snap-1999-05-30-WinCE" and
project files aren't compatible with eMbedded Visual C++ 3.0.
According to WINCE-Port readme file, project ported to WINCE but how to
generate pthread under Windows CE
Thank you for your help,
Fabrice Beauvir
fbeauvir@gerpi.fr
next reply other threads:[~2003-01-09 20:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-09 20:23 Ben Elliston [this message]
2003-01-13 2:27 ` Ross Johnson
2003-01-13 14:42 ` Fabrice Beauvir
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=m365sykrid.fsf@scooby.brisbane.redhat.com \
--to=bje@redhat.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).