-
-
Notifications
You must be signed in to change notification settings - Fork 398
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
custom "Arduino15" path #951
Comments
I believe that arduino-cli indeed usally loads its config file from the Arduino15 path, but inside that file you can specify a different path for storing e.g. the downloaded cores. Did you see https://arduino.github.io/arduino-cli/latest/configuration/ ? Maybe that would solve your need? Furthermore, you can even change the location of the configfile using the Lastly, |
Do you have an command line example to use the custom data path for compile? in my case: |
You would have to specify a custom data path in the directories:
data: /home/user/arduino-cli-data
downloads: /home/user/arduino-cli-data/staging
user: /home/user/arduino-cli-sketchbook The put this file in your Does that help? |
i have a complete copy of the Arduino15 path, where the arduino-cli.exe exist. yaml file ist this and placed in arduino-cli.exe:
commandline ist this: but it's not working.
|
I'm not sure how this works exactly on Windows, but on Linux starting a path with a
Maybe that should contain a full path to the Arduino15 directory, or maybe just remove the leading |
same result without / |
Closing because Arduino CLI already provides the capability to specify a custom |
Feature Request
Current behavior
the Arduino15 path is placed in "%USERPATH%\AppData\Local" and is used by CLI and IDE
Expected behavior
add option portable folder to place the Arduino15 files there, like IDE portable function
or add option to place Arduino15 in the same path, where arduino-cli.exe exist
Environment
arduino-cli version
): 0.10.0 Commit: ec5c3edAdditional context
so it's possilbe to use the CLI standalone
The text was updated successfully, but these errors were encountered: