0
0

we are using VS2005 and are currently doing transition to precompiled headers and static linkage. i keep getting the following warnings (which are not critical, but never the less :) ):

fmodex_vc.lib(fmodex.dll) : warning LNK4006: _FMOD_File_SetDiskBusy@4 already defined in fmod_event.lib(fmod_event.dll); second definition ignored

any ideas what i am doing wrong?

  • You must to post comments
0
0

fmod_event already links to fmodex so you dont need to link to it again.

  • You must to post comments
0
0

well, if i link it only against fmod_event.lib, the linker fails with unresolved external symbols on:
FMOD::System::getCPUUsage
FMOD::System::getChannelsPlaying
etc…

after adding fmodex_vc.lib, linker does it’s job, but we are back to 4006 warning.

  • You must to post comments
0
0

Same issue here, I live with the warnings (thinks like add_dsp etc)

  • You must to post comments
0
0

ok fmod’s examples link to both, how are yours different to those examples?
There are no warnings.

  • You must to post comments
0
0

basic overview of our setup:
we have created a fmod wrapper project, which uses our interface. it is using a precompiled header and builds into a static library, against which main executable project is linked.

will try to find the diff between fmod examples and our projects…

  • You must to post comments
Showing 5 results
Your Answer

Please first to submit.