After building and testing my platform in the platform builder [4.2] I
created a sample application that worked fine.
I then exported an SDK and installed it on the same computer.
Under eVC4 that sample application did not compile because it could not find
the file "nkintr.h" which is #included from one of the CPP files.
To resolve this I added the path
[D:\WINCE420\PUBLIC\my_platform\WINCE420\CEPC\cesysgen\oak\inc] in
Tools->options->Directories.

But this is not an acceptable solutions, because other developers in my team
to not have PB installed at all, only eVC4. They do not have a \WINCE420
folder at all...

After resolving the "nkintr.h" problem, the file "ceddk.lib" which was
required by the project was missing.So now I had to add
[D:\WINCE420\PUBLIC\my_platform\WINCE420\CEPC\cesysgen\oak\lib\x86\retail]

I was finally able to built the project; When I debugged it, eVC asked for
some missing DLL like "zlib.dll" So I directed it to
[D:\WINCE420\PUBLIC\my_platform\RelDir\CEPC_X86Release]

Why were the files "nkintr.h", "ceddk.lib", "zlib.dll" and other missing
from the SDK?
How do I address this problem in computers who do not have the platform
[\WINCE420] files install in?

Thanks.

Offir.

Re: Problem with an exported SDK by visi

visi
Mon May 31 21:09:21 CDT 2004

in PB,you should add MFC component,then export SDK.
"Offir Bakshitz" <bakshitz@email.com> wrote in message
news:uXed8ZyREHA.1216@TK2MSFTNGP10.phx.gbl...
> After building and testing my platform in the platform builder [4.2] I
> created a sample application that worked fine.
> I then exported an SDK and installed it on the same computer.
> Under eVC4 that sample application did not compile because it could not
find
> the file "nkintr.h" which is #included from one of the CPP files.
> To resolve this I added the path
> [D:\WINCE420\PUBLIC\my_platform\WINCE420\CEPC\cesysgen\oak\inc] in
> Tools->options->Directories.
>
> But this is not an acceptable solutions, because other developers in my
team
> to not have PB installed at all, only eVC4. They do not have a \WINCE420
> folder at all...
>
> After resolving the "nkintr.h" problem, the file "ceddk.lib" which was
> required by the project was missing.So now I had to add
> [D:\WINCE420\PUBLIC\my_platform\WINCE420\CEPC\cesysgen\oak\lib\x86\retail]
>
> I was finally able to built the project; When I debugged it, eVC asked for
> some missing DLL like "zlib.dll" So I directed it to
> [D:\WINCE420\PUBLIC\my_platform\RelDir\CEPC_X86Release]
>
> Why were the files "nkintr.h", "ceddk.lib", "zlib.dll" and other missing
> from the SDK?
> How do I address this problem in computers who do not have the platform
> [\WINCE420] files install in?
>
> Thanks.
>
> Offir.
>
>
>



Re: Problem with an exported SDK by Offir

Offir
Tue Jun 01 01:51:21 CDT 2004

I have already done so.
What is common to all the missing files is that they belong to the DDK. For
some reason they are not included in the SDK.

"visi" <zqvisi@hotmail.com> wrote in message
news:u3ZDm03REHA.1160@TK2MSFTNGP09.phx.gbl...
> in PB,you should add MFC component,then export SDK.
> "Offir Bakshitz" <bakshitz@email.com> wrote in message
> news:uXed8ZyREHA.1216@TK2MSFTNGP10.phx.gbl...



Re: Problem with an exported SDK by Paul

Paul
Tue Jun 01 12:50:59 CDT 2004

You can add the specific 'missing' header files to your SDK. The DDK stuff
doesn't seem to go into exported SDKs, by default, however.

Paul T.

"Offir Bakshitz" <bakshitz@email.com> wrote in message
news:uqcsbT6REHA.1312@TK2MSFTNGP12.phx.gbl...
> I have already done so.
> What is common to all the missing files is that they belong to the DDK.
For
> some reason they are not included in the SDK.
>
> "visi" <zqvisi@hotmail.com> wrote in message
> news:u3ZDm03REHA.1160@TK2MSFTNGP09.phx.gbl...
> > in PB,you should add MFC component,then export SDK.
> > "Offir Bakshitz" <bakshitz@email.com> wrote in message
> > news:uXed8ZyREHA.1216@TK2MSFTNGP10.phx.gbl...
>
>



Re: Problem with an exported SDK by Offir

Offir
Tue Jun 01 13:13:56 CDT 2004

> You can add the specific 'missing' header files to your SDK. The DDK
stuff
> doesn't seem to go into exported SDKs, by default, however.

Thanks Paul,
But all this does not explain why some DLL's are also not included in the
SDK, for example zlib.dll. Should I manually add such files also?
And how do I manually add files to my SDK?



Re: Problem with an exported SDK by Paul

Paul
Tue Jun 01 13:50:13 CDT 2004

I don't know; I guess that depends on your target device. I don't have any
zlib.dll installed with any of my SDKs. If the DLL is already in the device
and you don't care about the user debugging into the DLL itself, I'm not
aware of any reason for that DLL to be in the SDK.

Paul T.

"Offir Bakshitz" <offirb@adaptmedia.co.il> wrote in message
news:%23KoflSASEHA.3016@TK2MSFTNGP10.phx.gbl...
> > You can add the specific 'missing' header files to your SDK. The DDK
> stuff
> > doesn't seem to go into exported SDKs, by default, however.
>
> Thanks Paul,
> But all this does not explain why some DLL's are also not included in the
> SDK, for example zlib.dll. Should I manually add such files also?
> And how do I manually add files to my SDK?
>
>