Skip to content

Commit 130d7d0

Browse files
authored
Update document, fix typo of wamrc help info (#158)
1 parent 46b93b9 commit 130d7d0

File tree

2 files changed

+10
-8
lines changed

2 files changed

+10
-8
lines changed

README.md

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -13,7 +13,7 @@ WebAssembly Micro Runtime (WAMR) is a standalone WebAssembly (WASM) runtime with
1313

1414
- The dynamic management of the WASM applications
1515

16-
16+
1717

1818
iwasm VM core
1919
=========================
@@ -22,7 +22,7 @@ iwasm VM core
2222

2323
- Embeddable with the supporting C API's
2424
- Small runtime binary size (85K for interpreter and 50K for AoT) and low memory usage
25-
- Near to native speed by AoT
25+
- Near to native speed by AoT
2626
- AoT module loader works for both embedded OS and Linux system
2727
- Choices of WASM application libc support: the built-in libc subset for embedded environment or [WASI](https://github.com/WebAssembly/WASI) for standard libc
2828
- The mechanism for exporting native API's to WASM applications
@@ -32,8 +32,8 @@ iwasm VM core
3232
The iwasm supports following architectures:
3333

3434
- X86-64, X86-32
35-
- ARM, THUMB
36-
- MIPS
35+
- ARM, THUMB
36+
- MIPS
3737
- XTENSA
3838

3939
Following platforms are supported:
@@ -75,7 +75,7 @@ WAMR provides a set of C API for loading the WASM module, instantiating the modu
7575
Application framework
7676
===================================
7777

78-
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.
78+
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.
7979

8080
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) :
8181

@@ -97,7 +97,7 @@ The WAMR application manager supports remote application management from host en
9797

9898
<img src="./doc/pics/wamr-arch.JPG" width="80%">
9999

100-
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.
100+
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.
101101

102102

103103

@@ -110,7 +110,7 @@ The **wamr-sdk** tools build the WAMR to both **runtime SDK** for embedding by y
110110

111111
### Menu configuration for building SDK
112112

113-
Menu configuration is supported for easy integration of runtime components and application libraries for the target architecture and platform.
113+
Menu configuration is supported for easy integration of runtime components and application libraries for the target architecture and platform.
114114

115115
```
116116
cd wamr-sdk

doc/build_wasm_app.md

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -94,8 +94,10 @@ Usage: wamrc [options] -o output_file wasm_file
9494
Default is host arch, e.g. x86_64
9595
<sub> = for ex. on arm or thumb: v5, v6m, v7a, v7m, etc.
9696
Use --target=help to list supported targets
97+
--target-abi=<abi> Set the target ABI, e.g. gnu, eabi, gnueabihf, etc. (default: gnu)
98+
Use --target-abi=help to list all the ABI supported
9799
--cpu=<cpu> Set the target CPU (default: host CPU, e.g. skylake)
98-
Use --target=help to list all the CPU supported
100+
Use --cpu=help to list all the CPU supported
99101
--cpu-features=<features> Enable or disable the CPU features
100102
Use +feature to enable a feature, or -feature to disable it
101103
For example, --cpu-features=+feature1,-feature2

0 commit comments

Comments
 (0)