Re: Linker Error



You're not building the same set of things as the build system in Platform
Builder is. You're not building a library of your own functions, right?
You should be able to just link with the hidparse.lib. Where are you
getting it from? It should be in the
PBWorspaces\<yourproject>\wince500\cesysgen\oak\lib\<processor>\<debugtype>.

Paul T.

"kaza" <kaza@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:043543E5-C5DD-400C-A19C-A448F61E9E18@xxxxxxxxxxxxxxxx
Paul,
Thanks for your reply. I'm not sure though if I'm linking it the right
way,
and I still get that error. Basically I went to the sources file in my
eMbedded Visual C++ project, and under TARGETLIBS, I added
=$(OWNSTATICLIB)
$(MY_PATH)\hidparse.lib
where $(MY_PATH) was the path to the file under the WINCE00\PBWORKSPACE,
and
that didn't fix it How do I link it?



"Paul G. Tobey [eMVP]" wrote:

I think you're misunderstanding how the build works. That library file,
hidparse_lib.lib is the implementation file for a DLL called
hidparse.dll,
that is the code inside that DLL, not an import library for other DLLs to
use.

If you take a look at \PUBLIC\COMMON\CESYSGEN\MAKEFILE, you'll see how
the
HID DLLs that are built by platform builder are linked. That's the
pattern
you want to follow. So, for example kbdhid.dll is built using the
following
library set:

@set TARGETLIBS=$(OWNSTATICLIB)
$(SG_OUTPUT_OAKLIB)\hidparse.lib

OWNSTATICLIB is going to be kbdhid_lib.lib and, as you see, they're
linking
with the import library for the hidparse.dll file.

Paul T.

"kaza" <kaza@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:4A49E9EB-49B9-4158-A188-F266B4CBD970@xxxxxxxxxxxxxxxx
By the way I got the same linker error and more when I tried to build
the HID examples that are provided with Platform Builder, so that rules
out that it's a coding problem.
Still waiting for suggestions!


"kaza" wrote:

Hi,

I am writing an HID client driver for a device, and when I build in
eMbedded Visual C++ 4.0, I get this linker error:

error LNK2019: unresolved external symbol _HidP_GetCaps referenced in
function _HIDDeviceAttach

I started from the HID examples provided with platform builder 5.0,
and
I have HIDPI.H included, and I have the
"C:\WINCE500\PUBLIC\COMMON\OAK\LIB\X86\DEBUG" library path included
for
the "Hidparse_lib.lib" library. What am I missing?

Thanks in advance!







.



Relevant Pages

  • Re: ws2.lib size
    ... using the Visual Studio 2005 with Windows CE 6.0 Platform ... the emulator to connect to the host network. ... This is rather what I'd expect, as it's just a set of stubs for a DLL. ... Platform Builder, ...
    (microsoft.public.windowsce.platbuilder)
  • Re: ActiveX DLL and Borland C++ Builder
    ... Everything runs like water using Visual Studio. ... An ActiveX Dll comes with a built-in Type Library. ... VB does not normally produce an MIDL-generated header. ... it is possible C++ Builder ...
    (microsoft.public.vb.com)
  • Re: Bootloader for Da Vinci
    ... > there is any activity from platform builder side when it ... receiving a valid bootme though. ... is it a valid MAC address i.e. you haven't set ...
    (microsoft.public.windowsce.platbuilder)
  • Re: (CoreCon) 11:58:32 04/17/2007 Central Daylight Time: Failed to co-create service host!
    ... Fortunately, this has become somewhat less of a problem in CE6, as Platform ... Builder 6 is a plug-in for Visual Studio 2005, which gets a lot of testing. ... connection download errors as following: ... I need to debug WinCE build ...
    (microsoft.public.windowsce.embedded)
  • Re: Telnet server Windows CE 6
    ... I created a new os project using an industrial device template in platform ... builder instead of the gateway device. ...
    (microsoft.public.windowsce.embedded)