"When I compile on my linux box (SuSE 10.1) using GCC 4.1.0
and leaving out all the optional featuers of SQLite, I get
a library size of less than 166 KiB."
I would be very curious to know how exactly you leave out optional features.
If I write even a simple program using only the barest of calls:
sqlite3_open()
sqlite3_exec()
sqlite3_free()
sqlite3_close()
It's 599k.
I'm assuming you are specifying the options somewhere...config file...?
Thanks!
[EMAIL PROTECTED] wrote:
tim <[EMAIL PROTECTED]> wrote:
Hi,
I'm developing on an arm-elf platform that uses a flat binary (elf2flt)
(mmu-less processor) and the smallest executable I'm able to generate
runs about 599k. Also it tends to want an equal amount of memory at
run-time, which the board
will not support (on top of the already running processes).
I was reading in the FAQ and it states something about binaries as low
as 150k.
When I compile on my linux box (SuSE 10.1) using GCC 4.1.0
and leaving out all the optional featuers of SQLite, I get
a library size of less than 166 KiB.
I've seen people compile on ARM to a much smaller size than that.
I'm not sure what you are doing to get a 500KiB library.
--
D. Richard Hipp <[EMAIL PROTECTED]>
-----------------------------------------------------------------------------
To unsubscribe, send email to [EMAIL PROTECTED]
-----------------------------------------------------------------------------
