Skip to content

Commit cb564ce

Browse files
Update docs
1 parent 4cc8246 commit cb564ce

File tree

1 file changed

+6
-4
lines changed

1 file changed

+6
-4
lines changed

docs/os-development/running-on-desktop.md

Lines changed: 6 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -15,18 +15,20 @@
1515

1616
2. **Make sure you have the software**
1717

18-
If you built from source, you will already have it in `lvgl_micropython/build/lvgl_micropy_unix`
19-
20-
If you downloaded a pre-built binary (like `MicroPythonOS_amd64_macOS_0.7.1.bin` or `MicroPythonOS_amd64_linux_0.7.1.elf`), then copy it to the right location:
18+
The easiest is to downloaded a pre-built binary (like `MicroPythonOS_amd64_macOS_0.7.1.bin` or `MicroPythonOS_amd64_linux_0.7.1.elf`) from the [releases page](https://github.com/MicroPythonOS/MicroPythonOS/releases).
19+
20+
After downloading it, put it in the right location like this:
2121

2222
<pre>
2323
```
24-
mkdir -p lvgl_micropython/build
24+
mkdir -p lvgl_micropython/build # do this from within in the folder MicroPythonOS/ you cloned in step 1
2525
cp /Users/yourname/MicroPythonOS_amd64_macOS_0.7.1.bin lvgl_micropython/build/lvgl_micropy_macOS # for macOS
2626
cp /home/yourname/MicroPythonOS_amd64_linux_0.7.1.elf lvgl_micropython/build/lvgl_micropy_unix # for Linux or WSL2 on Windows 11
2727
```
2828
</pre>
2929

30+
Alternatively, instead of downloading a pre-built binary, you can [build it from source](../os-development/compiling.md), and then you will have the built binary in `lvgl_micropython/build/lvgl_micropy_XXX` where XXX is unix or macOS.
31+
3032
3. **Start the software:**
3133

3234
You're now ready to run it with:

0 commit comments

Comments
 (0)