You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Note: Homebrew’s Python installation already includes `pip`, `setuptools` and `venv`.
143
143
144
144
### On Windows
145
-
While installing and building natively on zephyr is supported as described at: https://docs.zephyrproject.org/latest/develop/getting_started/index.html.
145
+
Windows is not currently supported. However it is possible to setup and build the loader using WSL. You will need to follow the instructions given above for installing on Ubuntu.
146
146
147
-
Arduino currently has not ported their build setup to the Windows environment. However it is possible to setup and build the loaders on a Windows system using WSL and use the resulting Loader files within Windows. You will need to follow the instructions given above
148
-
for installing on Ubuntu.
147
+
There are two strategies:
148
+
1) Install the sources in the native Windows filesystem (NTFS, FAT32, etc) and within WSL, cd to the root directory where you installed your sources, like: `/mnt/d/github/ArduinoCore-zephyr`.
149
+
2) Install the sources within the WSL file system, like: `~/git/ArduinoCore-zephyr`
149
150
150
-
There are at least two strategies.
151
-
1) Install the sources in the native Windows filesystem (NTFS, FAT32, etc) and within WSL, cd to the root directory where you installed your sources, like: /mnt/d/github/ArduinoCore-zephyr.
151
+
There are pros and cons to both strategies:
152
+
1) Builds are relatively very slow, but once done you can use it directly within Arduino.
153
+
2) Builds are a lot faster, however, you need to copy the resulting build back to somewhere in your windows directory structure. It is this location, that you will add to the Arduino IDE as mentioned below in the section: Using the core in Arduino IDE/CLI.
152
154
153
-
2) Install the sources within the WSL file system, like: ~/git/ArduinoCore-zephyr
154
-
155
-
There are pros and cons to both strategies. With 1) Builds are relatively very slow, but once done you can use it directly within
156
-
Arduino. With 2) Builds are a lot faster, however, you then need to copy the resulting build back to somewhere in your windows directory
157
-
structure. It is this location, that you will add to the Arduino IDE as mentioned below in the section: Using the core in Arduino IDE/CLI
158
-
159
-
In either strategy, you may have to update the link: cores\arduino\api as sometimes this link file may or may not work properly.
155
+
In either strategy, you may have to update the link: `cores\arduino\api`.
0 commit comments