From: "Matthieu GALLIEN" <matthieu.gallien@actoll.com>
To: "'Ross Johnson'" <Ross.Johnson@homemail.com.au>
Cc: <pthreads-win32@sourceware.org>
Subject: RE: Support for Windows CE 6.0
Date: Tue, 16 Nov 2010 10:43:00 -0000 [thread overview]
Message-ID: <981ADCDE39EE4B4893D24BB4B35C4841@actoll.com> (raw)
In-Reply-To: <4CE25DB1.2010208@homemail.com.au>
Hello,
> -----Message d'origine-----
> De : pthreads-win32-owner@sourceware.org
> [mailto:pthreads-win32-owner@sourceware.org] De la part de
> Ross Johnson
> Envoyé : mardi 16 novembre 2010 11:32
> À : Matthieu GALLIEN
> Cc : pthreads-win32@sourceware.org
> Objet : Re: Support for Windows CE 6.0
>
> On 16/11/2010 3:03 AM, Matthieu GALLIEN wrote:
> > Hello,
> >
> > I am working on a project using an embedded board with an
> ARM running windows CE 6.0.
> >
> > I would like to use an existing library that depends on
> pthread for its threading needs.
> > I am more than happy to have found that there exists a
> library with the exact purpose of easing the porting of
> pthread using code to win32.
> >
> > So does anybody reading this mailling list have any
> information regarding the support of windows CE and
> especially the 6.0 version ?
> >
> > I am sorry, but because I mostly have a Linux background, I
> do not know the particularities of windows CE platform APIs.
> This is the main reason why I ask for help.
> >
> > Thanks in advance for any help
>
> It has definitely worked with WinCE in the past following Tristan
> Savatier's patches, and the last updates relating to WinCE
> were in 2007,
> but I don't know any more than this. So there is a very good
> chance it
> will work for you with little or no change. See the link for
> background
> information:
>
> http://sourceware.org/cgi-bin/cvsweb.cgi/pthreads/WinCE-PORT?r
> ev=1.5&content-type=text/x-cvsweb-markup&cvsroot=pthreads-win32
>
> You will ahve to build from source though.
>
Thanks for the information, I had downloaded the last version of the source archive after sending the mail and read the WinCE-PORT file. I will double check with the version in CVS.
I am definitely prepared to build from source. In case of further question or patches, I will follow on the list.
Is there some regression tests suite that I could use to test my build ?
Best regards
--
Matthieu Gallien
ACTOLL
19, Avenue du Granier 38240
Meylan - France
next prev parent reply other threads:[~2010-11-16 10:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-15 16:02 Matthieu GALLIEN
2010-11-16 10:32 ` Ross Johnson
2010-11-16 10:43 ` Matthieu GALLIEN [this message]
2010-11-16 11:06 ` Ross Johnson
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=981ADCDE39EE4B4893D24BB4B35C4841@actoll.com \
--to=matthieu.gallien@actoll.com \
--cc=Ross.Johnson@homemail.com.au \
--cc=pthreads-win32@sourceware.org \
/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).