-
Notifications
You must be signed in to change notification settings - Fork 58
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
Fixed linking wx.dylib with lua library (when building on macOS with … #45
Conversation
…external lua library)
Did it work without the fix? |
@valid-ptr, I'm not sure why this is needed. I'm building on macOS with an external library and don't see any issues. Here is the cmake command: https://github.com/pkulchenko/ZeroBraneStudio/blob/master/build/build-macosx.sh#L304 |
I was asking if it worked without the fix because: According to http://lua-users.org/wiki/BuildingModules modules should not link against lualib except for windows. |
It does work for me on both macOS and linux with the current configuration (without the fix). |
This is my configuration (perl):
I think, the reason of linking error is, that static (archive) liblua5.1.a used in my configuration instead of liblua.dylib in your configuration. ERROR OUTPUT IN CONSOLE:
PS |
But you do want to reference an external library, right? Or are you trying to build a static executable?
It has a long list of framework libraries (with libSystem, libiconv, libc++, and libobjc), but nothing lua-related.
Why don't you want to reference |
I agree with @sonoro1234. I think you should not link against liblua and rather specify
This suggests that you are mixing 32- and 64-bit libraries. You are compiling a 64-bit library, but if you run |
@valid-ptr, closing this one, as I don't see this as an issue. Feel free to re-open if you have any new information. |
…external lua library)