From: Zhao Zhili <quinkblack@foxmail.com> To: ffmpeg-devel@ffmpeg.org Cc: Zhao Zhili <zhilizhao@tencent.com> Subject: [FFmpeg-devel] [PATCH 0/2] Add wasi(WebAssembly System Interface) support Date: Fri, 28 Jun 2024 12:45:58 +0800 Message-ID: <tencent_26F44E0270622DD69A6040579A6A9F22AB08@qq.com> (raw) From: Zhao Zhili <zhilizhao@tencent.com> With wasi-sdk toolchain [1], now you can ./configure --cc=${wasi-sdk}/bin/clang \ --cxx=${wasi-sdk}/bin/clang++ \ --ar=${wasi-sdk}/bin/ar \ --strip=${wasi-sdk}/bin/strip \ --nm=${wasi-sdk}/bin/llvm-nm \ --ranlib=${wasi-sdk}/bin/ranlib \ --extra-cflags="--target=wasm32-wasi -D_WASI_EMULATED_SIGNAL -D_WASI_EMULATED_PROCESS_CLOCKS" --extra-libs="-lwasi-emulated-signal -lwasi-emulated-process-clocks" --disable-inline-asm \ --disable-x86asm \ --disable-network \ --disable-protocol=fd \ --disable-protocol=pipe \ --enable-cross-compile \ After make, you can run examples directly on cmdline with wasi runtime, for example, wasmtime [2] and wasmer [3] wasmtime --dir . ./demux_decode ./bbb.mp4 bbb-v bbb-a wasmer --dir . ./demux_decode ./bbb.mp4 bbb-v bbb-a Besides trying out wasm, I don't know what else it can be used for. [1] https://github.com/WebAssembly/wasi-sdk [2] https://github.com/bytecodealliance/wasmtime [3] https://github.com/wasmerio/wasmer Zhao Zhili (2): avutil/file_open: Fix build error with wasi avformat/file: guard fd_dup by FD_PROTOCOL or PIPE_PROTOCOL configure | 2 ++ libavformat/file.c | 2 ++ libavutil/file_open.c | 2 +- 3 files changed, 5 insertions(+), 1 deletion(-) -- 2.42.0 _______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit link above, or email ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe".
reply other threads:[~2024-06-28 4:46 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=tencent_26F44E0270622DD69A6040579A6A9F22AB08@qq.com \ --to=quinkblack@foxmail.com \ --cc=ffmpeg-devel@ffmpeg.org \ --cc=zhilizhao@tencent.com \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: link
Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel This inbox may be cloned and mirrored by anyone: git clone --mirror https://master.gitmailbox.com/ffmpegdev/0 ffmpegdev/git/0.git # If you have public-inbox 1.1+ installed, you may # initialize and index your mirror using the following commands: public-inbox-init -V2 ffmpegdev ffmpegdev/ https://master.gitmailbox.com/ffmpegdev \ ffmpegdev@gitmailbox.com public-inbox-index ffmpegdev Example config snippet for mirrors. AGPL code for this site: git clone https://public-inbox.org/public-inbox.git