Hello,

When adding the 'SIP for Large Screens' in a WinCE 5 Platform Build, I get
the following error during Platform Build (build.log) :
coredll.def : error LNK2001: unresolved external symbol SipEnumIM
coredll.def : error LNK2001: unresolved external symbol SipGetCurrentIM
....
coredll.def : error LNK2001: unresolved external symbol SipStatus

I checked and added Catalog Item Dependencies and found nothing wrong.

Any ideas ?

Thanks in advance,

Joost.

RE: Problem adding SIP driver by LucaCalligaris

LucaCalligaris
Tue May 16 07:36:03 CDT 2006

Probably coredll.dll has been linked before you added SIP feature?
try a 'sysgen' with 'clean before building' option selected



"JGW" wrote:

> Hello,
>
> When adding the 'SIP for Large Screens' in a WinCE 5 Platform Build, I get
> the following error during Platform Build (build.log) :
> coredll.def : error LNK2001: unresolved external symbol SipEnumIM
> coredll.def : error LNK2001: unresolved external symbol SipGetCurrentIM
> ....
> coredll.def : error LNK2001: unresolved external symbol SipStatus
>
> I checked and added Catalog Item Dependencies and found nothing wrong.
>
> Any ideas ?
>
> Thanks in advance,
>
> Joost.

RE: Problem adding SIP driver by JGW

JGW
Tue May 16 09:12:02 CDT 2006

OK, this solved my problem. Thanks.
I guess it's a good idea to always 'clean build' after adding components
with a lot of dependencies ?

Thanks again,

Joost.


"Luca Calligaris" wrote:

> Probably coredll.dll has been linked before you added SIP feature?
> try a 'sysgen' with 'clean before building' option selected
>
>
>
> "JGW" wrote:
>
> > Hello,
> >
> > When adding the 'SIP for Large Screens' in a WinCE 5 Platform Build, I get
> > the following error during Platform Build (build.log) :
> > coredll.def : error LNK2001: unresolved external symbol SipEnumIM
> > coredll.def : error LNK2001: unresolved external symbol SipGetCurrentIM
> > ....
> > coredll.def : error LNK2001: unresolved external symbol SipStatus
> >
> > I checked and added Catalog Item Dependencies and found nothing wrong.
> >
> > Any ideas ?
> >
> > Thanks in advance,
> >
> > Joost.