We have run into a quite rare issue on WIN32 having TBB/CMake build complaining about nasm: fatal: unrecognized output format. Soon it became clear that NASM could be mistakenly used instead of MASM, if NASM dialect is chosen by some other submodule within the same CMake build! Hence, here is a patch denoting that all TBB .asm files shall be handled on WIN32 particularly by MASM.
We have run into a quite rare issue on WIN32 having TBB/CMake build complaining about
nasm: fatal: unrecognized output format
. Soon it became clear that NASM could be mistakenly used instead of MASM, if NASM dialect is chosen by some other submodule within the same CMake build! Hence, here is a patch denoting that all TBB .asm files shall be handled on WIN32 particularly by MASM.