Hi All,
I was using the Windows USBD_ParseConfigurationDescriptor API (Winddk 7600)
and found that I was getting a linker error. My file is a .C file and I was
getting the error:
*unresolved external found _imp_UsbParseConfigurationDescriptor@28 refernced
in StatrDevice@8.*
I tried the TARGETLIB=$DDK_BUILD_PATH\lib\usbd.lib, but still no avail.
Can anyone help me in this direction…
Highly appreciate your inputs
Abdul
Use this instead
TARGETLIBS=$(DDK_LIB_PATH)\usbd.lib
Note the S in TARGETLIBS and the $(xxx), not $xxx syntax. BTW, you have a misspelling, it should be StartDevice, not StatrDevice. Why are you writing a WDM driver instead of using KMDF?
d
From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of Abdul Qader
Sent: Tuesday, November 09, 2010 7:54 PM
To: Windows System Software Devs Interest List
Subject: [ntdev] USBD_ParseConfigurationDescriptor
Hi All,
I was using the Windows USBD_ParseConfigurationDescriptor API (Winddk 7600) and found that I was getting a linker error. My file is a .C file and I was getting the error:
unresolved external found _imp_UsbParseConfigurationDescriptor@28 refernced in StatrDevice@8.
I tried the TARGETLIB=$DDK_BUILD_PATH\lib\usbd.lib, but still no avail.
Can anyone help me in this direction…
Highly appreciate your inputs
Abdul
— NTDEV is sponsored by OSR For our schedule of WDF, WDM, debugging and other seminars visit: http://www.osr.com/seminars To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer
Abdul Qader wrote:
I was using the Windows USBD_ParseConfigurationDescriptor API (Winddk
7600) and found that I was getting a linker error. My file is a .C
file and I was getting the error:
/unresolved external found _imp_UsbParseConfigurationDescriptor@28
refernced in StatrDevice@8./I tried the TARGETLIB=$DDK_BUILD_PATH\lib\usbd.lib, but still no avail.
Can anyone help me in this direction…
I’m guessing you typed all of that by hand instead of cutting and
pasting, because there are at least 4 typographical errors there, any
one of which would have caused your failure. Did you notice that the
entry point in the error is different from the one in the subject line?
Next time, use cut and paste to show us the EXACT error message, and
include a copy of your sources files. Then, we can offer you reasonable
advice.
–
Tim Roberts, xxxxx@probo.com
Providenza & Boekelheide, Inc.
Tim,
Sorry for the typos…
Anyways Doron’s suggestion worked…
Thanks for the help…
Abdul
On Wed, Nov 10, 2010 at 11:09 PM, Tim Roberts wrote:
> Abdul Qader wrote:
> >
> > I was using the Windows USBD_ParseConfigurationDescriptor API (Winddk
> > 7600) and found that I was getting a linker error. My file is a .C
> > file and I was getting the error:
> > /unresolved external found _imp_UsbParseConfigurationDescriptor@28
> > refernced in StatrDevice@8./
> >
> > I tried the TARGETLIB=$DDK_BUILD_PATH\lib\usbd.lib, but still no avail.
> >
> > Can anyone help me in this direction…
>
> I’m guessing you typed all of that by hand instead of cutting and
> pasting, because there are at least 4 typographical errors there, any
> one of which would have caused your failure. Did you notice that the
> entry point in the error is different from the one in the subject line?
>
> Next time, use cut and paste to show us the EXACT error message, and
> include a copy of your sources files. Then, we can offer you reasonable
> advice.
>
> –
> Tim Roberts, xxxxx@probo.com
> Providenza & Boekelheide, Inc.
>
>
> —
> NTDEV is sponsored by OSR
>
> For our schedule of WDF, WDM, debugging and other seminars visit:
> http://www.osr.com/seminars
>
> To unsubscribe, visit the List Server section of OSR Online at
> http://www.osronline.com/page.cfm?name=ListServer
>