46b93b9d22
* Implement memory profiler, optimize memory usage, modify code indent * Implement memory.grow and limit heap space base offset to 1G; modify iwasm build type to Release and 64 bit by default * Add a new extension library: connection * Fix bug of reading magic number and version in big endian platform * Re-org platform APIs: move most platform APIs from iwasm to shared-lib * Enhance wasm loader to fix some security issues * Fix issue about illegal load of EXC_RETURN into PC on stm32 board * Updates that let a restricted version of the interpreter run in SGX * Enable native/app address validation and conversion for wasm app * Remove wasm_application_exectue_* APIs from wasm_export.h which makes confused * Refine binary size and fix several minor issues Optimize interpreter LOAD/STORE opcodes to decrease the binary size Fix issues when using iwasm library: _bh_log undefined, bh_memory.h not found Remove unused _stdin/_stdout/_stderr global variables resolve in libc wrapper Add macros of global heap size, stack size, heap size for Zephyr main.c Clear compile warning of wasm_application.c * Add more strict security checks for libc wrapper API's * Use one libc wrapper copy for sgx and other platforms; remove bh_printf macro for other platform header files * Enhance security of libc strcpy/sprintf wrapper function * Fix issue of call native for x86_64/arm/mips, add module inst parameter for native wrapper functions * Remove get_module_inst() and fix issue of call native * Refine wgl lib: remove module_inst parameter from widget functions; move function index check to runtime instantiate * Refine interpreter call native process, refine memory boudary check * Fix issues of invokeNative function of arm/mips/general version * Add a switch to build simple sample without gui support * Add BUILD_TARGET setting in makefile to replace cpu compiler flags in source code * Re-org shared lib header files, remove unused info; fix compile issues of vxworks * Add build target general * Remove unused files * Update license header * test push * Restore file * Sync up with internal/feature * Sync up with internal/feature * Rename build_wamr_app to build_wasm_app * Fix small issues of README * Enhance malformed wasm file checking Fix issue of print hex int and implement utf8 string check Fix wasi file read/write right issue Fix minor issue of build wasm app doc * Sync up with internal/feature * Sync up with internal/feature: fix interpreter arm issue, fix read leb issue * Sync up with internal/feature * Fix bug of config.h and rename wasi config.h to ssp_config.h * Sync up with internal/feature * Import wamr aot * update document * update document * Update document, disable WASI in 32bit * update document * remove files * update document * Update document * update document * update document * update samples * Sync up with internal repo |
||
---|---|---|
.. | ||
app | ||
runtime | ||
build_sdk.sh | ||
Kconfig | ||
Makefile | ||
menuconfig.sh | ||
README.md | ||
wamr_config_default.cmake |
SDK for Wasm Micro Runtime
This folder contains some tools to generate sdk for wamr runtime and wasm applications, the script and cmake files here are called by make
, don't use them manually.
Build the SDK
cd ${WAMR_ROOT}/wamr-sdk
make config
Following the prompt to finish the settings for your customized runtime and app sdk, then you will get out
folder under ${WAMR_ROOT}
The structure of the output folder is like bellow:
out
|--app-sdk/
| |--sysroot/
| |--wamr_toolchain.cmake
|
|--runtime-sdk/
|--include
|--lib
|--wamr_config.cmake
app-sdk usage
The app-sdk
is used to develop wasm applications, if your project are built with cmake, then the wamr_toolchain.cmake
file is what you need to compile your project into wasm bytecode.
runtime-sdk usage
The runtime-sdk
is used to help you embed WAMR runtime into your product easier. There are two method you can use the SDK:
-
Use the provided
runtime_lib.cmake
file:You can include
${WAMR_ROOT}/cmake/runtime_lib.cmake
in your project'sCMakeLists.txt
file:include (${WAMR_ROOT}/cmake/runtime_lib.cmake) add_library (vmlib ${WAMR_RUNTIME_LIB_SOURCE}) # ...... target_link_libraries (your_target vmlib -lm -ldl -lpthread)
-
Use the pre-built static library:
You can link the pre-built library:
link_directories(${SDK_DIR}/runtime-sdk/lib) include_directories(${SDK_DIR}/runtime-sdk/include) # ...... target_link_libraries (your_target vmlib -lm -ldl -lpthread)
This method can also be used when you don't use cmake
You can refer to this sample: CMakeLists.txt.
NOTE: If you are familiar with how to configure WAMR by cmake and don't want to build the SDK, you can set the related settings on the top of your
CMakeLists.txt
, then theruntime_lib.cmake
will not load settings from the SDK.