🚀 go-pugleaf

Kris wrote:
> This seems like a never ending story of adding new header files (and 
> having those newly included header files cause other errors). For now I've 
> commented out GetCollectionDescription in order to get things compiled 
> (but the possibility exists that I'm going to still need it later on).

This is sometimes what one has to do to get code written from MSVC to work 
in BCB.


> (2) Hid API calls do not link
> E.g. HidD_GetAttributes(DeviceHandle,&Attributes); compiles fine but fails 
> to link with following error:
> [ILINK32 Error] Error: Unresolved external '__stdcall 
> HidD_GetAttributes(void *, _HIDD_ATTRIBUTES *)' referenced from 
> C:\DOCUMENTS AND SETTINGS\KRIS\MY DOCUMENTS\RAD 
> STUDIO\PROJECTS\USB_HID\DEBUG_BUILD\USB_IO_UNIT.OBJ
>
> For now I've worked around the problem by using GetProcAddress() to 
> extract the location of the function I need from HID.DLL. This works fine, 
> but it sure would be nice if I wouldn't have to do this for every HID 
> function call I want to use.

Use implib on the HID.dll file to get a BCB-compatible .lib file that will 
handle all these imports for you.


> Basically I'm wondering how one is able to efficiently and correctly use 
> the DDK header files from Visual studio in Builder 2007 ?

Like Dennis Jones said, you'll probably find that you need to use VS to 
develop device drivers. I think that there are some limitations to the BCB 
linker and/or compiler that prevent it from being able to create device 
drivers.

Jon