[SCIM] Library filenames

[Zhe Su]

You mean libscim-0.9.so.0 and libscim.so are different? Because, when
developing an app which want to link with libscim, you may just pass a
linker option like -lscim to g++. If libscim.so was renamed to
libscim-0.9.so then you must pass -lscim-0.9. It's not so convenience
because you may not know the version of libscim when linking the app.

This is the rule of libtool not me.

Regards
James Su

On Thu, 17 Jun 2004 20:44:19 -0500, Ming Hua <minghua at rice.edu> wrote:
> 
> Hi James,
> 
> I found out the libraries from SCIM are using a strange file name
> convention.  Take the main library, libscim, for example, I am seeing
> the following filenames installed (scim 0.9.6):
>     /usr/lib/libscim-0.9.so.0.0.6
>     /usr/lib/libscim-0.9.so.0 (symlink to libscim-0.9.so.0.0.6)
>     /usr/lib/libscim.so (symlink to libscim-0.9.so.0)
>     /usr/lib/libscim.a
>     /usr/lib/libscim.la
> Why are runtime libraries and development libraries using different
> names?  Is it intentional, or I messed something up in my compiling?
> 
> (This is also true for CVS head, just with -0.99 suffix instead)
> 
> Thanks,
> Ming
> 2004.06.17
> 
> --------------------------------------------------------------------------
> Wireless telegraph is not difficult to understand.  The ordinary telegraph
> is like a very long cat.  You pull the tail in New York, and it meows in
> Los Angeles.  The wireless is the same, only without the cat.
>                                                        --- Albert Einstein
> --------------------------------------------------------------------------
> 
> _______________________________________________
> scim mailing list
> scim at freedesktop.org
> http://freedesktop.org/mailman/listinfo/scim
>