![]() ![]() libavutil/common.h:533: In file included from. libavutil/avutil.h:296: In file included from. libavutil/avassert.h:31: In file included from. CC libavfilter/dnn/dnn_backend_native_layers.o In file included from libavfilter/aeval.c:26: In file included from. It works and keeps compiling until we hit another error. Let’s pass these arguments to compile with emscripten in build.sh : nm=NM use nm tool NM -ar=AR use archive tool AR -as=AS use assembler AS -ln_s=LN_S use symbolic link tool LN_S -strip=STRIP use strip tool STRIP -windres=WINDRES use windows resource compiler WINDRES -x86asmexe=EXE use nasm-compatible assembler EXE -cc=CC use C compiler CC -cxx=CXX use C compiler CXX -objcc=OCC use ObjC compiler OCC -dep-cc=DEPCC use dependency generator DEPCC -nvcc=NVCC use Nvidia CUDA compiler NVCC -ld=LD use linker LD. Under Toolchain options, there are arguments to assign the compiler to use./configure -help Usage: configure Options: Help options. Let’s check if there is any arguments to save us. C compiler gcc # Should be emcc C library glibc ARCH x86 (generic) big-endian no runtime cpu detection yes standalone assembly no x86 assembler nasmĮvery automation tool has its limitation and we need to do it manually in this case. emscripten sdl2-config called with /emsdk_portable/emscripten/tag-1.38.45/system/bin/sdl2-config -cflags emscripten sdl2-config called with /emsdk_portable/emscripten/tag-1.38.45/system/bin/sdl2-config -libs install prefix /usr/local source path. ![]() configure, we still get gcc as our compiler. One of the most important task for emconfigure is to replace the compiler from gcc to emcc (or g++ to em++), but in the output of. And magically there is no error or anything wrong, so do we just need to type emmake make -j and we get FFmpeg.wasm? Unfortunately, the answer is no.
0 Comments
Leave a Reply. |