• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Answers 1 answer
  • Subscribers 33 subscribers
  • Views 1215 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

Build Error on WDK 7600

shizunori
Prodigy 250 points

Hi

When I build a TUSBWINVCP driver for Windows7 64bit, there is following error.

WDK I use is WDK 7600.

Would you advise how can I solve this error?

1>link : error LNK2001: unresolved external symbol WinMainCRTStartup
1>c:\works\xxxxxxx\xxx\xxxxxxxxx\xxxxxxxxxxxxxxxx\xx-xxxxxxxxx\uminst.obj : error LNK2001: unresolved external symbol _wcsnicmp
1>c:\works\xxxxxxx\xxx\xxxxxxxxx\xxxxxxxxxxxxxxxx\xx-xxxxxxxxx\util.obj : error LNK2001: unresolved external symbol vsprintf
1>c:\works\xxxxxxx\xxx\xxxxxxxxx\xxxxxxxxxxxxxxxx\xx-xxxxxxxxx\util.obj : error LNK2001: unresolved external symbol wcstok
1>c:\works\xxxxxxx\xxx\xxxxxxxxx\xxxxxxxxxxxxxxxx\xx-xxxxxxxxx\uninst.obj : error LNK2001: unresolved external symbol sprintf
1>c:\works\xxxxxxx\xxx\xxxxxxxxx\xxxxxxxxxxxxxxxx\xx-xxxxxxxxx\uninst.obj : error LNK2001: unresolved external symbol swprintf
1>c:\works\xxxxxxx\xxx\xxxxxxxxx\xxxxxxxxxxxxxxxx\xx-xxxxxxxxx\uninst.obj : error LNK2001: unresolved external symbol _wfindfirst
1>c:\works\xxxxxxx\xxx\xxxxxxxxx\xxxxxxxxxxxxxxxx\xx-xxxxxxxxx\uninst.obj : error LNK2001: unresolved external symbol wcsncpy
1>c:\works\xxxxxxx\xxx\xxxxxxxxx\xxxxxxxxxxxxxxxx\xx-xxxxxxxxx\uninst.obj : error LNK2001: unresolved external symbol _wfindnext
1>c:\works\xxxxxxx\xxx\xxxxxxxxx\xxxxxxxxxxxxxxxx\xx-xxxxxxxxx\uninst.obj : error LNK2001: unresolved external symbol _findclose
1>c:\works\xxxxxxx\xxx\xxxxxxxxx\xxxxxxxxxxxxxxxx\xx-xxxxxxxxx\objfre_win7_amd64\amd64\usbinst.exe : error LNK1120: 10 unresolved externals

Regards,

KAZU

 

  • 0
    TI__Intellectual 2170 points

    Hi Kazu,

    Did you modified our Windows VCP source code? If yes, then the compilation errors might be related to the changes you performed in the code.

    I verified our default VCP source code and I had no compilation errors. I made a Win-7 x64 free build. See attached screenshot.

    Also which command are you using to compile? commonly it's "build -cZ"...

    I suggest using this command and copying the source code in a shorter path like "C:\VCPsource\usbuart\"

    By the way I compiled our latest source code v3.2. Which source code are you using?

     

  • 0 in reply to Ismael Duron10236
    Prodigy 250 points

    Hello

    I tried to use a shorter path, but I could not compile completely.
    Source code version I used is V3.2.
    There was the same error when I built for Windows 7, XP and VISTA.

    The reason why I compile this time is that I want to change the file name of installer. 
    I worry that some problems will occur, when I connect two different USB device which have different driver but the same installer file name, to the same PC.
    If I use the default file name for USB device, it is possible to conflict to the same file name, I think.
    Am I right?
    Don't I have to worry about this case?
    Would you advise again for this subject?

    Thank you very much for your continuous support.

    Regards,

    KAZU

  • 0 in reply to shizunori
    Prodigy 250 points

    Hello,

    I have checked source code version, and found a serious mistake in it.
    Then I have updated source code to v3.2 as your advice, and compile error has solved.

    I thank for your kind support very much.

    Best Regards,

    KAZU