BalancedTernary
BalancedTernary
> As far as I remember, this issue is caused by path to the file being too long. @SuGlider @lucasssvaz do you remember if there was any fix for Windows...
> @Jason2866 it's not command length, but path length, which was something like 256, but was often found to be a bit less. We already had that issue with RV...
> @me-no-dev I remember that this could happen if the path was too long or the extraction of the libraries failed somehow. I checked our talks regarding this and the...
> How long is in the path? This issue was solved in #8750, as @lucasssvaz mentioned.`` > > > I don't know if this information will be useful: I looked...
> @BalancedTernary if you can not find the file anywhere in the toolchain folder, then because of that same issue, it was not even extracted. I can find these files...
> It really seems like the combination of a 23 characters username and the long path is preventing Windows tools from being able to open the files. > > The...
> @BalancedTernary , [the toolchain release](https://github.com/espressif/crosstool-NG/releases/tag/esp-13.2.0_20240530) has fixes for paths on windows. Could you give it a try? I currently alleviate this problem by manually copying files to the lookup...