Re: exclude (r)depends

[Jaap de Jong <jaap.dejong@nedap.com>]

On 08/04/2011 12:07 PM, Paul Eggleton wrote:
> On Thursday 04 August 2011 10:46:53 Jaap de Jong wrote:
>> I've build a simple recipe.
>> Bitbake figures it depends on libsqlite0 and libsqlite3-0; which is
>> correct by the way...
>> For some reason I don't want the dependencies in the ipk file.
>> Is there some flag for this?
> There's no "flag" for this because just taking away the shlibdeps-generated
> RDEPEND will almost certainly break the application/library at runtime. There
> are a few correct ways to solve it:
>
> 1) If the part of the binary output that needs sqlite is a plugin or otherwise
> optional module, just put it into a separate package (e.g. using
> PACKAGES_prepend = "${PN}-sqlitemodule" then FILES_${PN}-sqlitemodule =
> "${libdir}/libsomethingsqlite.so.*". Then your main package (${PN}) should not
> depend on sqlite anymore, as long as it doesn't have a hard dependency on the
> sqlite-using module.
> 2) Disable the sqlite dependency during configure, or if that can't be done,
> patch the source to acheive the same effect.
>
> 3) Depending on how complex the program is, with extra effort you could patch
> the source to turn it into an optional runtime dependency by using dlopen(3)
> instead of linking to sqlite during the build.
>
Probably the easiest way for me is to remove the specific *.so files 
after building.
Thanks for your support!

Jaap