public inbox for pthreads-win32@sourceware.org
 help / color / mirror / Atom feed
From: Ross Johnson <rpj@callisto.canberra.edu.au>
To: Pthreads-Win32 list <pthreads-win32@sources.redhat.com>
Subject: Re: Win CE Port
Date: Thu, 12 May 2005 01:44:00 -0000	[thread overview]
Message-ID: <1115862261.7989.143.camel@desk.home> (raw)
In-Reply-To: <4282469F.6010404@gierach.net>

On Wed, 2005-05-11 at 10:53 -0700, Karl Gierach wrote:
> Hi All,
> 
> I just tried building the port for WinCE and found it did not work using 
> embedded visual studio C++ 4.0. Did he build including MING32 by chance? 
> I did not try that. Is there any way I can try to contact the author who 
> implemented the port in order to get it working again? I do not have his 
> email address.

Tristan Savatier, are you still on the list?

Last known address from the CONTRIBUTORS file:

tristan at mpegtv dot com

Maybe also check www.mpegtv.com

Have you checked README.WinCE and Tristan's original notes in WinCE-
PORT? This relates to his port to WinCE v2.1, which doesn't support
Win32 semaphores. These were added in WinCE v3 and the current pthreads-
w32 release assumes this (see NEED_SEM in config.h). Also check the
target specific group definitions at the bottom of config.h.

By the way, Tristan's notes say that not all POSIX semaphore routines
were supported under his port, however all of these routines should now
be supported even for WinCE v2.1. This also means that all of the
routines for condition variables and read/writer locks should also work
on v2.1 (if anyone is still interested in v2.1).

Apart from the semaphore stuff I've tried not to disturb those original
changes.

I'd appreciate any feedback and changes required (preferably diffs to
the most recent release) to make this work out of the box, but I can't
properly test any of the WinCE stuff. I've tested the recent semaphore
changes by defining NEED_SEM (POSIX semaphores based on Win32 events)
and building for W2000, and all tests passed.

Ross

> -Karl G.
> 
> 
> 

      reply	other threads:[~2005-05-12  1:44 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-11 17:53 Karl Gierach
2005-05-12  1:44 ` Ross Johnson [this message]

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=1115862261.7989.143.camel@desk.home \
    --to=rpj@callisto.canberra.edu.au \
    --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).