Build

Once Target Setup is done, build with whichever VM you want — both are available regardless of which environment setup path you took.

Using ESP-IDF

PicoRuby

$ rake picoruby:build

Equivalent to rake build -DPICORB_VM=mruby — PICORB_VM=mruby is what tells components/picoruby-esp32/CMakeLists.txt to select the *-esp-picoruby.rb build config (see Settings).

FemtoRuby

$ rake femtoruby:build

Equivalent to rake build -DPICORB_VM=mruby/c, selecting the *-esp-femtoruby.rb build config.

Using Docker

PicoRuby

$ rake docker:picoruby:build

FemtoRuby

$ rake docker:femtoruby:build

Cleaning

Using ESP-IDF

$ rake clean       # idf.py clean, plus mruby clean for all 4 build_config combinations
$ rake deep_clean  # clean, plus idf.py fullclean and removing mruby's build/repos/esp32

Reach for deep_clean if you switch targets or VMs and hit stale-build errors that a plain clean doesn’t fix.

Using Docker

$ rake docker:clean
$ rake docker:deep_clean

Next steps

Flash and monitor the result.