-
Notifications
You must be signed in to change notification settings - Fork 6.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[ffmpeg[x264]:x86-windows] build failure #12896
Comments
cc @Sibras |
@Neumann-A, could you take a look at this one please? Looks like the renaming of |
custom configure script ...... try commenting line 4465 in the configure script I was just following the name of the |
Same problem after modifying C:\vcpackage\vcpkg\buildtrees\ffmpeg\src\n4.2-a4d149a5c6.clean\configure as per above. |
libx264.lib is the default name on windows, changing that will break any user using x264 not just ffmpeg. This can be fixed by patching the ffmpeg side of things but I would recommend not changing lib names as that breaks all downstream users of x264. |
The default name for x264 in a shared build is libx264.dll.lib |
Not with msvc compilation. Previously vcpkg output libx264.lib on windows up until the recent change. FFmpeg has been independently using libx264.lib for linking for years without any issue. Mingw can output a "libx264.dll.a" lib that when converted to a msvc compatible file gets the ".dll.lib" extension but by default ffmpeg has always expected the msvc compiled "libx264.lib" |
I changed it because the *.pc file generated by the x264 buildsystem clearly states: |
By default ffmpeg does use pkg-config to get x264 information. The pkgconfig file for x264 does in fact say x264 which is why ffmpeg then does an internal conversion that converts all instances of x264.lib to libx264.lib when using msvc. So your right, in that upstream x264 never output a valid pkgconfig. So to correct that we can either change the lib name as you did or correct the pkgconfig file to match the output lib name. The former requires updating downstream projects (such as ffmpeg) whereas the later does not. Either approach would be technically valid for the pkg-config approach, However I was merely pointing out that all the windows projects that previously used x264 would not be using pkgconfig and would be expecting libx264.lib as that was the previous default. So i wasnt referring to ports but any user of vcpkg would find it no longer works as the defaults have been changed. |
I'm new here and caught into this situation. So why not just make a copy of x264.lib to libx264.lib? It seems to work. |
Please, do something. @Sibras has highlighted two possible ways to fix the issue (if I understood correctly), so why not just choose any and implement? |
Same error on ffmpeg[x264]:x64-windows:
|
Currently this issue shoud be fixed now, please get latest source and try again. I tried to build ffmpeg:x64-windows with latest source, it installed successfully.
|
Host Environment
To Reproduce
Steps to reproduce the behavior:
./vcpkg install ffmpeg[x264]:x86-windows
Failure logs
Contents of
C:\misc\vcpkg\buildtrees\ffmpeg\build-x86-windows-rel-out.log
:Additional context
I have been waiting for several months for
x264
being fixed for Windows, and, when I have finally got it fixed, I can't installx264
version offfmpeg
because of some brand new incredible issues.The text was updated successfully, but these errors were encountered: