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

Using existing copies of lua, pcre2, sqlite3 instead of built-in copies #494

Open
ryandesign opened this issue Apr 1, 2024 · 2 comments

Comments

@ryandesign
Copy link

I see that tup bundles lua 5.4.6, pcre2 10.42, and sqlite3 3.45.2. I already have these installed on my system, and in the case of pcre2 my version is newer. How can I tell tup to use these existing libraries instead of building its own?

@gittup
Copy link
Owner

gittup commented Apr 1, 2024

Lua is slightly modified in tup to support things like the += operand, so if you used a local version you would find that some Tupfile.luas would fail to parse. As such, there isn't a supported way to use a local version, though you could modify tup's own Tupfiles yourself if you were interested in pursuing this.

SQLite3 is also built-in by default for performance reasons, though it is not modified from the stock version (other than to specify specific compilation flags). You can use a local libsqlite3 by adding this to the tup.config used to build tup:

CONFIG_TUP_USE_SYSTEM_SQLITE=y

For pcre2, the embedded version is only used on Windows since there isn't a native packaged version easy to use. On Linux and macOS, the system's libpcre2 is used by default.

@ryandesign
Copy link
Author

SQLite3 is also built-in by default for performance reasons

How would SQLite3 being built-in result in better performance than an external SQLite3?

adding this to the tup.config used to build tup

What's tup.config? See #496.

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