Linking with different library based on Flavor

(Dimitar Dimitrov) #1

Using the current native plugins, I need to define a variant of a library that links against shared dependencies, and another one that links all dependencies statically.

Right now I am defining different components, but I thought that this is a good use of a “flavor”, as the binaries are functionally equivalent.

But only then I realized that unlike the Android plugin, the native flavors are not available in the component definition (they seem to be available only at “binary spec” level.

Any suggestions?