cannot link *.obj file produced from *.asm having beeen generated by MSVisual Studio 2017 C++

  • Thread starter Thread starter AAA BBB XXX YYY
  • Start date Start date
A

AAA BBB XXX YYY

Guest
Hello, everybody, I am a student and I tried to get *.asm code by compilation C++ project in MS Visual Studio 2017. ASM code was got OK. It also was compiled OK with ml.exe (MASM32). But I stuck on linking: there were multiple unresolved externals with very long and pretentious names like: "__imp____stdio_common_vfprintf", "__imp____stdio_common_vfscanf" and so on. My source C code is simple: it opens file, read it (vfscanf), and then writes (vprintf) to another file. It also uses new() and delete() functions (they are also unresolved!). How to fix this problem? I did not write even a letter in this asm source code - all was completely generated by MS VC++ 2017. So, why it cannot resolve it's own code? it is srange. Pls help...

Continue reading...
 
Back
Top