public inbox for pthreads-win32@sourceware.org
 help / color / mirror / Atom feed
From: Philip Van Hoof <spam@pvanhoof.be>
To: Marcel Ruff <mr@marcelruff.info>
Cc: pthreads-win32@sources.redhat.com
Subject: Re: Trying to get pthread-win32 compiling for WinCE
Date: Thu, 28 Dec 2006 21:47:00 -0000	[thread overview]
Message-ID: <1167342425.4875.31.camel@lort> (raw)
In-Reply-To: <45943A27.9090009@marcelruff.info>

On Thu, 2006-12-28 at 22:41 +0100, Marcel Ruff wrote:
> Hi Philip,
> 
> i have compiled the patched pthreads successfully for Windows CE with 
> ARM processor.
> 
> Download the patch for Windows CE from
>    http://www.xmlBlaster.org/wince/pthreads-2006-11-29.patch
> and apply it on pthreads 2.7.0 or better the cvs checkout from 2006-11-29.

Oh, cool and thanks.

I will of course check it out.

Note. So far I succeeded pretty far in getting the cvs HEAD compiled
(with x86 as target, however). Some minor discrepanties about errno.h
and stuff like that .. and winver.h not existing (check my new post).

> I'm not sure if the patch was integrated to the current release 2.8.0
> as i didn't get any feedback.

Oh ok. Well, to the maintainers of pthread-win32: it would be very
interesting to have default wince support! ;)

ps. My plan is to after this try to get glib (from the GNOME stack)
working. And after that, who knows, the win32 gtk+ port of Tor. Guessing
iconv and pthread will be the two most difficult dependencies.

> Compile pthread.c, pthread.h and config.h with the compiler defines 
> /DWINCE and /D_ARM_.
> (all other files are automatically added by pthread.c)

Ok, I'll try that.

> My compiler was from VC++ 2005,


thanks

-- 
Philip Van Hoof, software developer
home: me at pvanhoof dot be 
gnome: pvanhoof at gnome dot org 
http://www.pvanhoof.be/blog




  reply	other threads:[~2006-12-28 21:47 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-28 21:04 Philip Van Hoof
2006-12-28 21:40 ` Marcel Ruff
2006-12-28 21:47   ` Philip Van Hoof [this message]
2006-12-28 22:02     ` Philip Van Hoof

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=1167342425.4875.31.camel@lort \
    --to=spam@pvanhoof.be \
    --cc=mr@marcelruff.info \
    --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).