Update document, fix typo of wamrc help info (#158)

This commit is contained in:
wenyongh 2020-01-21 14:24:10 +08:00 committed by GitHub
parent 46b93b9d22
commit 130d7d07d0
2 changed files with 10 additions and 8 deletions

View File

@ -13,7 +13,7 @@ WebAssembly Micro Runtime (WAMR) is a standalone WebAssembly (WASM) runtime with
- The dynamic management of the WASM applications - The dynamic management of the WASM applications
iwasm VM core iwasm VM core
========================= =========================
@ -22,7 +22,7 @@ iwasm VM core
- Embeddable with the supporting C API's - Embeddable with the supporting C API's
- Small runtime binary size (85K for interpreter and 50K for AoT) and low memory usage - Small runtime binary size (85K for interpreter and 50K for AoT) and low memory usage
- Near to native speed by AoT - Near to native speed by AoT
- AoT module loader works for both embedded OS and Linux system - AoT module loader works for both embedded OS and Linux system
- Choices of WASM application libc support: the built-in libc subset for embedded environment or [WASI](https://github.com/WebAssembly/WASI) for standard libc - Choices of WASM application libc support: the built-in libc subset for embedded environment or [WASI](https://github.com/WebAssembly/WASI) for standard libc
- The mechanism for exporting native API's to WASM applications - The mechanism for exporting native API's to WASM applications
@ -32,8 +32,8 @@ iwasm VM core
The iwasm supports following architectures: The iwasm supports following architectures:
- X86-64, X86-32 - X86-64, X86-32
- ARM, THUMB - ARM, THUMB
- MIPS - MIPS
- XTENSA - XTENSA
Following platforms are supported: Following platforms are supported:
@ -75,7 +75,7 @@ WAMR provides a set of C API for loading the WASM module, instantiating the modu
Application framework Application framework
=================================== ===================================
By using the iwasm VM core, we are flexible to build different application frameworks for the specific domains, although it would take quite some efforts. By using the iwasm VM core, we are flexible to build different application frameworks for the specific domains, although it would take quite some efforts.
The WAMR has offered a comprehensive framework for programming WASM applications for device and IoT usages. The framework supports running multiple applications, which are based on the event driven programming model. Here are the supporting API sets by the [WAMR application library](./doc/wamr_api.md) : The WAMR has offered a comprehensive framework for programming WASM applications for device and IoT usages. The framework supports running multiple applications, which are based on the event driven programming model. Here are the supporting API sets by the [WAMR application library](./doc/wamr_api.md) :
@ -97,7 +97,7 @@ The WAMR application manager supports remote application management from host en
<img src="./doc/pics/wamr-arch.JPG" width="80%"> <img src="./doc/pics/wamr-arch.JPG" width="80%">
The tool [host_agent](./test-tools/host-tool) communicates to the WAMR app manager for installing/uninstalling the WASM applications on companion chip from host system. And the [IoT App Store Demo](./test-tools/IoT-APP-Store-Demo/) shows the conception of remotely managing the device applications from cloud. The tool [host_tool](./test-tools/host-tool) communicates to the WAMR app manager for installing/uninstalling the WASM applications on companion chip from host system. And the [IoT App Store Demo](./test-tools/IoT-APP-Store-Demo/) shows the conception of remotely managing the device applications from cloud.
@ -110,7 +110,7 @@ The **wamr-sdk** tools build the WAMR to both **runtime SDK** for embedding by y
### Menu configuration for building SDK ### Menu configuration for building SDK
Menu configuration is supported for easy integration of runtime components and application libraries for the target architecture and platform. Menu configuration is supported for easy integration of runtime components and application libraries for the target architecture and platform.
``` ```
cd wamr-sdk cd wamr-sdk

View File

@ -94,8 +94,10 @@ Usage: wamrc [options] -o output_file wasm_file
Default is host arch, e.g. x86_64 Default is host arch, e.g. x86_64
<sub> = for ex. on arm or thumb: v5, v6m, v7a, v7m, etc. <sub> = for ex. on arm or thumb: v5, v6m, v7a, v7m, etc.
Use --target=help to list supported targets Use --target=help to list supported targets
--target-abi=<abi> Set the target ABI, e.g. gnu, eabi, gnueabihf, etc. (default: gnu)
Use --target-abi=help to list all the ABI supported
--cpu=<cpu> Set the target CPU (default: host CPU, e.g. skylake) --cpu=<cpu> Set the target CPU (default: host CPU, e.g. skylake)
Use --target=help to list all the CPU supported Use --cpu=help to list all the CPU supported
--cpu-features=<features> Enable or disable the CPU features --cpu-features=<features> Enable or disable the CPU features
Use +feature to enable a feature, or -feature to disable it Use +feature to enable a feature, or -feature to disable it
For example, --cpu-features=+feature1,-feature2 For example, --cpu-features=+feature1,-feature2