zefie/llvm-mingw
1
0 Fork 0
Code Activity

Update README.md about using llvm-rc instead of GNU binutils windres

Browse Source
This commit is contained in:
Martin Storsjö committed 2018-05-07 09:44:41 +03:00
1 parent 08224169fd
commit decfd0030b
1 file changed
+3 -10
Download Patch File Download Diff File Expand all files Collapse all files
README.md
+3 -10
View File
@@ -46,14 +46,6 @@ a different version) - and likewise, if configure flags in the build-*.sh
scripts have changed, you might need to wipe the build directory under scripts have changed, you might need to wipe the build directory under
each project for the new configure options to be taken into use. each project for the new configure options to be taken into use.
If building without the dockerfile, manually install a copy of normal
GNU binutils windres with the name `x86_64-w64-mingw32-windresreal`.
Wrappers named `<triplet>-windres` are installed that call this binary
with the necessary options to make it output in the arch independent
res format, allowing using it for all architectures, even those that
GNU binutils don't support. (LLVM does provide a similar tool, llvm-rc,
but it's not yet ready to actually replace windres in all cases.)
Status Status
@@ -80,7 +72,8 @@ normal GCC/binutils based MinGW.
at the moment. at the moment.
- The C++ exception unwinding in libunwind uses APIs that aren't available - The C++ exception unwinding in libunwind uses APIs that aren't available
in the UWP/WinRT API subset. in the UWP/WinRT API subset.
- The windres wrapper requires a copy of a normal GNU binutils windres, - The windres replacement, llvm-rc, isn't very mature and doesn't support
see above for more details. everything that GNU windres does. Additionally, some part of the preprocessing
is currently implemented in shell script, making it a bit slow.
Additionally, one may run into other minor differences between GCC and clang. Additionally, one may run into other minor differences between GCC and clang.