Hi,

> Good afternoon, sorry that it took so long to update this thread, well I am 
> still trying to use uar ffmpeg in my own way, but it seems that everything is 
> going against me, now the problem is that if I try to compile in windows the 
> process seems to be it carries out but then it doesn't actually do anything, 
> it doesn't compile the executables or the dll, but in linux if you want to 
> use the same set of commands, to compile I do the following:
> I introduce it in the form of a column so that it does not occupy too much
wut
> ./configure 
> --arch=x86_64 
> --target-os=mingw32 
> --cross-prefix=x86_64-w64-mingw32- 
> --prefix=/usr/local 
> --pkg-config=pkg-config 
> --pkg-config-flags=--static 
> --extra-cflags=-static 
> --extra-ldflags=-static 
> --extra-libs="-lm -lz -fopenmp" 
> --enable-static 
> --disable-shared 
> --enable-nonfree
> --enable-gpl 
> --enable-avisynth 
> --enable-libaom 
> --enable-libfdk-aac 
> --enable-libfribidi 
> --enable-libmp3lame 
> --enable-libopus 
> --enable-libsoxr 
> --enable-libvorbis 
> --enable-libvpx 
> --enable-libx264 
> --enable-libx265
> Make
> If I compile it in linux in this way it compiles well, although along the way 
> it tells me that some codecs are deprecated but it does compile, but this 
> same set of commands in windows does not compile, if it indicates that it 
> does but does not produce the final link, this it only happens to me with 
> ffmpeg.
Does that automatically cross-compile with just make? I thought you would need 
to add --enable-cross-compile. Also I’d have thought you’d want a different 
prefix at the least for cross-compiling on linux and compiling on windows.
> I have tried both with cygwin and with the monster developed by microsoft, 
> (the wsl2)

On wsl2, you’d just compile as if you were on a linux system, and not bother 
with mingw32, it’s basically a vm isnt it?

Regards,
Ted Park

_______________________________________________
ffmpeg-user mailing list
[email protected]
https://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
[email protected] with subject "unsubscribe".

Reply via email to