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

Solved Missing Lua Library in Ubuntu 18.04 #4

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

gustavohmsilva
Copy link

Problem: lua53.pas couldn't find liblua5.3-dev in my System...
Simple solution really. Probably also affects Mac OS X, as it also put a dot between 5 and 3 in the liblua5.3.so library when installed with Homebrew, Discrepancy identified when I ran the command

$ ldconfig -p | grep liblua

Problem: lua53.pas couldn't find liblua5.3-dev in my System...
Simple solution really. Probably also affects Mac OS X, as it also put a dot between 5 and 3 in the liblua5.3.so library when installed with Homebrew, Discrepancy identified when I ran the command ldconfig -p | grep liblua
@heX16
Copy link

heX16 commented Mar 4, 2019

Download official binaries from: https://sourceforge.net/projects/luabinaries/files/5.3.5/Linux%20Libraries/

Open archive, see: liblua53.so

Your patch ("LUA_LIB_NAME = 'liblua5.3.so';") is not correct.

May be need add IFDEF for Mac OS X? (if Homebrew place '.').

@gustavohmsilva
Copy link
Author

gustavohmsilva commented Mar 4, 2019

I can confirm that Ubuntu Linux 16.04 and 18.04 also don't store the lib as liblua53.so, but as liblua5.3.so

It is probably best to change line 106: LUA_LIB_NAME = 'liblua53.so'; to liblua5.3.so for the sake of compatibility.

Today's age Lua libraries are standard on all linux package managers and homebrew on Mac OS, and they are all always installed as liblua5.3.so

It makes more sense to change the source code of your project, IMHO.

@heX16
Copy link

heX16 commented Mar 5, 2019

Then need to inform the project lua that they have an incorrect file name in the archive.

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

Successfully merging this pull request may close these issues.

2 participants