fix MXE compiler warnings #4753
Comments
Forgon uploaded file patch file created with |
Forgon uploaded file patch file created with |
Forgon uploaded file patch file created with |
Forgon uploaded file patch file created with |
Forgon uploaded file patch file created with |
Forgon uploaded file all parts of this patch series joint into one patch file |
Forgon uploaded file complete command line output of |
Forgon uploaded file complete command line output of |
Forgon2100 <forgon2100@...> changed status from |
Forgon2100 <forgon2100@...> changed owner from `` to |
Forgon2100 <forgon2100@...> changed resolution from `` to |
Forgon2100 <forgon2100@...> commented In Warzone2100/warzone2100@be42a20:
|
Forgon2100 <forgon2100@...> committed [066] In Warzone2100/warzone2100@066e900:
|
Forgon2100 <forgon2100@...> committed [74364172] In Warzone2100/warzone2100@7436417:
|
Forgon2100 <forgon2100@...> committed [11] In Warzone2100/warzone2100@11fcfa2:
|
Forgon2100 <forgon2100@...> commented In Warzone2100/warzone2100@ad63e40:
|
resolution_fixed
type_patch (an actual patch, not a request for one)
| by ForgonMXE ensures that all code is position-independent. Warzone 2100 uses the "-fPIC" compile flag, leading to several unnecessary warnings like:
GCC developers expect users not use "-fPIC" for Windows targets. Consequently, we no longer do.
The MSVC-specific pragma "comment" was executed on other platforms and thus not recognised:
The format specifier macros 'PRIu32', 'PRIu64' and 'PRId64' were not properly expanded with MXE, causing warnings such as:
The solution was to use the MXE-specific macros '!__USE_MINGW_ANSI_STDIO' and '!__MINGW_PRINTF_FORMAT' as described here.
A typo caused this warning:
Parentheses were added around assignments used as truth values to avoid compiler warnings like:
Issue migrated from trac:4753 at 2022-04-16 13:03:45 -0700
The text was updated successfully, but these errors were encountered: