Build WAMR VM core | Embed WAMR | Export native function | Build WASM applications | Samples
A Bytecode Alliance project
WebAssembly Micro Runtime (WAMR) is a standalone WebAssembly (WASM) runtime with a small footprint. It includes a few parts as below:
-
The "iwasm" VM core, supporting WebAssembly interpreter, ahead of time compilation (AoT) and Just-in-Time compilation (JIT)
-
The application framework and the supporting API's for the WASM applications
-
The dynamic management of the WASM applications
- 100% compliant to the W3C WASM MVP
- Small runtime binary size (85K for interpreter and 50K for AoT) and low memory usage
- Near to native speed by AoT
- Self-implemented module loader enables AoT working cross Linux, SGX and MCU systems
- Choices of WASM application libc support: the built-in libc subset for the embedded environment or WASI for standard libc
- Embeddable with the supporting C API's
- The mechanism for exporting native API's to WASM applications
- Multiple modules as dependencies
- Thread management and pthread library
- Non-trapping float-to-int conversions
- Sign-extension operators
- Bulk memory operations
- Shared memmory
- Multi-value
The WAMR performance, footprint and memory usage data are available at the performance wiki page.
The iwasm supports the following architectures:
- X86-64, X86-32
- ARM, THUMB (ARMV7 Cortex-M7 and Cortex-A15 are tested)
- AArch64 (Cortex-A57 and Cortex-A53 are tested)
- MIPS
- XTENSA
Following platforms are supported. Refer to WAMR porting guide for how to port WAMR to a new platform.
WAMR supports building the iwasm VM core only (no app framework) to the mini product. The WAMR mini product takes the WASM application file name or AoT file name as input and then executes it. For the detailed procedure, please see build WAMR VM core and build and run WASM application. Also we can click the link of each platform above to see how to build iwasm on it.
Both wasm binary file and AoT file are supported by iwasm. The wamrc AoT compiler is to compile wasm binary file to AoT file which can also be run by iwasm. Execute following commands to build wamrc compiler:
cd wamr-compiler
./build_llvm.sh (use build_llvm_xtensa.sh instead to support xtensa target)
mkdir build && cd build
cmake ..
make
ln -s {current path}/wamrc /usr/bin/wamrcFor MacOS, you should replace cmake .. with cmake -DWAMR_BUILD_PLATFORM=darwin ...
By using the iwasm VM core, we are flexible to build different application frameworks for the specific domains, although it would take quite some effort.
The WAMR has offered a comprehensive framework for programming WASM applications for device and IoT usages. The framework supports running multiple applications, that are based on the event driven programming model. Here are the supporting API sets by the WAMR application framework library :
- Timer, Inter-app communication (request/response and pub/sub), Sensor, Connectivity and data transmission, 2D graphic UI
Browse the folder core/app-framework for how to extend the application framework.
The WAMR application manager supports remote application management from the host environment or the cloud through any physical communications such as TCP, UPD, UART, BLE, etc. Its modular design makes it able to support application management for different managed runtimes.
The tool host_tool communicates to the WAMR app manager for installing/uninstalling the WASM applications on companion chip from the host system. And the IoT App Store Demo shows the conception of remotely managing the device applications from the cloud.
Usually there are two tasks for integrating the WAMR into a particular project:
- Select what WAMR components (vmcore, libc, app-mgr, app-framework components) to be integrated, and get the associated source files added into the project building configuration
- Generate the APP SDK for developing the WASM apps on the selected libc and framework components
The WAMR SDK tools is helpful to finish the two tasks quickly. It supports menu configuration for selecting WAMR components and builds the WAMR to a SDK package that includes runtime SDK and APP SDK. The runtime SDK is used for building the native application and the APP SDK should be shipped to WASM application developers.
The WAMR samples integrate the iwasm VM core, application manager and selected application framework components.
- Basic: Demonstrating how host runtime calls WASM function as well as WASM function calls native function.
- Simple: The runtime is integrated with most of the WAMR APP libraries, and a few WASM applications are provided for testing the WAMR APP API set. It uses built-in libc and executes apps in interpreter mode by default.
- littlevgl: Demonstrating the graphic user interface application usage on WAMR. The whole LittlevGL 2D user graphic library and the UI application is built into WASM application. It uses WASI libc and executes apps in AoT mode by default.
- gui: Moved the LittlevGL library into the runtime and defined a WASM application interface by wrapping the littlevgl API. It uses WASI libc and executes apps in interpreter mode by default.
WAMR is a community effort. Since Intel Corp contributed the first release of this open source project, this project has received many good contributions from the community.
See the major features releasing history and contributor names
See the roadmap to understand what major features are planned or under development.
Please submit issues for any new feature request or your plan for contributing new features.
WAMR uses the same license as LLVM: the Apache 2.0 license with the LLVM
exception. See the LICENSE file for details. This license allows you to freely
use, modify, distribute and sell your own products based on WAMR.
Any contributions you make will be under the same license.
Click here to submit. Your feedback is always welcome!
Contact the maintainers: [email protected]