[Windows] .manifest files are architecture-specific

bmx-ng / bmk

The enhanced BlitzMax build program.

zlib License

28 stars 13 forks source link

[Windows] .manifest files are architecture-specific #73

Open GWRon opened 5 years ago

GWRon commented 5 years ago

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 commented 5 years ago

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 commented 5 years ago

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.