-
Notifications
You must be signed in to change notification settings - Fork 60
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
Request for feedback #178
Comments
is there any way this could be backported to the |
It's probably doable, but I didn't really want to introduce a stable branch until zig 0.14.0, and given zig 0.14.0 is intended to be released soon-ish, I don't think I want to do this work. However if anyone wants to work on this I'll happily review a PR. |
This looks to work fine for me with malcolmstill/clerk#43, just had to remove a |
Nice, thank you for testing ! |
I'm kind of surprised that the artifact doesn't exist anymore, not sure exactly what causes it to be available in the first place so I'll look into it. |
Nevermind, I found the issue, I removed the call to (but yeah, the |
Hello everyone,
I'd like to get feedback from users of zig-sqlite, if anyone happens to look at issues and sees this.
I recently worked on improving the build script in the use-upstream branch.
The main change is that we leverage the zig package manager to fetch the sqlite amalgamation instead of vendoring the source code in this repository.
I'm looking for people that can test their programs with this branch and report back if everything works fine; for people not using the loadable extension feature everything should be transparent.
If you are using loadable extensions however, there is a breaking change: you need to use the
sqliteext
module in your build script instead ofsqlite
.To summarize:
sqliteext
sqlite
I'll wait a couple of weeks before merging the branch.
The text was updated successfully, but these errors were encountered: