I believe the configure script is not maintained. It probably needs more patches than this.
Mike -----Ursprüngliche Nachricht----- Von: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Im Auftrag von Nicolas Williams Gesendet: Mittwoch, 20. Februar 2008 00:19 An: General Discussion of SQLite Database Betreff: Re: [sqlite] Given sqlite3_enable_load_extension(),why omit loadable extensions? On Wed, Feb 20, 2008 at 12:09:16AM +0100, Michael Ruck wrote: > This is most likely done to reduce compiled code size. For a lot of > systems this code probably is wasted space, as the feature is not used everywhere. > For embedded systems the ability to simply cut features at compile > time to reduce code size is very important. Thanks. I'm working on integrating SQLite3 into OpenSolaris. So I wonder if I should enable this feature, and what the risks are. The security risk is already addressed via sqlite3_enable_load_extension(). Interface instability might be a risk -- I don't know yet but I'll assume this is a risk. Finally, w.r.t. object code size, I see that the --enable-shared configure option only enables building a shared library -- it does not actually build the sqlite3 shell (nor sqlite3_analyzer) to use that shared library. That'd be a useful option, at least for us. Would you welcome a patch? Nico -- _______________________________________________ sqlite-users mailing list [email protected] http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users _______________________________________________ sqlite-users mailing list [email protected] http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
