You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've created an AUR package for LumoSQL. During creation of this package, it took quite a while to figure out what files were placed where, where to place the ./configure options and how to workaround not being able to execute make install in the generated and patched sqlite3 source directory. (breaks because of not-forking modification)
Not a fan of the custom Tcl build system. I do appreciate it was documented, though! Having an make install that takes a DESTDIR environment variable would help future packagers out.
When generating the package, all the header files, shared libraries and binaries are renamed to (lib)lumosql. As to not conflict with the main SQLite package, and to not cause issues in applications that rely on the old SQLite shared library behavior.
Is there a way to avoid building SQLite twice, by the way?
I've created an AUR package for LumoSQL. During creation of this package, it took quite a while to figure out what files were placed where, where to place the
./configureoptions and how to workaround not being able to executemake installin the generated and patched sqlite3 source directory. (breaks because ofnot-forkingmodification)Not a fan of the custom Tcl build system. I do appreciate it was documented, though! Having an
make installthat takes aDESTDIRenvironment variable would help future packagers out.When generating the package, all the header files, shared libraries and binaries are renamed to
(lib)lumosql. As to not conflict with the main SQLite package, and to not cause issues in applications that rely on the old SQLite shared library behavior.Is there a way to avoid building SQLite twice, by the way?