Re: Writing buildlink files: optional dependencies?

[Thomas Klausner <tk%giga.or.at@localhost>]

On Mon, Oct 14, 2019 at 12:19:54PM +0200, Edgar Fuß wrote:
> When creating a buildlink3.mk for a package foo that exposes libfoo, if 
> libfoo depends on libbar (from package bar), my understanding is that I 
> should include ../../whatever/bar/buildlink3.mk in foo's buildlink3.mk.
> 
> But how do I handle the case where foo only depends on bar when built with 
> the "bar" option? Do I consult PKG_OPTIONS.foo?


There is support for this. Look at e.g. gtk3/buildlink3.mk for an example.

> If yes, how do I make sure 
> that the newly created buildlink3.mk doesn't run out of sync with the 
> options.mk file (of foo)? The next version of foo built with the "bar" 
> option could depend on bar-ng.

You'll have to take care of that manually (and might need to bump ABI
if the dependencies change).
 Thomas