[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
Re: Writing buildlink files: references to ../mk/foo.buildlink3.mk
Edgar Fuß <ef%math.uni-bonn.de@localhost> writes:
>> You only need it if the dep is required at client build time; e.g. if
>> libbar uses libfoo, so libfoo's bl3 is in libbar's Makefile, it only
>> needs to put libfoo's bl3 in its own bl3 if its installed includes
>> depend on libfoo's.
> Hm. The Guide says:
>> Run ldd on all installed libraries and look against what other libraries
>> they link.
> That's what I did.
>> Some of the packages providing these probably need to be buildlinked;
> This is -- erm -- not very specific.
> If app depends on libbar and libbar depends on libfoo, then app/Makefile
> includes bar/buildlink3.mk. Now, if bar/buildlink3.mk would not include
> foo/buildlink3.mk, then building app would not see libfoo. Wouldn't that
> make linking app fail?
more or less:
If libbar.so references libfoo.so, then libbar/buildlink3.mk should
But if app depends on bar, and doesn't try to 1) link with libfoo or 2)
use libfoo's symbols, then app should not include libbar/buildlink3.mk.
This is hard to discuss in general. If you think there is a specific
bug (which I am willing to believe!), please point it out.
Main Index |
Thread Index |