On Wed Feb 28 20:24:21 2024 +0000, Alexandre Julliard wrote:
Or is there another reason to prefer having it in winebuild?
No, it's mostly because it seems to fit better. We already have all the needed support for generating that sort of thing, instead of using a C file with an asm statement and custom macros.
I pushed a version that uses winebuild. One downside I noticed is that now it's always pulled, even if the linker doesn't make use of it. For that a symbol in a static library symbol seems like an elegant way of just skipping it.
When it's pulled, its symbols need to be resolved and some of them are builtin linker symbols, not supported by binutils (because they don't make sense without load config support). We don't support CF guards yet, so I just filled that with zeroes, but supporting them at some point seems potentially interesting.