
The ’ characters around the executable and arguments are ‘-LE:/projects/jitsi/ffmpeg-3.4.8/libswscale’ ‘-LE:/projects/jitsi/ffmpeg-3.4.8/libavutil’ ‘-LE:/projects/jitsi/ffmpeg-3.4.8/libavformat’ ‘-LE:/projects/jitsi/ffmpeg-3.4.8/libavfilter’

‘-LE:/projects/jitsi/ffmpeg-3.4.8/libavcodec’ gcc -LE:/projects/jitsi/ffmpeg-3.4.8/libavcodec -LE:/projects/jitsi/ffmpeg-3.4.8/libavfilter -LE:/projects/jitsi/ffmpeg-3.4.8/libavformat -LE:/projects/jitsi/ffmpeg-3.4.8/libavutil -LE:/projects/jitsi/ffmpeg-3.4.8/libswscale -LE:/projects/jitsi/openh264/ -m64 -Wl,-ojnffmpeg.dll -Wl,–kill-at -static-libgcc -shared -o libjnffmpeg.so …\target\native_obj\FFmpeg.o -lavformat -lavcodec -lavfilter -lavutil -lswscale -lopenh264Įxecute:Java13CommandLauncher: Executing ‘gcc’ with arguments: The major problem when gcc start linking, it seems to omit the lame.h in my lame-3.100/include, I’ve created the include/lame link according to the instruction in windows part of lame building step.enum.AVFILTER_AUTO_CONVERT_NONE in lgpl-dependencies/src/main/c/ffmpeg/FFmpeg.c already defined in ffmpeg project and the #ifndef macro didn’t work, so I deleted it in FFmpeg.c.Right now I’m stuck in the ‘ant ffmpeg’ step of the README-native doc of the lgpl-dependencies project.
#Ffmpeg windows lgpl install
I guess the reason is that when I mvn install the jitsi-lgpl-dependencies, the openh264 not inclueded. = FFmpeg.avcodec_find_encoder(FFmpeg.CODEC_ID_H264) != 0 Īs the method avcodec_find_encoder(FFmpeg.CODEC_ID_H264) failed to return any encoder the example failed. I did some digging and found the problem is in MediaUtils.java. However when running the example AVReceive2 it failed on matching the camera encoding fomat, which is H264. Also removed the exclude lines about lgpl-dependencies in the libjitisi pom(I suppose it should be done to make things work?).
#Ffmpeg windows lgpl download
Download and mvn install each of its dependencies on github/jitsi. I’ve been trying to build and use the libjitsi project tag.

I’m building the lgpl-dependencies project to use libjitsi. Is pom.xml equal to build.xml? Hope someone could offer a clear list.

I wonder what is the right sequence to do all these ant/mvn/make operations.

There are both build.xml and pom.xml, while README-native tells something about compile lame、openh264、ffmpeg and finally jnffmpeg. I’m a little confused with the jitsi-lgpl-dependencies project when I tried to compile it.
