I know where MY paths are coming from, thanks, but i dont know where HIS paths are coming from
. I am using the macros and they expand to the proper location for me. I guessed he hardcoded the paths to wrong values, because he is already using a very strange compiler setup with relative paths to compiler internal directories as you can see from the build log (and i remember him from another thread where he displayed his strange compiler setup).
And yes, you have to use the mt.exe from the SDK that you are linking against, and no, the manifest should get created automatically, at least thats what MSDN says. However it doesnt hurt to specify /MANIFEST explicit in the linker options to enable it. And the default name for it is indeed <full name with extension>.manifest, most important use of the manifest is to enable proper UI dlls or your application looks like Windows 3.1.