Long Install Directory Pathname Creates Issues for Compiler and Make (ESP8266) #705
Comments
|
A check is done whether the install path is no longer than 100 chars here https://github.com/Sloeber/arduino-eclipse-plugin/blob/master/io.sloeber.core/src/io/sloeber/core/Activator.java#L222 |
jantje
added
domain: configuration
|
This fix brakes my installation: I haven't the described issue here |
|
@dpeddi |
|
I use that and compiled some project with esp8266 and that setup with
success. Now i get the path to long error. Build still work but upload to
flash not.
Regards
Il 15/apr/2017 22:19, "jantje" <[email protected]> ha scritto:
… @dpeddi <https://github.com/dpeddi>
you will get problems if you install and use the xtensa-lx106-elf-gcc
stuff.
It is a tough call but or I test and limit everybody to the largest still
working size or I don't test and get lots of issues.
Given the patreon support it is actually not really a tough choice.
And after all it is a windows problem
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#705 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABCVX9yA62UnnSCrmWjAaz8nyOHyPcGMks5rwSZHgaJpZM4M3LO9>
.
|
|
I compared my path with the path of the guy which opened this case: C:\io.sloeber.product-4.0.1-20170401.212426-33-win32.win32.x86_64\arduinoPlugin\tools\ I still using Sloeber 4.0 (Release) without any issue.. I think that you could increase a bit the path limit. On my environment a quick debug of the plugin tell me that"installPath.toString().length() == 57" |
|
The max path length for the slçoeber installation = max path length allowed by windows - the eclipse install path - "arduinoPlugin" - "packages" - whatever could be in the zip file delivered by a third party. The last part is out of control of sloeber and can change on a day to day basis. Therefore I advice to go for [Drive letter]:\Sloeber and I use a "safe 40" |
|
V4.1 fails to install in Neon 4.6.3 #760 Can you provide explicit instructions on how to make the install work in a Windows 10 environment? |
|
@bill-orange |
|
I will move on to a different product and leave it at that. |
|
RUssia |
|
@grompes |
|
hi |
|
i solved it with shortening the path to my eclipse |
|
@greeran |
|
Why don't you just let the path point to anywhere in the file system rather than insist on having it in this arduinoPlugin subdirectory? I used to be able to just point to my existing Arduino installation and things would be ok, this does not seem to be the case anymore? |
|
This means that Windows 10 users can't use the Eclipse Marketplace to install Sloeber. Don't really understand why this is closed. |
|
I like @greg-ware 's idea. |
|
@wimjongman
I however fear this got lost as I can't find manager_path in the Sloeber code |
|
@tyblu |
|
To avoid the issue with Eclipse-Portable (or any other case where Eclipse is otherwise in a "non-40-safe" folder), simply make a batch file that reads like the following: Of course, change the path and drive letter as desired and possibly the name of the .exe file. Then run that batch file to start Eclipse. Works fine and no error msg when uploading sketches (that I've found yet, anyways.) |
|
Nice one. Thanks!
…________________________________
From: shutterbug-photo <[email protected]>
Sent: Sunday, January 7, 2018 10:36:09 PM
To: Sloeber/arduino-eclipse-plugin
Cc: Wim Jongman; Mention
Subject: Re: [Sloeber/arduino-eclipse-plugin] Long Install Directory Pathname Creates Issues for Compiler and Make (ESP8266) (#705)
To avoid the issue with Eclipse-Portable (or any other case where Eclipse is otherwise in a "non-40-safe" folder), simply make a batch file that reads like the following:
subst m: e:\dropbox\eclipse-portable
m:
EclipsePortable.exe
rem these last two lines simply remove the subst and are optional
c:
subst m: /d
Of course, change the path and drive letter as desired and possibly the name of the .exe file. Then run that batch file to start Eclipse. Works fine and no error msg when uploading sketches (that I've found yet, anyways.)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub<#705 (comment)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AALC6d3cgVx8TJKLeZrlvpjkiiEULwEXks5tITjJgaJpZM4M3LO9>.
|
|
Open a command prompt as administrator. In there, navigate to the folder where eclipse.exe exists (or where eclipse-portable.exe exists, if using the portable version.) Then type in the following five lines:
Echo subst m: %cd% > run-eclipse.bat
Echo m: >> run-eclipse.bat
Echo Eclipse.exe >> run-eclipse.bat
Echo c: >> run-eclipse.bat
Echo subst m: /d >> run-eclipse.bat
This will result in a batch file called run-eclipse.bat. Then you run that file instead of eclipse.exe. The m: can be changed to any unused drive letter.
|
|
It seems you can solve this issue on Windows 10 since version 1607 by disabling the maximum path length limitation. You'll still receive the error message that the path is too long, but I haven't encountered any strange results yet. You can either enable the registry key Source: https://docs.microsoft.com/en-us/windows/desktop/FileIO/naming-a-file#maximum-path-length-limitation |
|
Thanks for the info. |
Enabled NTFS long paths on Win 10 1909. |
|
Thanks Marek.
It is not an Eclipse issue but an issue of the make tooling iirc. |
|
I'm having an issue trying to get Sloeber working and get the error that is discussed here. The difference is that my issue is with the plugin and not the actual .exe file. "Due to issues with long pathnames on Windows, the Sloeber installation path must be less than 40 characters. |
|
Install sloeber in C:\Sloeber or c:\Programs_My\Sloeber |
Basic Infos
Hardware
OS, IDE
Description
During my testing while re-discovering the 'spaces-in-path' issue (see 'Install Advice' under topic 'Windows Comments'), I accidentally forgot to rename the unzip directory before performing the install. The long pathname created issues for both the compiler and 'make', even without spaces present:
Problems Output
Console Output
Requested Install Information
The text was updated successfully, but these errors were encountered: