0
0

Hey all. Please help… I hate warnings, and can’t seem to get rid of these:

1>fmodex_vc.lib(fmodex.dll) : warning LNK4006: _FMOD_File_SetDiskBusy@4 already defined in fmod_event.lib(fmod_event.dll); second definition ignored
1>fmodex_vc.lib(fmodex.dll) : warning LNK4006: __imp__FMOD_File_SetDiskBusy@4 already defined in fmod_event.lib(fmod_event.dll); second definition ignored
1>fmodex_vc.lib(fmodex.dll) : warning LNK4221: no public symbols found; archive member will be inaccessible
1>fmodex_vc.lib(fmodex.dll) : warning LNK4006: _FMOD_File_GetDiskBusy@4 already defined in fmod_event.lib(fmod_event.dll); second definition ignored
1>fmodex_vc.lib(fmodex.dll) : warning LNK4006: __imp__FMOD_File_GetDiskBusy@4 already defined in fmod_event.lib(fmod_event.dll); second definition ignored
1>fmodex_vc.lib(fmodex.dll) : warning LNK4221: no public symbols found; archive member will be inaccessible

I’m using VC2005, and in my code, I’ve been using the C++ api to make calls into FMOD. Tonight, I added a #include "fmod_event.h" and it complained that I did so below my #include "fmod.hpp", so I moved it above and got rid of the compile complaints.

However, it looks like the .lib files (fmodex_vc and fmod_event) each declare FMOD::File separately, so linking both of them spews a lot of warnings. I can’t get rid of either lib, though.

Is there a solution to this that I’m not seeing?

Thanks,
JH

  • You must to post comments
0
0

you should not be linking fmod_event lib AND fmod_vc.lib because fmod_event already has a dependency on fmod_vc and loads the dll automatically for you.

  • You must to post comments
0
0

Hmm. This is not working for me. Just to be clear, I’m building for PC with VC2005. I have a sound library that I’ve configured to specify additional dependencies fmod_event.lib. When I link against my library, it definitely does not pull in fmodex_vc.lib as you say it should, because I get errors from missing functions.

Also, if I do not put the library dependency in my own lib, but rather put it in my executable–so my .exe builds by including fmod_event.lib directly, I still have this issue.

I can get either way working by manually including both the event lib and fmodex_vc, though I get a number of function redeclaration warnings.

Any ideas how I can fix this? My opinion, for what it’s worth: libs should not depend on other libs. It’s not any more convenient to include one rather than two, and it’s less obvious what’s going on for the developer.

Thanks,
JH

  • You must to post comments
0
0

I get the same number of warnings, actually. I seem to be having the exact same problem. I link with both fmodex_vc.lib and fmod_event.lib. If I don’t link with both, the project fails to compile.

If it’d be helpful, I can post the warnings generated.

  • You must to post comments
0
0

[quote="Tarviathun":3r10ugb1]I link with both fmodex_vc.lib and fmod_event.lib. If I don’t link with both, the project fails to compile.[/quote:3r10ugb1]

we are also using FMOD::System object which requires fmodex_vc.lib to link properly.

  • You must to post comments
0
0

I’ve still yet to find a way to remove the linker warnings, and I get about 25 of them. Does anyone have any ideas about how to solve this issue?

  • You must to post comments
Showing 5 results
Your Answer

Please first to submit.