I have to agree, on windows while it doesn't matter, cross compiling say from linux it makes all the difference. I vote that it should be lower case.
---- On Fri, 06 Dec 2019 12:11:35 -0800 Martin Storsjö_ <[email protected]> wrote ---- Hi, I noticed that the new header files for Hyper-V (added in 3ac71ed3) use mixed upper/lower case file names. Normally mingw-w64 headers use all-lowercase names, despite the headers having different casing in the WinSDK. The WinSDK header casing isn't self-consistent (headers are spelled differently in #include directives in different files, different from the name of the file on disk), therefore there's no single consistent way to spell each of them, and mingw-w64 has so far simply made all headers lowercase. When building things on a case insensitive file system (like on windows), it doesn't matter, but when cross compiling, it's essential to have a clear way that it is supposed to be done. "All old header use plain lowercase, while some new headers happen to have a mixed casing that matches the WinSDK" doesn't feel like a sensible policy to me, so I'd suggest we should rename these new files to all lowercase. As they are recently added (after the v7.0.0 tag), they're probably not very widely used in cross compiled code yet. If the WinSDK ends up self-consistent at some point, with a single canonical way to spell each header file with mixed upper/lower case letters, we could add such symlinks (if installing on a case sensitive file system), but until that point, I'd recommend keeping plain lowercase filenames. // Martin _______________________________________________ Mingw-w64-public mailing list mailto:[email protected] https://lists.sourceforge.net/lists/listinfo/mingw-w64-public _______________________________________________ Mingw-w64-public mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
