-
Notifications
You must be signed in to change notification settings - Fork 340
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
Build a shared library and install headers #1100
Labels
enhancement
New feature or request
Comments
This mostly just didn't come up. All production applications that use Luau so far ship with statically linked library I believe. A couple things to know off the top of my head:
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I am curious why luau does not build a common shared library so one can package/update it separately from whatever project uses it? That's how it's done in the reference Lua and LuaJIT. Luau seems to only build static archives and hence needs to be linked statically. Any idea why -- is that by design or did the use case just not come up?
I'm looking to package Luau for Debian and only shipping static libraries is kind of frowned upon, since that would mean that an update of the library would need rebuilds of everything that depends on it if there are only static libraries.
I (and maybe others as well) would prefer to have a clear, installed set of library and headers (maybe also pkgconfig info etc) that would make Luau as a library immediately usable as most developers would expect it, with the least amount of surprise.
The text was updated successfully, but these errors were encountered: