[Windows] .manifest files are architecture-specific

[GWRon]

BMK allows to provide a "binaryname.exe.manifest" which get's autoincluded.
Yet these manifest files are architecture (x86, x64) specific.

This means BMK should check FIRST for:
binaryname.exe.x86_or_x64.manifest
and then for the common named
binaryname.exe.manifest

[woollybah]

I don't think bmk does anything with user-provided manifest files.
Windows can load a manifest in this format when the app is executed.

[GWRon]

I thought BMK brings the manifest data into the executable (make.bmk + linker stuff)?
These .manifest files contain architecture specific configurations - while the binaries are not getting the architecture "appended".
program.bmx becomes program.exe - on 32 and on 64 bit.