http://www.sqlite.org/compile.html
Read section 1.4 -- tells you all you need to know. First thing you should do is see if there's any significant performance difference with -Os instead of -O3. You may be surprised. Michael D. Black Senior Scientist NG Information Systems Advanced Analytics Directorate ________________________________ From: sqlite-users-boun...@sqlite.org [sqlite-users-boun...@sqlite.org] on behalf of Baruch Burstein [bmburst...@gmail.com] Sent: Tuesday, July 12, 2011 8:10 AM To: sqlite-users@sqlite.org Subject: EXT :[sqlite] Minimize sqlite3.o size I assume this is the same for sqlite3.dll or sqlite3.lib, but if not, I am interested in sqlite3.o (mingw32). How can I minimize the size of the library (compiling with -O3, since speed is my top concern, so different optimizations is not an option)? If I know there are parts of SQL I don't need in my program (like JOIN or ATTACH or triggers), can I remove support for them (this is for an embedded system and every byte counts, or at least every 100 bytes or so)? What pre-processor options can I set to remove things like FTS or R-Tree support which I do not need? Are there any other things easily removable that I might not need and might not even know they exist in order to remove them? How about some of the c API? Most of it I never use. _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
