Different Ways to Set Gradle Home While Importing Existing Project in Android Studio
Table of Content Debugging build logic Other installation failures Cleanup of caches and distributions Link a Gradle project to an IntelliJ IDEA project Open an existing Gradle project I am building our potentially cross-platform and cross-language build environment entirely on gradle and the lack of support for adding component private include path is a blocking issue. Adding compiler flag is not maintainable across a lot of components and different tool chains... At the meantime, there seems to be a better workaround, taking advantage of source set dependency and NativeDependencySet. Basically, we have the source set depend on a specially generated NativeDependencySet, which returns the private include paths from its getIncludeRoots() function. As a result, the private include paths are added when compiling the source set, but will not be exposed to dependents of this component because dependency in gradle is not transitive. Sign up for a free GitHub account to open an issue ...