public inbox for pthreads-win32@sourceware.org
 help / color / mirror / Atom feed
From: Ross Johnson <rpj@callisto.canberra.edu.au>
To: pthreads-win32@sources.redhat.com
Subject: Re: Compiling pthreads under windows CE with eVC++
Date: Sat, 22 May 2004 01:12:00 -0000	[thread overview]
Message-ID: <40AEA7F3.2030507@callisto.canberra.edu.au> (raw)
In-Reply-To: <01e201c43f1f$8a23e200$0901a8c0@test>

I look's like PAPCFUNC isn't defined via windows.h for the WinCE 
cross-compilers. Either that or defining _WIN32_WINNT to 0x400 doesn't 
make sense for WinCE.

Anyway, my suggestion to Phillip was to look in MSVC's windef.h (I don't 
have it at hand) and copy the definition into implement.h.

E.g. implement.h should look something like this if I recall correctly:-

#include <windows.h>

#ifndef PAPCFUNC
# define PAPCFUNC (void CALLBACK (*)(DWORD))
#endif

And then hopefully CALLBACK is defined.

If this doesn't work then someone please let me know because I'll need 
to re-arrange the code for WinCE.

Does WinCE support APC? Pthreads-win32 is assuming it does (by expecting 
these macros to be defined) even if it doesn't get used.

Cheers.
Ross

James Ewing wrote:

>Phillip Cuadra wrote -
>
>"I'm trying to build the .dll for pthreads under MS eVC++ 4.0 for Windows
>CE 4 (Pocket PC 2003) on an ARM processor (the IPAQ 5555).  "
>-------------
>
>This thread may help in getting WINCE pthreads to compile -
>
>http://sources.redhat.com/ml/pthreads-win32/2003/msg00101.html
>
>James Ewing
>
>  
>

  reply	other threads:[~2004-05-22  1:12 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-20 21:53 Philip Cuadra
2004-05-21 10:36 ` James Ewing
2004-05-22  1:12   ` Ross Johnson [this message]
     [not found] ` <40ADBE88.5030805@callisto.canberra.edu.au>
2004-06-08 22:38   ` Philip Cuadra

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=40AEA7F3.2030507@callisto.canberra.edu.au \
    --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).