Fix a number of cross compilation issues using mingw #14003
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
cscd98
changed the title
|
I'd like to mention that the compilation problems with libiconv's |
Correction: NTFS is actually a case sensitive file system, but Windows APIs treat it as a case insensitive one by default. On Windows 10 1803 and later, users can configure individual folders to expose their underlying case sensitivity. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
On a case sensitive filesystem such as what the majority of Linux users have, compilation will fail because the headers are lower case on disk. Makes no difference to Windows as its case insensitive file system.