linker error

i have a wince 4.2 bsp which i need to migrate in wince 5.0.I did alll
sucessfull steps as defined in wince 5.0 msdn that are necessary to migrate
,build during build and sysgen i get error as follows
BUILD: [01:0000000032:ERRORE] ceddk.def : error LNK2001: unresolved external
symbol BusIoControl
BUILD: [01:0000000033:ERRORE] ceddk.def : error LNK2001: unresolved external
symbol BusTransBusAddrToStatic
BUILD: [01:0000000034:ERRORE] ceddk.def : error LNK2001: unresolved external
symbol BusTransBusAddrToVirtual
BUILD: [01:0000000035:ERRORE] ceddk.def : error LNK2001: unresolved external
symbol CloseBusAccessHandle
BUILD: [01:0000000036:ERRORE] ceddk.def : error LNK2001: unresolved external
symbol CreateBusAccessHandle
BUILD: [01:0000000041:ERRORE] ceddk.def : error LNK2001: unresolved external
symbol DDKPwr_RequestLevel
E:\WINCE500\platform\28NOV_TI_BSP1050\lib\MIPSII\debug\ceddk.lib : fatal
error LNK1120: 20 unresolved externals

this all error are in file ceddk.h which is in public folder I dont know
what to do in this case
please help me out in this
waiting for the reply

Tom
Wed Nov 30 07:31:13 CST 2005

These functions were all added to ceddk.dll in Windows CE 5.0. They were
added to the default CEDDKs, but it seems your platform has its own
implementation of ceddk, so you will have to add these functions yourself.
You can see the source for these file in the
WINCE500\PUBLIC\COMMON\OAK\DRIVERS\CEDDK folder.

Tom Gensel (eMVP)

Sangel
Thu Dec 01 05:17:02 CST 2005


hi,
thanks for your reply

I didnt get you but yes our platform has own implementation of ceddk
I didnt get what u said about "so you will have to add these functions
yourself."
can u eloborate in detail




"Tom Gensel (eMVP)" wrote:

> These functions were all added to ceddk.dll in Windows CE 5.0. They were
> added to the default CEDDKs, but it seems your platform has its own
> implementation of ceddk, so you will have to add these functions yourself.
> You can see the source for these file in the
> WINCE500\PUBLIC\COMMON\OAK\DRIVERS\CEDDK folder.
>
> Tom Gensel (eMVP)
>
>
>

Bruce
Thu Dec 01 08:33:45 CST 2005

What Tom is saying is that your CEDDK needs to be updated to support CE 5.0.
In CE 5.0 some new functions were added to the CEDDK, which your cloned
CEDDK for 4.2 does not have. You have some dependencies on these new
functions, if for no other reason you are using a new ceddk.def file.

You are now responsible for determining which functions these are and adding
them to your CEDDK. That is the cost of cloning public code, not that it is
bad just that it isn't always free.

--
Bruce Eitman (eMVP)
Senior Engineer
beitman AT applieddata DOT net

Applied Data Systems
www.applieddata.net
An ISO 9001:2000 Registered Company
Microsoft WEP Gold-level Member

"Sangel" <Sangel@discussions.microsoft.com> wrote in message
news:D0B12B1E-FE87-49C5-9107-2918C5FD66D8@microsoft.com...
>
> hi,
> thanks for your reply
>
> I didnt get you but yes our platform has own implementation of ceddk
> I didnt get what u said about "so you will have to add these functions
> yourself."
> can u eloborate in detail
>
>
>
>
> "Tom Gensel (eMVP)" wrote:
>
>> These functions were all added to ceddk.dll in Windows CE 5.0. They were
>> added to the default CEDDKs, but it seems your platform has its own
>> implementation of ceddk, so you will have to add these functions
>> yourself.
>> You can see the source for these file in the
>> WINCE500\PUBLIC\COMMON\OAK\DRIVERS\CEDDK folder.
>>
>> Tom Gensel (eMVP)
>>
>>
>>