https://sourceware.org/bugzilla/show_bug.cgi?id=16790
--- Comment #6 from Corinna Vinschen <corinna at vinschen dot de> --- After some discussion with Jon_Y and Yaakov on IRC, I'm pretty much ok with moving the default-manifest handling to GCC. I'm just wondering if the default-manifest shouldn't then be made into its own package, independent of binutils and GCC, so that we can update the default manifest if a new Windows comes out, without having to update binutils or GCC packages as well. If we do that, GCC would have to handle three situations: - The default-manifest.o file doesn't exist in the search path. Don't even try to add it to the command line. - The manifest file exists, the -shared option is given. Don't add default-manifest.o to the command line. - The manifest file exists, the -shared option is not given. Append default-manifest.o to the command line. Will that work? 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
