Skip to content
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

error on windows executable #292

Closed
MidyGamy opened this issue Sep 23, 2023 · 6 comments
Closed

error on windows executable #292

MidyGamy opened this issue Sep 23, 2023 · 6 comments

Comments

@MidyGamy
Copy link

image
translation:
the procedure entry point decode URI could not be located in the dynamic link library

so when i compile the game and launch if from the exported executable, i get this error every time i load a video...
the thing is it doesn't happen when using the lime test windows command

@MidyGamy MidyGamy changed the title error on wondiws executable error on windows executable Sep 23, 2023
@polybiusproxy
Copy link
Owner

image translation: the procedure entry point decode URI could not be located in the dynamic link library

so when i compile the game and launch if from the exported executable, i get this error every time i load a video... the thing is it doesn't happen when using the lime test windows command

Your builds are missing the 'plugins' folder.

@MidyGamy
Copy link
Author

image translation: the procedure entry point decode URI could not be located in the dynamic link library
so when i compile the game and launch if from the exported executable, i get this error every time i load a video... the thing is it doesn't happen when using the lime test windows command

Your builds are missing the 'plugins' folder.

no its not

@polybiusproxy
Copy link
Owner

Then libvlc somehow can't find a function in the libqt4_plugin DLL file.

@MidyGamy
Copy link
Author

how can I fix it?

@polybiusproxy
Copy link
Owner

how can I fix it?

Do you have everything in your plugins folder? Make sure you're not missing anything.

@MidyGamy
Copy link
Author

ok for some reasons, removing that plugin fixed the thing...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants