| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
This reverts commit 7f3cb91779907c12d02e8e5c5f4a6a7c510d210e.
|
|
|
|
|
|
| |
Make dsl changes due to gradle update.
Change-Id: I65729783f5c8f985ed31a231e7dd9a0b9e50f7b3
|
|
|
|
| |
Change-Id: I93a2e42fb0a81d1495bb12b657b6bd6a597a128e
|
|
|
|
| |
Change-Id: I3062b447167a9d2d479a7205a5236176946d4e54
|
|
|
|
| |
Change-Id: Iacff7f6bfe95a2a95b85cf00cd3e2dd34e5358b6
|
|
|
|
| |
Change-Id: I02ee9cdbb9f721ffdbeb1c285cfc85711779004e
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This fixes 2 issues:
- A bug in android.bat was that the bat+lib were
only copied if the arguments were 'update sdk'.
However since Tools R14 the sdkmanager doesn't
use these arguments anymore.
- Consequently when invoked as 'android sdk' it was
not copying itself in the temp folder and thus
was locking the tools folder, preventing updates.
- The new behavior is to always copy, like that we
don't care how the app is launched.
- The SDK Manager.exe was launching android.bat and
then waiting for it to finish, capturing its
stdout in care there's an error to display.
That locks SDK Manager.exe and thus prevent from
updating it too. So instead we just don't wait for
the bat to finish, don't capture/display its stdout.
If there's an error, the user can still use the
command line version to find out what's wrong.
SDK Bugs: 21212:SDK Setup.exe [keeps] an open file handle
SDK Bugs: 11989:SDK Manager.exe should be able to detach
(it doesn't do the part where the sdk manager could restart
itself after an update though. I'll file a different issue.)
Change-Id: Id473ce58d3f36d417b6c0ee5f07a039adbbe06c0
|
|
In Tools R14, the Windows SDK will have 2 icons in the root
of the SDK: one to launch the AVD window, and a different one
to launche the SDK Manager window.
I'll need to change the icon in a later CL. I don't have
any ICO editor at hand right now.
Change-Id: Ic651e3c3d71c2eac5fe851fba8ea2782eca5e594
|