Comment 18 for bug 376801

> Sorry, why would that solve the problem?

Because we're having problems with DLLs that the pre-built Mixxx dependencies depend on, evidenced by the fact that their versions are VS 2005, and I'm using VS 2008.

> I thought we could just delete the .manifest file and be done with it.

I didn't understand why it helped before, but I have a good idea now, having read the first article I linked to above (look toward the bottom of the article.) Last time, we were carrying around a manifest for an old/wrong version of a DLL, so removing it helped, at least on systems that had the correct version installed (or we just didn't need that DLL at all anymore.)

This time, at least right now, according to the mixxx.exe.manifest, for win32, we need a particular version of msvcrt80.dll. Win64 wants a debug and runtime build of that same version of that same DLL as well as msvcrt90.dll.

So we have a few choices: 1) for each of the x86 and x64 version of Mixxx, read the mixxx.exe.manifest files and make sure to include the listed versions of the DLLs (and _their_ manifest files, so Windows will try them first) in the Mixxx install packages, 2) don't use any pre-built dependencies but build them ourselves, making sure to specify to embed the manifest in the DLL (we may still need to include msvcrt90.dll however,) or 3) Forget all this crap and move to a MinGW build process in earnest.