Shared library packaging

[Gary Thomas <gary@mlbassoc.com>]

I'm working on a recipe which has a number of shared libraries (actually
this is just an import from OE (mozilla/nss) which has the same problem as listed below)
The package creates a number of libraries (from the work tree):
     image/usr/lib/libsmime3.so -> libsmime3.so.1oe
     image/usr/lib/libsmime3.so.1oe
     image/usr/lib/libsoftokn3.so
     image/usr/lib/libfreebl3.so
     image/usr/lib/libnssutil3.so -> libnssutil3.so.1oe
     image/usr/lib/libnssutil3.so.1oe
     image/usr/lib/libnss3.so -> libnss3.so.1oe
     image/usr/lib/libnss3.so.1oe
     image/usr/lib/libssl3.so -> libssl3.so.1oe
     image/usr/lib/libssl3.so.1oe

The .so.1oe files are packaged in nss_XXX.ipk and the .so files are
put into nss-dev_XXX.ipk.  The problem is that there is code out there
that only wants to look for the .so files (no -dev packages installed)
and fail to find libsoftokn3.so and libfreebl3.so

Is there a way to [easily?] force these two libraries to be packaged
into nss-XXX.ipk?

My current workaround is to use a post-install script to create the .so
files from the .so.1oe files for these two libraries.  It gets my code
(chromium-11 browser!) to work, but it's not very satisfying.

Any ideas?  Thanks

-- 
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------