On Sun, Jan 15, 2012 at 15:17:37 -0600, Bill McCormick wrote:
> Tim Streater wrote, On 1/15/2012 3:00 PM:
> >On 15 Jan 2012 at 20:44, Bill McCormick<wpmccorm...@gmail.com> wrote:
> >
> >>What is the problem with the shared lib stuff?
> >>
> >>Black, Michael (IS) wrote, On 1/15/2012 2:27 PM:
> >>>A simple one -- and please compile sqlite3.c into your program and make
> >>>everybody happy.
> >>>
> >>>Forget the shared library stuff as we have just been talking about.
> >The problem is that the computer vendor installs a shared lib with
> >a version of the library. Some 3rd party app installer then replaced that
> >shared lib with another version, and existing apps don't like it.
> >
> >SQLite is small enough that it can be compiled and linked in in its entirety.
I am quite certain Debian requires packages to be linked dynamically to
libraries that are packaged, the strongest reason being security support.
Of course since Debian package declares dependency and versions, 3rd party
installer won't just replace the shared library with incompatible version.
> OK. I don't see this as a problem for my use case. It would be
> better for me to stick with the shared libs.
>
> What is the difference between the two libs: libsqlite.so.0 and
> libsqlite3.so.0? I assume that I'll be linking to libsqlite3.
When you are compiling, you link against the .so file, which is symlink to
the actual .so.0 file. That file is provided by 'libsqlite3-dev' package and
is called '/usr/lib/libsqlite3.so'. The corresponding linker option is
'-lsqlite3'. Since the header is installed as '/usr/include/sqlite3.h', you
don't need any special options for compilation step. To see where the files
are, use 'dpkg -L libsqlite3-dev'.
--
Jan 'Bulb' Hudec <b...@ucw.cz>
_______________________________________________
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
