public inbox for pthreads-win32@sourceware.org
 help / color / mirror / Atom feed
From: "David Bo Jensen" <dbj@elektronik.dk>
To: <pthreads-win32@sourceware.org>
Cc: <mr@marcelruff.info>
Subject: Re:Status for Windows CE with pthreads 2.7.0?
Date: Thu, 14 Sep 2006 15:56:00 -0000	[thread overview]
Message-ID: <001f01c6d816$57058ee0$2101a8c0@dit3155830689b> (raw)

 I can compile, if the following flag are set /D "WINCE" /D "HAVE_CONFIG_H"
Further more some header files like <process.h> should be prevented from 
being included like this.
#ifndef WINCE
#    include <procee.h>
#endif

Doing that I could create a static library if I compiled the follow files:

"private.c" "attr.c""barrier.c""cancel.c" "cleanup.c" "condvar.c" "create.c" 
"dll.c"
"errno.c" "exit.c" "fork.c" "global.c" "misc.c" "mutex.c" "nonportable.c"
"rwlock.c" "sched.c" "semaphore.c" "signal.c" "spin.c" "sync.c" "tsd.c"

unfortunately it gives me linking errors when I try to link it to my 
program.

create.obj : error LNK2019: unresolved external symbol ptw32_threadDestroy 
referenced in function pthread_create
create.obj : error LNK2019: unresolved external symbol 
ptw32_setthreadpriority referenced in function pthread_create
create.obj : error LNK2019: unresolved external symbol ptw32_threadStart 
referenced in function pthread_create
create.obj : error LNK2019: unresolved external symbol ptw32_new referenced 
in function pthread_create
SCUtility.lib(SCUtility.obj) : error LNK2019: unresolved external symbol 
__imp_pthread_join referenced in function "int __cdecl exit(void)" 
(?exit@@YAHXZ)


I can see that source code exist for the unresolved external symbols, but if 
I add some of the files I get "already defined" warnings..
I would appreciate if someone could tell us what files are appropriate for 
use with windows CE. 


             reply	other threads:[~2006-09-14 15:56 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-14 15:56 David Bo Jensen [this message]
2006-09-14 18:27 ` Status " Romano Paolo Tenca
2006-09-14 18:30 ` small fixes Romano Paolo Tenca

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='001f01c6d816$57058ee0$2101a8c0@dit3155830689b' \
    --to=dbj@elektronik.dk \
    --cc=mr@marcelruff.info \
    --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).