>Von: sqlite-users [mailto:sqlite-users-boun...@mailinglists.sqlite.org] Im >Auftrag von Nico Williams > >On Tue, Aug 01, 2017 at 10:56:47AM -0700, Matt Chambers wrote: >> load_extension() has the very sensible behavior of: >> > So for example, if "samplelib" cannot be loaded, then names like >> > "samplelib.so" or "samplelib.dylib" or "samplelib.dll" might be >> > tried also. >> >> I would like to see that extended to include "libsamplelib.so" since >> that is the default naming scheme on many *nix platforms. This simple >> change would allow me to use the same base library name for my >> extension on both Windows and Linux. Otherwise I have to modify my >> build system to override its default behavior of adding the lib prefix on >> Linux. > >You're mistaken. > >lib<name>.so is NOT "the default naming scheme on many *nix platforms". > >lib<name>.so is the naming scheme when you want the link-editor (e.g., >ld(1)) to find a library using -l<name>. > >But loadable modules are almost never meant to be used that way. >They're usually meant to be used only through dlopen() and friends. >
Which other method apart from dlopen() would you recommend for dynamically loaded extensions? We are using virtual tables to interface with diverse data stores and make them queryable with SQL. The general interactive shell needs access to a certain subset of functions, and some speciality tools have dedicated loadable extensions that should not be accessible outside of that scope. ___________________________________________ Gunter Hick Software Engineer Scientific Games International GmbH FN 157284 a, HG Wien Klitschgasse 2-4, A-1130 Vienna, Austria Tel: +43 1 80100 0 E-Mail: h...@scigames.at This communication (including any attachments) is intended for the use of the intended recipient(s) only and may contain information that is confidential, privileged or legally protected. Any unauthorized use or dissemination of this communication is strictly prohibited. If you have received this communication in error, please immediately notify the sender by return e-mail message and delete all copies of the original communication. Thank you for your cooperation. _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
