The image is missing, so a vital part of our question isn't visible.
That being said, we usually update sqlite when we need to to fix NSS issues, or if NSS needs to use more advanced sqlite features.
Many users of NSS provide their own copy of sqlite (either because they have their own copy as part of a larger application... like firefox, or because sqlite is provided by the os (like many Linux distributions). If you are concerned with shipping or using the older version of sqlite3, you could build our own from the sqlite3 project and use it.
bob
Any help greatly appreciated
Thanks.
--
You received this message because you are subscribed to the Google Groups "dev-tec...@mozilla.org" group.
To unsubscribe from this group and stop receiving emails from it, send an email to dev-tech-cryp...@mozilla.org.
To view this discussion on the web visit https://groups.google.com/a/mozilla.org/d/msgid/dev-tech-crypto/88ae58f8-c4c2-4f91-aa85-eccc3c745d71n%40mozilla.org.
To view this discussion on the web visit https://groups.google.com/a/mozilla.org/d/msgid/dev-tech-crypto/d868fcdb-cd3a-c49b-66af-00c389425b8e%40redhat.com.
To view this discussion on the web visit https://groups.google.com/a/mozilla.org/d/msgid/dev-tech-crypto/CAPLxc%3DV%2BGO24kXmaQGw1QCGx3ef4vE5r42ytHyoOrwC48ShnMg%40mail.gmail.com.
Hello
Thank you both for your responses.
Forgive me but I do have few follow up questions:
In event say a machine (windows or Linux) have latest version of sqlite ( system provided or say built manually ) , what needs to be done for NSS to pick it up ?
Do we need to build NSS with certain option so it can link to the machine’s SQLite ? In event there’s none on machine, I’m assuming NSS will default to using it’s own SQLite?
The easiest way is to build with system_sqlite:
./builds.sh --system-sqlite {your other build options}
for ninja/gyp builds or
export NSS_USE_SYSTEM_SQLITE=1
gmake nss_build_all
gmake builds
it's possible you can just make sure your copy of sqlite is in your path and remove the nss built one as well (I haven't tried it, but the only thing that would prevent it from working is any .dll config difference between the system shared library and the nss built one.
If you build with system-sqlite you'll need to have the system-sqlite build environment installed at build time. If sqlite isn't on your system, NSS would fail (the libraries are direct link, so the systems loader will fail to load nss if it can't find a matching sqlite. You could also use the system function to include your own sqlite. Go to sqlite upstream and pull and build it yourself, the install the header files. You can then build nss with the --system-sqlite and NSS would end up using your own built sqlite.
bob
bob