Hmmm, I found details on the net that recommended adding an [Environment64] section, which we did.
I don't seem to have VCINSTALLDIR or WindowsSdkDir variables on my system :/ .. that said, VC obviously works on my machine.
It also seems potentially problematic that a variable would define a single install directory, since it's pretty common that programmers have multiple versions of VS on their machines.
I have VS2010 and VS2012 on my machine. Simon had VS2012 and VS2013.
I was also thinking it might be a mistake to keep phobos64.lib in the same folder as the 32bit omf libs. If paths are wrong, the link errors will only be understood by a programmer who understands compilers and lib/object formats in depth.
Perhaps you should put them in a parallel lib64 directory, and hook that up in [Environment64] (I did that on my machine while trying to isolate problems and wort out where paths were coming from)?
I reckon you should look into hooking up DirectX SDK patahing by default too since it's so common for basically any multimedia app.