The VideoLAN Forums

Library compiled on 10.13 system based on branch 3.0 crashes on 10.12 system.

dyld: Symbol not found: _open_memstream
Referenced from: /Users/../Frameworks/VLCKit.framework/Versions/A/lib/libvlccore.9.dylib (which was built for Mac OS X 10.13)
Expected in: /usr/lib/libSystem.B.dylib

Can you please give the full log, mainly which library is supposed to contain that symbol.

Please also tell us which exact version of VLC you tested and if you compiled VLC yourself or not. Note, if you compile for yourself, you need to use build.sh.

Can you please give the full log, mainly which library is supposed to contain that symbol.

Please also tell us which exact version of VLC you tested and if you compiled VLC yourself or not. Note, if you compile for yourself, you need to use build.sh.

I compiled VLCKit library myself, using the buildVLCKit.sh script, I did not directly compile vlc repository, because it is C language.

VLCKit version of the collapse is the latest 3.0 branch, I first check to the 3.0 branch, and then execute the buildVLCKit.sh script.

It is worth mentioning that the latest 3.0 branch fails to compile on the 10.12 system, which can only be compiled on the 10.13 system, but the 10.13 compiled library crashes at 10.12.

Thank you for your attention.

VLC itself compiles fine on both 10.13 and 10.12. I'm not sure about VLCKit and the build scripts there, though.

VLC itself compiles fine on both 10.13 and 10.12. I'm not sure about VLCKit and the build scripts there, though.

First of all thank you for your attention.
This is where I do not understand, VLCKit is described as "libvlc bindings for OS X, iOS and tvOS in Objective-C", but the official Mac VLC APP does not use VLCKit, but direct use of libvlc, why?
Anyone else know about VLCKit? I hope to get some suggestions, thanks.

The official VLC macOS app consists of internal modules, i.e. it also uses internal APIs not exported by VLCKit yet. But the VLC executable itself is just a simple wrapper around libvlc.

If you want to build a backwards-compatible VLCKit framework, you likely need to modify buildVLCKit.sh by yourself (similar to build.sh in the vlc repository). Alernatively, you can also build VLCKit on the oldest macOS version with the oldest macOS SDK your App wants to support.

This patch solved my problem.
https://code.videolan.org/videolan/VLCK ... cosx.patch
In addition, developers have fixed this bug in the latest code.