Need libmfx as MultiThreaded Debug /MTd

Need libmfx as MultiThreaded Debug /MTd

All my projects compile with the static runtime library (NOT  the dynamic DLL version).

When i build the release version i have no problems using the libmfx.lib, but in the debug version there is a conflict in the runtime librarys:

VC projects use the libcmtd.lib, while the libmfx.lib references the libcmt.lib.

Looks like that:

  • 2>libcmt.lib(invarg.obj) : error LNK2005: __call_reportfault already defined in LIBCMTD.lib(invarg.obj)
  • 2>libcmt.lib(invarg.obj) : error LNK2005: __get_invalid_parameter_handler already defined in LIBCMTD.lib(invarg.obj)
  • ...

Same problem appears, if i use the dynamic version (libfmxmd.lib).

Every time I compile my main projects with the debug runtime i get the conflict between libmfx (no debug runtime, libcmt.lib) and VC-Projects (debug runtime, libcmtd.lib)

The only solution to solve this problem seems, that Intel adds the debug-runtime version of libmfx into the lib-path  too, or is there any other workaround (i feel very uncomfortable with specifying "ignore libraries:libcmt"  in the debug version, this is a very dirty trick)

3 posts / 0 new
Last post
For more complete information about compiler optimizations, see our Optimization Notice.

Hi,

One option is to build the debug library yourself.  The code/project is included in the <installdir>\opensource\mfx_dispatch folder (or Media SDK 2013 R2).

-Tony

The "ignore libraries:" option is for precisely this type of issue. It's much simpler for most projects to allow the default libraries, and then exclude any causing conflicts, rather than specifying "Ignore all default libraries", and then have to specify them all on the command line.

Leave a Comment

Please sign in to add a comment. Not a member? Join today