From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 12096 invoked by alias); 13 Jan 2003 14:42:59 -0000 Mailing-List: contact pthreads-win32-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: pthreads-win32-owner@sources.redhat.com Received: (qmail 12084 invoked from network); 13 Jan 2003 14:42:58 -0000 Received: from unknown (HELO mail2.gerpi.fr) (217.167.49.68) by 209.249.29.67 with SMTP; 13 Jan 2003 14:42:58 -0000 Received: by mail2.gerpi.fr (Postfix, from userid 33) id A5577C008; Mon, 13 Jan 2003 15:42:45 +0100 (CET) Received: from 213.36.130.120 ( [213.36.130.120]) as user fbeauvir@localhost by mail2.gerpi.fr with HTTP; Mon, 13 Jan 2003 15:42:45 +0100 Message-ID: <1042468965.3e22d0657ba07@mail2.gerpi.fr> Date: Mon, 13 Jan 2003 14:42:00 -0000 From: Fabrice Beauvir To: Ross Johnson Cc: pthreads-win32@sources.redhat.com Subject: Re: [Fabrice Beauvir ] Porting pThread under Windows CE References: <3E22248A.90705@ise.canberra.edu.au> In-Reply-To: <3E22248A.90705@ise.canberra.edu.au> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit User-Agent: Internet Messaging Program (IMP) 3.1 X-Originating-IP: 213.36.130.120 X-Company: GERPI - www.gerpi.fr X-SW-Source: 2003/txt/msg00010.txt.bz2 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 : > 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 > > 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 > > > > >