Page 1 of 1

PostPosted: Tue Feb 11, 2003 10:23 am
by MaxS
I'm going mad..
I've a Philips Nino PsPC (winCE 2.01, b&w) and pocketC v3.
I'd like to use CEAPIs libraries on my device but there are
a lot of things that I ignore.
I've downloaded the correct CAB file and I've installed it in my Nino.
When I try to run one of example files that comes with libraries I get an error at runtime (pocketC compiles regularly) "library must be present in the same directory"...
Following dlls are in my windows directory:


and obviously

Guy thinks that I'm missing


not supplied with wince2.01 sdk...:(

I'm thinking that I'm doing something wrong.. does someone
can send a reply indicating all steps in installing and using
CEAPIs libraries? must I register dlls in OS with regsvrce?

There's another way to manage all OS features with ONLY pocketC V3?
A direct call to dlls?
:?I really don't know what I'm talkin about...:?:

Any help, suggestion, link to a download site for missing dlls will be
very apreciated..


PostPosted: Tue Feb 11, 2003 11:06 am
by guy
I've rebuilt CEAPI to not include the common dialogues on PPC 2.01. They're already excluded for PPC 2.11 since the .lib doesn't exist. For 2.01 the .lib exists, but there's no DLL to match it.

I'll post the updated CEAPI once I've done some more testing.

Unfortunately there is no other alternative for directly calling a DLL from PocketC unless you write one yourself.

CEAPI does have the CEAPI_stdcall() function which allows you to call any function in any DLL (in fact any function that you have a real address for), not just the ones that CEAPI provides directly callable entry points for.

PocketC CE API interface:
PCForm and CE API forum:

PostPosted: Tue Feb 11, 2003 12:06 pm
by MaxS
Thanks a lot.
some questions now:
1) Does PCForm support CEAPIs?
2) I've read in this forums that you are working on a ansiC compiler..
any news?
3) I'd like to learn COM you have some tutorial link
to suggest me?

thanks a lot one more time

PostPosted: Tue Feb 11, 2003 12:30 pm
by guy
1. PCForm doesn't generate any code that requires CEAPI. You can use CEAPI in your own code in a PCForm program. The current internal next version of PCForm uses CEAPI itself, but again doesn't require it for generated code.
2. No news. Trying to nail down CEAPI before continuing with compiler. Some of the CEAPI stuff will go into the compiler (principally the work I did on _stdcall and _cdecl).
3. Look in the knowledge base section of this site. Kevin posted a COM tutorial many months (or years) ago.

PocketC CE API interface:
PCForm and CE API forum: