Why does the visual C++ compiler generate an unresolved reference to _vasprintf?
C / C++ / MFC
1
Posts
1
Posters
0
Views
1
Watching
-
I have a project that needs to be compiled on multiple hosts, some of which provide an implementation of vasprintf and some that do not. I don't see a declaration of vasprintf() in the Visual C++ 2015 cstdio include file, so I assume that it does not contain a definition of that function, yet the visual C++ compiler generates a call to _vasprintf from the call to vasprintf() in my source code. The linker then emits an unresolved reference to _vasprintf error. Is this a visual C++ bug? Does visual C++ declare its implementation of vasprintf in a different include file?