* [Fabrice Beauvir <fbeauvir@gerpi.fr>] Porting pThread under Windows CE
@ 2003-01-09 20:23 Ben Elliston
2003-01-13 2:27 ` Ross Johnson
0 siblings, 1 reply; 3+ messages in thread
From: Ben Elliston @ 2003-01-09 20:23 UTC (permalink / raw)
To: pthreads-win32
[-- 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
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [Fabrice Beauvir <fbeauvir@gerpi.fr>] Porting pThread under Windows CE
2003-01-09 20:23 [Fabrice Beauvir <fbeauvir@gerpi.fr>] Porting pThread under Windows CE Ben Elliston
@ 2003-01-13 2:27 ` Ross Johnson
2003-01-13 14:42 ` Fabrice Beauvir
0 siblings, 1 reply; 3+ messages in thread
From: Ross Johnson @ 2003-01-13 2:27 UTC (permalink / raw)
To: pthreads-win32, Fabrice Beauvir
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
>
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [Fabrice Beauvir <fbeauvir@gerpi.fr>] Porting pThread under Windows CE
2003-01-13 2:27 ` Ross Johnson
@ 2003-01-13 14:42 ` Fabrice Beauvir
0 siblings, 0 replies; 3+ messages in thread
From: Fabrice Beauvir @ 2003-01-13 14:42 UTC (permalink / raw)
To: Ross Johnson; +Cc: pthreads-win32
Okay,
thank you Ross.
I had began to try to compile unde Windows CE and I notice #define UWIN in some
cases (for example not including process.h with not exist in WinCE )
UWIN, what is meaning UWIN definitions ?
I am trying to port pthread on a ARM target running WINdows CE 3.0 on an Ipaq 3600.
Thank you,
Fabrice.
Quoting Ross Johnson <rpj@ise.canberra.edu.au>:
> 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
> >
>
>
>
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2003-01-13 14:42 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2003-01-09 20:23 [Fabrice Beauvir <fbeauvir@gerpi.fr>] Porting pThread under Windows CE Ben Elliston
2003-01-13 2:27 ` Ross Johnson
2003-01-13 14:42 ` Fabrice Beauvir
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).