Error LNK2019: unresolved external symbol __vsnwprintf_s referenced in function _stringvprintfworkerw@20

Question

1.00/5 (1 vote)

See more:

odbccp32.lib(dllload.obj) : error LNK2019: unresolved external symbol __vsnwprintf_s referenced in function _StringVPrintfWorkerW@20
.\Debug/RegConvert.exe : fatal error LNK1120: 1 unresolved externals
NMAKE : fatal error U1077: '-----path-----\VC\bin\link.exe' : return code '0x460'

What I have tried:

i tried adding legacy_stdio_definitions.lib to the linker input.it is building using visual studio but not with command line.i am using 'nmake'

Posted 10-Aug-17 20:18pm

Naveen_vemuri

Add a Solution

Comments

Jochen Arndt 11-Aug-17 2:59am

You are not linking the CRT (C Run Time) library or linking very old version.
In the latter case check which library directories are included when using nmake.

Naveen_vemuri 11-Aug-17 3:33am

also i need difference between nmake and msbuild?can we use msbuild instead of nmake to build?and in msbuild we use /v for verbose .in nmake to get detailed information what should we use

Jochen Arndt 11-Aug-17 3:44am

nmake will itself mainly call other commands. So you usually have to pass the verbose option to those commands.

Because it is a linker related problem it, it would be sufficient to make the link calls verbose. Try to get the list of library files linked by your namke file.

Regarding the CRT pathes and libraries see
https://blogs.msdn.microsoft.com/vcblog/2015/03/03/introducing-the-universal-crt/
This has changed with VS 2015 so that it may be the source of your problem if the project was created with an older version.

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)