You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Compiling libmediapipe_c.dylib results in various unresolved undefined symbols, which makes it impossible for MediaPipe.NET to work on MacOS.
The ones that are not being resolved seem to be _AV*. There may be other unresolved symbols among them, such as _CV*.
Having FFmpeg installed on the system doesn't seem to fix the issue, which leads me to think that we have some sort of configuration issue related to the MediaPipe.NET.Runtime building script on MacOS.
Here are all undefined MacOS symbols in a text file (no indication of whether they are being resolved at runtime or not).
If you have a MacOS system, you can get them by typing the command nm -gu <path-to>/libmediapipe_c.dylib. undefined-macos-symbols.txt
The text was updated successfully, but these errors were encountered:
Compiling
libmediapipe_c.dylib
results in various unresolved undefined symbols, which makes it impossible for MediaPipe.NET to work on MacOS.The ones that are not being resolved seem to be
_AV*
. There may be other unresolved symbols among them, such as_CV*
.Having FFmpeg installed on the system doesn't seem to fix the issue, which leads me to think that we have some sort of configuration issue related to the MediaPipe.NET.Runtime building script on MacOS.
Here are all undefined MacOS symbols in a text file (no indication of whether they are being resolved at runtime or not).
If you have a MacOS system, you can get them by typing the command
nm -gu <path-to>/libmediapipe_c.dylib
.undefined-macos-symbols.txt
The text was updated successfully, but these errors were encountered: