https://sourceware.org/bugzilla/show_bug.cgi?id=16790
Corinna Vinschen <corinna at vinschen dot de> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |ktietz at redhat dot com
--- Comment #4 from Corinna Vinschen <corinna at vinschen dot de> ---
[Pulling in ktietz to get a Mingw POV as well]
>From my POV the linker is the right place to do this, and I think it would
be the right thing to add logic to ld to add the default manifest only for
executables and only if necessary, rather than adding it indiscriminately to
the linker scripts.
GCC could handle the fact to add a default manifest only when building
executables, but it has no idea if a manifest is already present in the
sources or not. Also, ld (now) has all the logic to merge resources, while
GCC knows squat about this stuff. Also, as soon as a new Windows version
with a new GUID comes out, it's much easier and faster to get a binutils
package out than a complete new GCC package.
Having said that, I guess this is all fixable one way or the other. It's
just that I think it's much simpler to have everything, the logic and the
required input file, in one place.
Corinna
--
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
bug-binutils mailing list
bug-binutils@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-binutils
