-
Notifications
You must be signed in to change notification settings - Fork 110
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
Import error on MacOS #37
Comments
I do not have a Mac at hand to test this, but I would tend to say that this dynamic linker issue should be reported to upstream VLC. I used to solve such issues with install_name_tool some years ago. |
Where can I find VLC 3.0 RC9? What is environment variable There is no problem with VLC 2.2.8 and Btw, if VLC 3+ does load multiple |
Using this VLC 3.0 RC9 build, the error is the same (for Python 2.7.14 and 3.6.4):
Both
However, the following command line does not show the error:
Modifying
Neither does setting But changing
|
Great work Jean. Could you submit a patch with this modification (so that authorship is preserved)? |
Will do. But why is this an suddenly an issue? Does it only happen with the macOS version of VLC?
/Jean
… On Feb 14, 2018, at 11:01 AM, Olivier Aubert ***@***.***> wrote:
Great work Jean. Could you submit a patch with this modification (so that authorship is preserved)?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.
|
Something must have changed in the macosx build chain. The extras/package/macosx directory of VLC has had lots of changes these last months. I would even expect that videolan/vlc@f6e51b0 (and the following one removing build-package.sh) look like the ones that could have introduced the issue. |
Submitted patch for the header.py file.
/Jean
… On Feb 14, 2018, at 11:59 AM, Olivier Aubert ***@***.***> wrote:
Something must have changed in the macosx build chain. The extras/package/macosx directory of VLC has had lots of changes these last months. I would even expect that ***@***.*** (and the following one removing build-package.sh) look like the ones that could have introduced the issue.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.
|
I don't see the patch. Where did you submit it? |
Not sure what happened. Redid the patch and it should be there now as mrJean1-patch-1.
/Jean
… On Feb 16, 2018, at 4:12 AM, Olivier Aubert ***@***.***> wrote:
I don't see the patch. Where did you submit it?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub <#37 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AVIMYZTZJd1hi4bWdYsf7hIKdxNbClwgks5tVUZ_gaJpZM4R4OBL>.
|
in my case, there is no C library in my system..
|
Just a quick note because this thread keeps popping up on my google searches: If you are packaging with pyinstaller for Mac, VLC.app MUST be installed in the applications folder for it to work smoothly. If VLC is not in the applications folder (for example you want your .app to work regardless if the user has previously installed VLC), you must add adding dylibs in the .spec file
vlc.py changed to look in
|
Importing libvlc doesn't work on MacOS. When I try to import VLC (using VLC 3.0 RC9) I get the following error:
It looks like
libvlccore.dylib
needs to be imported first before importinglibvlc.dylib
.The text was updated successfully, but these errors were encountered: