-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Install Arduino-CLI when not already present #5
Comments
No, I've re-worded that now. What I meant was after you put the executable in the local file-system you have to tell the extension where it is using the setting you snapped. If you were to put Thus, best to supply a fully qualified path in the path setting but as a courtesy and convenience to the user it should also be on the system path. |
Node reports Windows platforms as win32 irrespective of their actual bitness but |
@RBM-PITT a note on your path, it should be the path to the executable, not the path to the folder containing the executable
|
@RBM-PITT These instructions are now in the wiki. Feedback? https://github.com/PeterWone/vscode-arduino-cli/wiki/How-to-manually-install-Arduino-CLI |
@PeterWone This is perfect - love it. I should be able to step through it later today. Do we have the ability to contribute to the Wiki? I could help out by adding in detail directly rather than having you do that. |
Um... I dunno? Try! |
I have made you a collaborator. This should allow you to create pages as well as edit the existing material. It probably also permits accidental destruction so take care until we understand the tools better. As a side note, this issue wasn't intended as an instruction for use, it is a feature for implementation, that's why I didn't originally write it in a user friendly way. |
@PeterWone I can access the Wiki to contribute - thanks, I understand the need to watch for deletions. I think this issue can close. |
On *nix systems the following will install the CLI
On Windows systems it is necessary to determine platform bitness and fetch one of
then unpack the file and put the executable somewhere in the filesystem, then set the extension path accordingly.
The text was updated successfully, but these errors were encountered: