Hi,
We are facing the build issue with arm-none-eabi-gcc on Windows 11 when the file path length exceeds 260 characters, although the registry and group policy are configured to support long path. Compiler always complains something like "fatal error: xxx file: No such file or directory"
arm-none-eabi-gcc version: 12.2 rel1
Windows version: Windows 11 23H2
Does GNU Arm Embedded Toolchain support long file path? Or could it be configured to support long path?
Thanks.
This issue must be resolved in the 14.2 release. Look at these lines in the release notes -"The top directory structure from the Windows zip packages have been removed. This means the contents of the package can now be directly extracted. The manifest file in the packages is renamed to manifest.txt"
Not entirely sure about this, but do please try our latest release. I suspect what you are running into https://learn.microsoft.com/en-us/windows/win32/fileio/maximum-file-path-limitation?tabs=registry#enable-long-paths-in-windows-10-version-1607-and-later and our the blue note says:> Understand that enabling this registry setting will only affect applications that have been modified to take advantage of the new feature. Developers must declare their apps to be long path aware, as outlined in the application manifest settings below. This isn't a change that will affect all applications.Our binaries have not been modified to take advantage of this yet AFAIK, but we will look into this for our next release.
Hi Andre,
Yes, Windows maximum file path limitation is exactly the root cause. Appreciate that very much to improve the binaries to be able to handle files whose path length exceeds 260 characters.