-
-
Notifications
You must be signed in to change notification settings - Fork 892
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
Implemented building single XCFramework #147
base: master
Are you sure you want to change the base?
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice work!
But before I merge, you should fix some issues I found while testing.
- uncomment BuildAll
- try to download FFmpeg source if missing
- macCatalyst fails to build
src/libavcodec/videotoolbox.c:699:45: error: 'kCVPixelBufferOpenGLESCompatibilityKey' is
unavailable: not available on macCatalyst
CFDictionarySetValue(buffer_attributes, kCVPixelBufferOpenGLESCompatibilityKey, kCFB... - framework name should be FFmpeg (notice lower case m)
Now fixing issues and submitting PR with fix to |
Don't you get an error like above while building for macCatalyst? |
I got the same error such as 「'kCVPixelBufferOpenGLESCompatibilityKey' is I got the source from Url: hopes solve the problem and good luck ! |
I also had same error while building.
to following code:
|
Everything worked well when I modify the libavcodec/videotoolbox.c, Thank you very much @666tos Your magic script really helped me . |
👍 |
Hi, I am trying to get the frames of the video, but then i get the below error. [h264 @ 0x7f8c21030200] No start code is found. Can anyone please help me. |
Isn't |
|
||
libtool $LIBTOOL_FLAGS \ | ||
-static -D -arch_only $arch \ | ||
$object_files -o "$thin_dir/$LIBRARY_FILE" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why do you need to call libtool instead of using the .a generated by ffmpeg?
This is due to |
I've gotten the |
@amayers I'm having a similar issue with importing the framework using Swift in an iOS project. Did you manage to figure this out? All I get is |
@Raees678 Not with this repo. But I did get xcframeworks from https://github.com/tanersener/mobile-ffmpeg and with those I just dropped them in and it just worked. I didn’t try from Swift as I have an older Objective-C wrapper around the parts I needed. The strange thing is that project gives you a handful of xcframeworks instead of the one that this PR gives you. That repo has a nice script to build it with just the things you want, or they have up to date prebuilt releases. |
Supported platforms
Issues
xcodebuild -create-xcframework