You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When building the default "D/VC++ based Windows Application" template in VS2022 I get the following error:
COMPILED : error : cannot find input file -c.d
After investigating what dmd actually got it looks like the first argument argv[1] begins with a BOM.
So the first argument "-c" becomes 239, 187, 191, 45, 99, 0 (0xEFBBBF is the UTF-8 byte order mark)
The compilation error only occurs for dmd builds, not for ldc and only when having the experimental UTF-8 support in Windows 11 enabled: Region Settings - "Beta: Use Unicode UTF-8 for worldwide language support"
It does not happen in "visuald" projects either.
I have not debugged ldc to see if same thing happens there but I suspect it might ignore the BOM.
The text was updated successfully, but these errors were encountered:
I can reproduce this: with UTF-8 as the system encoding the response file is now created with UTF-8 encoding as well. The C# StreamWriter defaults to adding a BOM in this case (which has been disabled for LDC). Should be fixed in https://github.com/dlang/visuald/releases/tag/v1.4.0-rc1
When building the default "D/VC++ based Windows Application" template in VS2022 I get the following error:
COMPILED : error : cannot find input file
-c.d
After investigating what dmd actually got it looks like the first argument argv[1] begins with a BOM.
So the first argument "-c" becomes 239, 187, 191, 45, 99, 0 (0xEFBBBF is the UTF-8 byte order mark)
The compilation error only occurs for dmd builds, not for ldc and only when having the experimental UTF-8 support in Windows 11 enabled: Region Settings - "Beta: Use Unicode UTF-8 for worldwide language support"
It does not happen in "visuald" projects either.
I have not debugged ldc to see if same thing happens there but I suspect it might ignore the BOM.
The text was updated successfully, but these errors were encountered: