@@ -177,12 +177,24 @@ board_manager:
177
177
- https://arduino.esp8266.com/stable/package_esp8266com_index.json
178
178
` ` `
179
179
180
- From now on, commands supporting custom cores will automatically use the additional URL from the configuration file:
180
+ If you have your package indexes locally installed, you can list their file path in the Arduino CLI configuration file.
181
+
182
+ For example, to add the NRF52832 core, edit the configuration file and change the ` board_manager` settings as follows:
183
+
184
+ ` ` ` yaml
185
+ board_manager:
186
+ additional_paths:
187
+ - /absolute/path/to/your/package_nrf52832_index.json
188
+ ` ` `
189
+
190
+ From now on, commands supporting custom cores will automatically use the additional URL and additional paths from the
191
+ configuration file :
181
192
182
193
` ` ` sh
183
194
$ arduino-cli core update-index
184
195
Updating index: package_index.json downloaded
185
196
Updating index: package_esp8266com_index.json downloaded
197
+ Updating index: package_nrf52832_index.json
186
198
Updating index: package_index.json downloaded
187
199
188
200
$ arduino-cli core search esp8266
@@ -202,6 +214,18 @@ ID Version Name
202
214
esp8266:esp8266 2.5.2 esp8266
203
215
` ` `
204
216
217
+ The same applies to the additional package index file provided by file paths. Use the `--additional-paths` option, that
218
+ has to be specified every time and for every command that operates on a 3rd party platform core, for example :
219
+
220
+ ` ` ` sh
221
+ $ arduino-cli core update-index --additional-paths /absolute/path/to/your/package_esp8266com_index.json
222
+ Updating index: package_esp8266com_index.json downloaded
223
+
224
+ $ arduino-cli core search esp8266 --additional-paths /absolute/path/to/your/package_esp8266com_index.json
225
+ ID Version Name
226
+ esp8266:esp8266 2.5.2 esp8266
227
+ ` ` `
228
+
205
229
# # Compile and upload the sketch
206
230
207
231
To compile the sketch you run the `compile` command, passing the proper FQBN string :
0 commit comments