From: Ross Johnson <rpj@ise.canberra.edu.au>
To: pthreads-win32@sources.redhat.com, Fabrice Beauvir <fbeauvir@gerpi.fr>
Subject: Re: [Fabrice Beauvir <fbeauvir@gerpi.fr>] Porting pThread under Windows CE
Date: Mon, 13 Jan 2003 02:27:00 -0000 [thread overview]
Message-ID: <3E22248A.90705@ise.canberra.edu.au> (raw)
In-Reply-To: <m365sykrid.fsf@scooby.brisbane.redhat.com>
Sorry for the delay, I'm just back from vacation.
I'm not at all familiar with the process of building for WinCE and
I'm not able to build and test WinCE builds. The port relies
entirely on contributions for patches and testing.
The first requirement for building would be to define WINCE in your
build environment. This is used by config.h to define other macros
that the WinCE port uses.
Check config.h to confirm that those defines are appropriate for
your version of WinCE. Later versions, for example, support
semaphores and don't need to define NEED_SEM.
If you make any changes to config.h or anything else please send me
your changes (after you confirm that it works), and I'll incorporate
any improvements.
Regards.
Ross
Ben Elliston wrote:
> Subject: Topics
>
> Topics:
> Porting pThread under Windows CE
>
>
>
> ------------------------------------------------------------------------
>
> Subject:
> Porting pThread under Windows CE
> From:
> Fabrice Beauvir <fbeauvir@gerpi.fr>
> Date:
> Thu, 09 Jan 2003 15:27:20 +0100
> To:
> bje@redhat.com
>
>
> 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 prev parent reply other threads:[~2003-01-13 2:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-09 20:23 Ben Elliston
2003-01-13 2:27 ` Ross Johnson [this message]
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=3E22248A.90705@ise.canberra.edu.au \
--to=rpj@ise.canberra.edu.au \
--cc=fbeauvir@gerpi.fr \
--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).