-
-
Notifications
You must be signed in to change notification settings - Fork 138
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
Can not build with lua-lib option #218
Comments
What about changing |
Hmm. Yes, calling it The intention is really to allow I think a generic name is really the best we can (and should) do here. |
Thanks for the timely report, BTW. I appreciate the testing and the feedback. |
I think we can add a prefix to all modules, like |
Anyway, the easiest way should be change the pxd file's name. Maybe |
That's not what you'd want to write as a user, is it?
It's not about loading the Lua library. Each of the version modules is a complete (and usually statically linked) copy of the lupa module.
It's possible that someone uses that |
BTW, there is another issue related to this commit. If you build with this option on windows, lupa will inject a |
With the latest commit(3016db8), lupa seems to generate
lua.pyx
whenlua-lib
andlua-includes
is set, which conflict withlua.pxd
because cython thinkslua.pyx
is the implementation forlua.pxd
. Choosing another name for it should be fine. For instance,_lua.pyx
.The environment:
The text was updated successfully, but these errors were encountered: