# CLI Usage This is the help output from the Wasmer CLI for `wasmer --help` : ``` WebAssembly standalone runtime. USAGE: wasmer FLAGS: -h, --help Prints help information -V, --version Prints version information SUBCOMMANDS: cache Wasmer cache compile Compile a WebAssembly binary config Get various configuration information needed to compile programs which use Wasmer create-exe Compile a WebAssembly binary into a native executable help Prints this message or the help of the given subcommand(s) inspect Inspect a WebAssembly file run Run a WebAssembly file. Formats accepted: wasm, wat self-update Update wasmer to the latest version validate Validate a WebAssembly binary wast Run spec testsuite ``` ## `wasmer cache` ``` USAGE: wasmer cache FLAGS: -h, --help Prints help information -V, --version Prints version information SUBCOMMANDS: clean Clear the cache dir Display the location of the cache help Prints this message or the help of the given subcommand(s) ``` ## `wasmer compile` Compile a WebAssembly binary ``` USAGE: wasmer compile [FLAGS] [OPTIONS] -o FLAGS: --enable-all Enable support for all pre-standard proposals --enable-bulk-memory Enable support for the bulk memory proposal --cranelift Use Cranelift compiler --enable-verifier Enable compiler internal verification -h, --help Prints help information --jit Use JIT Engine --llvm Use LLVM compiler --enable-multi-value Enable support for the multi value proposal --native Use Native Engine --object-file Use ObjectFile Engine --enable-reference-types Enable support for the reference types proposal --enable-simd Enable support for the SIMD proposal --singlepass Use Singlepass compiler --enable-threads Enable support for the threads proposal -V, --version Prints version information OPTIONS: --header
Output path for generated header file -o Output file -m ... --llvm-debug-dir LLVM debug directory, where IR and object files will be written to --target Compilation Target triple ARGS: Input file ``` ## `wasmer config` Get various configuration information needed to compile programs which use Wasmer ``` USAGE: wasmer config [FLAGS] FLAGS: --bindir Directory containing Wasmer executables --cflags C compiler flags for files that include Wasmer headers -h, --help Prints help information --includedir Directory containing Wasmer headers --libdir Directory containing Wasmer libraries --libs Libraries needed to link against Wasmer components --pkg-config It outputs the necessary details for compiling and linking a program to Wasmer, using the `pkg- config` format --prefix Print the installation prefix -V, --version Prints version information ``` ## `wasmer create-exe` Compile a WebAssembly binary into a native executable ``` USAGE: wasmer create-exe [FLAGS] [OPTIONS] -o FLAGS: --enable-all Enable support for all pre-standard proposals --enable-bulk-memory Enable support for the bulk memory proposal --cranelift Use Cranelift compiler --enable-verifier Enable compiler internal verification -h, --help Prints help information --llvm Use LLVM compiler --enable-multi-value Enable support for the multi value proposal --enable-reference-types Enable support for the reference types proposal --enable-simd Enable support for the SIMD proposal --singlepass Use Singlepass compiler --enable-threads Enable support for the threads proposal -V, --version Prints version information OPTIONS: -o Output file -m ... -l ... Additional libraries to link against. This is useful for fixing linker errors that may occur on some systems --llvm-debug-dir LLVM debug directory, where IR and object files will be written to --target Compilation Target triple ARGS: Input file ``` ## `wasmer inspect` Inspect a WebAssembly file ``` USAGE: wasmer inspect [FLAGS] [OPTIONS] FLAGS: --enable-all Enable support for all pre-standard proposals --enable-bulk-memory Enable support for the bulk memory proposal --cranelift Use Cranelift compiler --enable-verifier Enable compiler internal verification -h, --help Prints help information --jit Use JIT Engine --llvm Use LLVM compiler --enable-multi-value Enable support for the multi value proposal --native Use Native Engine --object-file Use ObjectFile Engine --enable-reference-types Enable support for the reference types proposal --enable-simd Enable support for the SIMD proposal --singlepass Use Singlepass compiler --enable-threads Enable support for the threads proposal -V, --version Prints version information OPTIONS: --llvm-debug-dir LLVM debug directory, where IR and object files will be written to ARGS: File to validate as WebAssembly ``` ## `wasmer run` Run a WebAssembly file. Formats accepted: wasm, wat ``` USAGE: wasmer run [FLAGS] [OPTIONS] [--] [--]... FLAGS: --enable-all Enable support for all pre-standard proposals --enable-bulk-memory Enable support for the bulk memory proposal --cranelift Use Cranelift compiler --disable-cache Disable the cache --enable-verifier Enable compiler internal verification -h, --help Prints help information --jit Use JIT Engine --llvm Use LLVM compiler --enable-multi-value Enable support for the multi value proposal --native Use Native Engine --object-file Use ObjectFile Engine --enable-reference-types Enable support for the reference types proposal --enable-simd Enable support for the SIMD proposal --singlepass Use Singlepass compiler --enable-threads Enable support for the threads proposal -V, --version Prints version information OPTIONS: --dir ... WASI pre-opened directory --mapdir ... Map a host directory to a different location for the wasm module --env ... Pass custom environment variables -i, --invoke Invoke a specified function --llvm-debug-dir LLVM debug directory, where IR and object files will be written to ARGS: File to run <-->... Application arguments ``` ## `wasmer self-update` It auto-updates Wasmer to the most-recent published version. ## `wasmer validate ` Validate a WebAssembly binary ``` USAGE: wasmer validate [FLAGS] [OPTIONS] FLAGS: --enable-all Enable support for all pre-standard proposals --enable-bulk-memory Enable support for the bulk memory proposal --cranelift Use Cranelift compiler --enable-verifier Enable compiler internal verification -h, --help Prints help information --jit Use JIT Engine --llvm Use LLVM compiler --enable-multi-value Enable support for the multi value proposal --native Use Native Engine --object-file Use ObjectFile Engine --enable-reference-types Enable support for the reference types proposal --enable-simd Enable support for the SIMD proposal --singlepass Use Singlepass compiler --enable-threads Enable support for the threads proposal -V, --version Prints version information OPTIONS: --llvm-debug-dir LLVM debug directory, where IR and object files will be written to ARGS: File to validate as WebAssembly ``` ## `wamser wast` Run spec testsuite ``` USAGE: wasmer wast [FLAGS] [OPTIONS] FLAGS: --enable-all Enable support for all pre-standard proposals --enable-bulk-memory Enable support for the bulk memory proposal --cranelift Use Cranelift compiler --enable-verifier Enable compiler internal verification -f, --fail-fast A flag to indicate wast stop at the first error or continue -h, --help Prints help information --jit Use JIT Engine --llvm Use LLVM compiler --enable-multi-value Enable support for the multi value proposal --native Use Native Engine --object-file Use ObjectFile Engine --enable-reference-types Enable support for the reference types proposal --enable-simd Enable support for the SIMD proposal --singlepass Use Singlepass compiler --enable-threads Enable support for the threads proposal -V, --version Prints version information OPTIONS: --llvm-debug-dir LLVM debug directory, where IR and object files will be written to ARGS: Wast file to run ``` --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://jubianchi.gitbook.io/wasmer-docs/fix-python-summary/ecosystem/wasmer/usage.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.