diff --git a/CrossBranch.md b/CrossBranch.md index 8e55d99..62adadb 100644 --- a/CrossBranch.md +++ b/CrossBranch.md @@ -2,6 +2,6 @@ Branch `cross` in the repository contains some convenience/example scripts to cr You can browse contents of this branch at https://github.com/micropython/micropython/commits/cross (and due to the fact that branch is rebased on top of master, its changes are always "at the top"). -The general idea is that there're `unix/build-.sh` scripts which build a MicroPython executable for a particular target, using suitable cross-compiling toolchain and set of options. To use it, you already should have a cross-compiler installed, build scripts try to provide links/instructions how to set it up. Cross-compiling options are configured in such way as to compile as standalone binary as possibly (ultimately, linked sully statically and requiring just bare Linux kernel to run, but we're not yet there). +The general idea is that there're `unix/build-.sh` scripts which build a MicroPython executable for a particular target, using suitable cross-compiling toolchain and set of options. To use it, you already should have a cross-compiler installed, build scripts try to provide links/instructions how to set it up. Cross-compiling options are configured in such way as to compile as standalone binary as possible (ultimately, linked fully statically and requiring just bare Linux kernel to run, but we're not yet there). Beyond the build script, if a target is supported by QEMU user-level emulation, there's a convenience `unix/micropython.` script provided to run cross-compiled binary via such emulation (until binaries are fully static, this requires at least small target filesystem with libraries, etc. - it is usually part of cross-compiling toolchain). As a final convenience, `tests/run-tests.` script is provided, to run MicroPython testsuite using `micropython.` wrapper.