[Issue 18964] -m32 should mean COFF, default is surprising

[d-bugmail at puremagic.com]

https://issues.dlang.org/show_bug.cgi?id=18964

--- Comment #2 from Manu <turkeyman at gmail.com> ---
That's where he started, but the trouble usually comes when wanting to build
-m32 after building -m64. The errors are surprising, and he spent time trying
to understand what was wrong with his libs, maybe pathing problems, a good
amount of head-scratching, etc... nope, it's just 'broken'!
No reasonable person would expect OMF.

I don't know why, but it's still common to emit both binaries in windows
builds.
There's a sort of de-facto standard that distributing libs should include the
full suite.


> Also, when you submit a PR [...]

Oh okay, can do in future. Honestly, I expected this would have exactly no
traction... but I think it's worth consideration.

It's not any skin off anyone's noses here, but unsuspecting new users only
really stand to be surprised and/or annoyed by the current arrangement.

--