Android, Gradle and source control systems

I have an Android app that is being recorded in Android Studio and therefore configured to use gradle as my build system. The source is in ClearCase. Using the generated gradlew script, anyone can build an app from the command line without first installing gradle, but they need to configure all Android devices on their local machine. Ideally I would like to put the sdk in source control and point to gradle. My project has a local.properties file with the following content:

## This file is automatically generated by Android Studio.
# Do not modify this file -- YOUR CHANGES WILL BE ERASED!
#
# This file should *NOT* be checked into Version Control Systems,
# as it contains information specific to your local configuration.
#
# Location of the SDK. This is only used by Gradle.
# For customization when using a Version Control System, please read the
# header note.
sdk.dir=/Applications/Android Studio.app/sdk 

      

Obviously I don't want to modify this file or check against the original control, but the comment seems to indicate that there is a way to do what I want. My question is, does anyone really know where I can find the "title" or what information I find there?

+3


source to share


1 answer


We are building using the same tools and are facing this problem. We decided to point sdk.dir to a storage location outside of ClearCase where Gradle can read it. We also install the Android SDK on share so that developers don't have to install it on their desktop. This is especially important when we need to build against multiple SDK versions.



0


source







All Articles