Re: Help on coredll.dll

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance



You're looking at this all wrong. There is no single SDK for any Windows CE
device of any version. I have several devices that we sell. One of them
has a display, keyboard, audio, etc., etc. The other has no display, no
keyboard, no windowing system, no audio, etc. You can't expect the same SDK
to work for those devices. That's why every device type has a *separate*
SDK for eVC.

Some devices have common API sets defined by MS. Pocket PC is an example.
All Pocket PC devices can use any of the calls in the Pocket PC SDK
(installed separately from eVC). However, that doesn't mean that *any*
other device can use the Pocket PC SDK. Since Windows CE is highly modular,
any number of things might be missing or things that the Pocket PC doesn't
have might be in the other device.

The Standard SDK, which is named poorly, is a set of APIs which a device
maker can decide to support *or not support*. If the device supports it,
any API in the Standard SDK will work on the device. However, that does
*not* mean that all of the APIs on the device are supported by the Standard
SDK. If you want to use any of those other APIs, you *must* install and use
the SDK for the actual device.

If you would answer my question from several messages back about WHAT
DEVICE, we'd already have this problem solved!

Paul T.

"Alex" <xia_alex_9542@xxxxxxxxxxxxxx> wrote in message
news:emjCjPSRFHA.3672@xxxxxxxxxxxxxxxxxxxxxxx
>I have compiled the code using eVC 3.0 and have no problem, but I can not
> use eVC 4.0. So I guess I need an extra lib for SIP support in cVC 4.0.
> But
> where I can get that lib?
>
> Thanks for help.
>
> Alex
>
> "Alex" <xia_alex_9542@xxxxxxxxxxxxxx> wrote in message
> news:ei$nEESRFHA.3628@xxxxxxxxxxxxxxxxxxxxxxx
>> Yes, I use standard SDK and try to compile for ARM device. Under standard
>> SDK ARMV4 directory, the header "sipapi.h" is provided, but I guess there
> is
>> no implementation for it. So if I try to compile for ARM device, I need
>> to
>> get a lib to suppout SIP. This does not sound right.
>>
>> Please provide some documentation so I can fix this problem. Thanks.
>>
>> Alex
>>
>> "Paul G. Tobey [eMVP]" <ptobey no spam AT no instrument no spam DOT com>
>> wrote in message news:OiE%23J3RRFHA.2252@xxxxxxxxxxxxxxxxxxxxxxx
>> > After slight modifications to make your code actually compilable
> (where's
>> > DlgProc?), etc., I can build this fine without adding *any* extra .lib
>> files
>> > to the link specification. I'm targeting our device, which *does* have
>> SIP
>> > support in it. I say that yours doesn't or that you're targeting the
>> > Standard SDK, WHICH DOES NOT REQUIRE SIP SUPPORT!
>> >
>> > Paul T.
>> >
>> > "Alex" <xia_alex_9542@xxxxxxxxxxxxxx> wrote in message
>> > news:OJ7$8URRFHA.2252@xxxxxxxxxxxxxxxxxxxxxxx
>> > > The code is straightforward,
>> > >
>> > > #include "stdafx.h"
>> > > #include <sipapi.h>
>> > >
>> > > int WINAPI WinMain( HINSTANCE hInstance,
>> > > HINSTANCE hPrevInstance,
>> > > LPTSTR lpCmdLine,
>> > > int nCmdShow)
>> > > {
>> > > hInst = hInstance;
>> > > SipShowIM(SIPF_ON);
>> > > DialogBox(hInst, MAKEINTRESOURCE(IDD_STARTUP), NULL, DlgProc);
>> > > return 0;
>> > > }
>> > >
>> > > And the error is
>> > > Compiling...
>> > > myapp.cpp
>> > > Linking...
>> > > myapp.obj : error LNK2019: unresolved external symbol SipShowIM
>> referenced
>> > > in function WinMain
>> > > ARMV4Rel/myapp.exe : fatal error LNK1120: 1 unresolved externals
>> > > Error executing link.exe.
>> > >
>> > > I think the lib reference is not right, but I just can not find
>> SipShowIM
>> > > in
>> > > coredll.lib.
>> > >
>> > > Thanks for your help.
>> > >
>> > > Alex
>> > >
>> > > "Steve Maillet (eMVP)" <nospam1@xxxxxxxxxxxxxxxxxxxxxxx> wrote in
>> message
>> > > news:%23WPnMCRRFHA.3704@xxxxxxxxxxxxxxxxxxxxxxx
>> > >> post the offending code sections and the EXACT error message.
>> > >>
>> > >> --
>> > >> Steve Maillet
>> > >> EmbeddedFusion
>> > >> www.EmbeddedFusion.com
>> > >> smaillet at EmbeddedFusion dot com
>> > >>
>> > >>
>> > >
>> > >
>> >
>> >
>>
>>
>
>


.



Relevant Pages

  • Re: At a loss for development environment
    ... > Fully compatible with Microsoft SDK for Pocket PC's; Symbol SDK ... >available to support bar code scanning ...
    (microsoft.public.pocketpc.developer)
  • Re: Standard SDK
    ... your device *does* have the Standard SDK set of components in it and if you ... compile against the Standard SDK, your program will run on the device. ... there are no applications that run on every ARMx platform of Windows CE; ... Commercial applications generally target Pocket PC SDKs. ...
    (microsoft.public.windowsce.platbuilder)
  • Re: XP Taskbar problem
    ... At the time I posted I had two samples - Chad's tutorial and the April SDK ... and now my project runs at full screen without any flicker. ... support starting in full screen correctly mouse support in multimonitor ... Check startup code and see if window client has dimensions of your screen ...
    (microsoft.public.win32.programmer.directx.managed)
  • Re: Unsupported Functions and Objects w/ new SDKs from Visual Stud
    ... use VS2005 to continue to support existing applications for older platforms. ... solution properties to use paths to the right SDK, ... should compile in the newer one using the same SDK. ... > You must have created a C++ MFC Desktop app. ...
    (microsoft.public.pocketpc.developer)
  • Re: directx samples
    ... DX9 requires DX7 level DDI display drivers. ... level of driver support, you wont get DX9 interface support. ... have the SDK set up properly. ...
    (microsoft.public.win32.programmer.directx.graphics)