This happened when I was transferring code from one machine to another, using the same version of both VC++ and the FMOD api.
After the transfer, I tried compiling and linking the project and I got a couple of “unresolved externals”, namely with FSOUND_Stream_Open and FSOUND_Stream_SetMode.
I checked and doublechecked the presence of fmodvc.lib in my project and all library paths. In fact, I use many more functions from the FMOD lib and only these 2 unresolved externals show up. I’ve tried everything and double-checked all project settings from my old machine and can’t reach any viable conclusions. I’ve been using FMOD for more than 2 years now and I’ve never before ran into this problem.
How is it possible for the linker to process the fmodvc.lib and fail to resolve the FMOD_Stream_Open funcs… I’m using multithreaded DLL code generation options and everything else that i’ve used during my FMOD development time…
I would really appreciate an explanation since I’m practically going mad with the situation.
- Kodachi_Garou asked 14 years ago
Thanks for the tip! I had suspected as much even before I posted the message, but I had done a thorough search of all library paths but I couldn’t find any stray .lib packages.
However, after seeing your reply I became more resolute and I performed a full search of my hard-drives for whatever copies of fmodvc.lib that I could find. I ended up finding my mismatch: lying still on the MSVC 6.0 internal libraries directory. I don’t know how it got there, but I sure hope it isn’t some sort of caching system of MSVC…
Anyway, thanks again for the support!
- Kodachi_Garou answered 14 years ago
Please login first to submit.