When performing a stand-alone Gradle `build` of a ...
# multiplatform
d
When performing a stand-alone Gradle
build
of a multi-platform module; it is natural that all variants are built. When including a multi-platform module as a project dependency, it's a reasonable default that all variants are built - since one expects any modules overall integrity to be verified in the build process. But as a heavy optimisation, wouldn't it make sense to have an easy option to build only the platform variant that's demanded by the project inclusion
i
Hm... unnecessary targets of a project dependency shouldn't be built. Could you share the project where you met this issue?