bmk icon indicating copy to clipboard operation
bmk copied to clipboard

Published 20 hours ago • verified publisher icon bmx-ng

[Windows] .manifest files are architecture-specific

Open GWRon opened this issue 5 years ago • 2 comments

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

GWRon avatar May 07 '19 08:05 GWRon

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.

woollybah avatar May 09 '19 06:05 woollybah

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.

GWRon avatar May 09 '19 06:05 GWRon