Hello,

In Platform Builder 5.0, I created a Tiny Kernel platform from the New
Platform Wizard. Then I created a new static library project inside the
platform. In one source file of the project I included "pkfuncs.h".

When building, I got the error message: "fatal error C1083: Cannot open
include file: 'pkfuncs.h': No such file or directory".

I assure this include file existed in my platform folder:
"D:\Test\WINCE500\Emulator_x86\cesysgen\oak\inc\". Also, when building, I
chose the active configuration as "Emulator: x86 Release".

I did the same thing with Platform Builder 4.2 and everything was fine.

What's wrong with WinCE 5.0?

Thanks sincerely,
ARINTEL

Re: Error opening "pkfuncs.h" in Platform Builder 5.0 by Steve

Steve
Wed Mar 30 21:12:12 CST 2005

Does your sources file set WINCEOEM=1?

--
Steve Maillet
EmbeddedFusion
www.EmbeddedFusion.com
smaillet at EmbeddedFusion dot com



Re: Error opening "pkfuncs.h" in Platform Builder 5.0 by ARINTEL

ARINTEL
Wed Mar 30 21:27:02 CST 2005

Hi Steve,

You solved my problem.
The sources file didn't set that switch. But when I manually set it, it
worked.
Is there any corresponding option that I can set in the IDE instead of
setting it manually?

Thanks sincerely,
ARINTEL


"Steve Maillet (eMVP)" wrote:

> Does your sources file set WINCEOEM=1?
>
> --
> Steve Maillet
> EmbeddedFusion
> www.EmbeddedFusion.com
> smaillet at EmbeddedFusion dot com
>
>
>

Re: Error opening "pkfuncs.h" in Platform Builder 5.0 by ARINTEL

ARINTEL
Wed Mar 30 21:31:03 CST 2005

Hello Steve,

Could you please explain for me what it means to set WINCEOEM=1?

Thanks sincerely,
ARINTEL

"Steve Maillet (eMVP)" wrote:

> Does your sources file set WINCEOEM=1?
>
> --
> Steve Maillet
> EmbeddedFusion
> www.EmbeddedFusion.com
> smaillet at EmbeddedFusion dot com
>
>
>

Re: Error opening "pkfuncs.h" in Platform Builder 5.0 by Steve

Steve
Wed Mar 30 22:47:44 CST 2005

Search for WINCEOEM in the Ms header files and it will begin to come clear.
Basically when you #include <Windows.h> you get more stuff that is intended
for device OEMs but not application developers using an exported SDK when
WINCEOEM is defined.

In V5.0 you can add WINCEOM=1 as a custom variable (right click on the
project or sources file in the File View tab

--
Steve Maillet
EmbeddedFusion
www.EmbeddedFusion.com
smaillet at EmbeddedFusion dot com