SDKs with multiple libraries should be application configurable

So, suppose we have an SDK with libraries A, B, and C. By default, the SDK build script will build all of these and package them up.

However, suppose we have an application X, that only needs library B. X's build script should be able to configure the SDK so that it only makes B (and any dependents of B).
