aboutsummaryrefslogtreecommitdiffstats
path: root/layoutlib_api/src/com/android/ide/common/rendering
diff options
context:
space:
mode:
authorRaphael Moll <ralf@android.com>2011-05-02 14:24:26 -0700
committerRaphael Moll <ralf@android.com>2011-05-04 14:03:15 -0700
commit9294085c94ef94939fef467af411fc3f0723003c (patch)
treedd478997c3c9e089730fce8ebf6e1cbf7ab263f3 /layoutlib_api/src/com/android/ide/common/rendering
parentaca790d38fc768d84c44783fad5db1c997b52735 (diff)
downloadsdk-9294085c94ef94939fef467af411fc3f0723003c.zip
sdk-9294085c94ef94939fef467af411fc3f0723003c.tar.gz
sdk-9294085c94ef94939fef467af411fc3f0723003c.tar.bz2
Merge "SdkManager: handle missing platforms/ and add-ons/ folders."
A while ago, when we were dealing with monolithics SDKs, the strategy was that we wanted to make sure that the 'android' command was invoked from a properly setup SDK folder. Consequently the SdkManager required at least the platforms/ and add-ons/ folders to be present, even if empty. I don't think that behavior is really necessary anymore. The 'android' tool is invoked with knowledge from its tools folder, so we can safely assume the top parent is "the SDK folder" and create these directories if they are missing. We do however try to create them as early as possible if they are missing, so that the tool aborts early if we can't create them. The other alternative would be to just try to create them when we're actually installing a package. (cherry picked from commit a77c147c9e7ed3ef0c99cb2cdf986603e6d229cf) Change-Id: I6da1710b1a1844931bdb99d840ae575f53a9b947
Diffstat (limited to 'layoutlib_api/src/com/android/ide/common/rendering')
0 files changed, 0 insertions, 0 deletions