| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
Change-Id: Idf12b9f222ad862bf5b8f0cc51b602eaf0924054
|
|
|
|
| |
Change-Id: I0421e319ec529feb0b6bcbfc3fe41350295afe5d
|
|
|
|
| |
Change-Id: I35126be74bfbbafb3c7acb047b8dc0076bd3b669
|
|
|
|
| |
Change-Id: I23d62d1778b798711d1ad666db3bead193f90ef2
|
|
|
|
| |
Change-Id: I77448d2769d2a15b64987ae7d9e2cb887aef3bc2
|
|
|
|
| |
Change-Id: I25f248244c588c36eeb92b4abb802a2877f3407b
|
|
|
|
| |
Change-Id: Ieceeae72231107ea4d49aa9dcb4a4c33220f5ffd
|
|
|
|
| |
Change-Id: Icb5be47b688808488811411a5f45a23a49f774d2
|
|
|
|
| |
Change-Id: I354930bdc6304908e447b4eb8b66f6f09b0ffb4c
|
|
|
|
|
|
|
| |
Similar to change I1913711556c17fe1799a963b52214f338768fffd
this is only provisional till the final versio number gets decided.
Change-Id: I976cd490a7dee07d4a6b0eaf98972bcd89620f80
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
We tried the approach of replacing bundled jars with OSGI
jars. However, this eventually ended up resulting in
ClassCircularityError thrown at runtime when running on
Java 7. As far as we could diagnose, the issue seems to
be that:
- LayoutLibrary attempts to load layoutlib.jar (which is
a regular jar present inside the android sdk data folder).
- The class loader passed to layoutlib is the LayoutLibrary's
class loader.
- The classes inside the layout library then attempt to
load classes from a different OSGI jar (layoutlib-api)
- At this time, we receive a ClassCircularityError
Most of our other jars depend on layoutlib-api, so it is
not possible to just bundle layoutlib-api. So for now, we
are back to bundling jars.
Change-Id: Ic8c838a1a7e90e1bc6b8c5251341b1ded46053ba
|
|
|
|
|
|
|
| |
The earlier CL to add this broke the existing PDE build scripts.
The PDE build has now been turned off.
Change-Id: Ica3b783af117ff1e52f53e6813ac8389c4bb80c9
|
|
|
|
|
|
|
|
|
|
|
|
| |
This CL removes all the jars bundled in inside the libs
folder and adds explicit dependencies on OSGI bundles
for each of the dependencies.
See eec615b94b504de6d87702b830a6fc85fc7d5108 for more
info on how the dependency jars are converted into
OSGI bundles.
Change-Id: I5356edc2ca857ea961392c599fa0e985b16b4b2d
|
|
|
|
|
|
|
|
| |
Breaks existing scripts.
This reverts commit 68bd64a51f78ae6a66bd8eea9baf07185e2b9588.
Change-Id: I2cfe3ba2cea94850f4273170fbb5a46d7b727633
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This CL adds all the required files to perform a build
using Tycho. It is not integrated into the Android build
system though. In order to perform a build, make sure your
repository has the git projects prebuilts/eclipse and
prebuilts/eclipse-build-deps, then do:
$ cd sdk/eclipse
$ make -f maven.mk
That should create the necessary target platform and start
a build using Maven/Tycho. The resulting artifacts should
be in out/host/maven/bundles-<version>/products
Change-Id: I4672cd9ea1ac072a9b5ddb27d98a9849b2a2b8cb
|
|
|
|
|
| |
Change-Id: Ia548e9c61a6d2d1ec121a86002af8810ba2f4340
(cherry picked from commit 81e48b1ba10e38ae10db1dbdefcba99758e9ffd2)
|
|
|
|
| |
Change-Id: I4ca7e5c5ab3d44cd2ccfc5ef26d0382c633d308a
|
|
|
|
| |
Change-Id: I596991ceef33ed2b09a2e18013e671cc2e2b26c5
(cherry picked from commit 17f167fdbc0c08b301a0f2debca1afc05aa6406e)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This CL allows users to control whether the device chooser dialog
will be displayed during a launch.
Currently, when performing a launch, the chooser dialog is displayed.
It has a checkbox for users to indicate that the same selected device
should be used for further launches. However, once set, there was no
way that the setting could be overridden to show the dialog again.
This CL mirrors that checkbox in the launch configuration. This allows
users to modify the launch configuration and disable the "Use last
selected device" checkbox, thereby forcing the chooser dialog to be
displayed again.
Fixes https://code.google.com/p/android/issues/detail?id=56076
Change-Id: I19dce8dd3acb76e799a422568267f28318b5ef58
(cherry picked from commit d43a349cecbf4c35b5d7286af4fe34a0a5aa693e)
|
|
|
|
| |
Change-Id: I388397dde0f465409e7cede32ce38cc91a8f94c3
(cherry picked from commit fc5197e3e4de338b895c2fb8c15faea60024dfb7)
|
|
|
|
| |
Change-Id: I14e95b886f39ffc73f14fbe201e7936e4fe57778
(cherry picked from commit 6598a14ec6f0bd983d22aef0c7bc1cfed66efb40)
|
|
|
|
| |
Change-Id: I85c92266998677c8f47b61ac539b32f7bb420afa
(cherry picked from commit 7e7b15172c324693555bb3657c28a26fc3129b32)
|
|
|
|
| |
Change-Id: I4c0fc9be7b64606d109dd636066f856d618465a0
|
|
|
|
| |
Change-Id: I6cd127ed7034ba33c32a1994bc312e187a15b250
|
|
|
|
| |
Change-Id: I0e4f2c0d56285b911f0210a3cddbed0f5ec05ecc
|
|
|
|
| |
Change-Id: I3cff176281b4949f814023f0c7ecda897bc1354b
|
|
|
|
|
|
|
|
|
|
| |
Turns off the ability to use @SuppressWarnings with optional
errors is available, but off by default (see Eclipse issue 392875).
This turns that off, makes missing enums in switch statements a
warning, and synchronizes the settings file to all projects (except
tests.)
Change-Id: Iad7060523b6ee2cbbca97e0a6ffedb264b185222
|
|
|
|
|
|
|
|
|
|
|
|
| |
Language Settings Provider is CDT's new scanner discovery
mechanism (http://wiki.eclipse.org/CDT/ScannerDiscovery61) introduced
with CDT 8.1.0. Until we migrate to that, this will allow scanner
discovery to work in CDT 8.0.x or with CDT 8.1.x without any user
intervention.
Fixes http://code.google.com/p/android/issues/detail?id=33788
Change-Id: Ie26d60cd33ceb5442dafd3fa116b5e381bef680e
|
|
|
|
|
|
|
| |
Move stuff out of sdklib into common and ide_common.
Remove androidprefs and move the one class into common.
Change-Id: I71d126a13cf2ba413692e29616f4968a37d7b33a
|
|
|
|
| |
Change-Id: Ic54d7e5b77bf6912b54855c5b30d8fcf790ff311
|
|
|
|
| |
Change-Id: I43add9790edf1418cd821f3486035f495fe45ad2
|
|
|
|
| |
Change-Id: Idde24b6b893d1029d48ba32766110a6a3cdf73c6
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
When checking whether a device can run a certain project,
the only valid conditionals are:
- If the device API level is less than the minApiLevel,
then the device cannot run the app.
- If the app is built against a standard SDK, then the above
check is sufficient.
- If the app is built against an add-on, then we cannot
determine for sure if a device can run the app.
An AVD might provide some additional info that can be
used to determine if the app cannot be run on a particular
AVD.
This CL fixes a bug where platforms with API level greater
than the build target API level were being filtered out from
the DeviceChooserDialog.
It also fixes another bug where running devices that are
clearly not capable of running an app were being displayed
in the DeviceChooserDialog, albeit with a red check mark
indicating that they cannot run the app. Selecting that
device for deployment would error out in the next step.
This CL filters out such devices.
Fixes http://code.google.com/p/android/issues/detail?id=35367
Change-Id: Iba31a45572dabe3895c4e51707ed515d407caae0
|
|
|
|
|
|
|
|
|
|
|
| |
There is no way to get out of the NDK preference page unless
a valid NDK is provided since Eclipse always pops up a message
saying that "the provided path is invalid".
This CL allows empty path to be a valid path and disables error
checking in such a case.
Change-Id: I4e5d5b975bd4629920f1b2750adec521c3a054a4
|
|
|
|
|
|
|
|
| |
Assume that extensions .exe, .bat and .cmd all refer to native
Windows executables. For such executables, do not use "sh"
(Cygwin shell) to launch them.
Change-Id: Ia04f69e85d8b7d7f4fc2421ae4c9839a3df914a0
|
|
|
|
|
|
|
|
|
| |
This patch fixes NdkCommandLauncher to:
1. Launch a command using "sh" only if it is a shell script.
2. If a command's path is given in Cygwin/Unix format on Windows,
convert to Windows format before it is actually used.
Change-Id: I27fc5865058fbefbfa9574f185b13d1023d15b97
|
|
|
|
| |
Change-Id: I5052717f3fc00979c0da1e5eab501fa24fe21684
|
|
|
|
|
|
|
|
| |
The assumption that there is only one platform inside NDK/prebuilt
is incorrect. This CL iterates through all the folders to locate
make.
Change-Id: Ie55f54052f2d591f315e79a86772d7b2cee57678
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
First, update our various project-specific Eclipse compiler settings
configuration files to include the new Eclipse 4 flags.
Second, turn off the "Unchecked conversion from non-annotated type to
@NonNull" warnings; there are hundreds or thousands of these, and
there isn't much we can do about them when they're coming from
platform and library APIs.
Third, make the lint projects warning-clean again by addressing
various warnings Eclipse found (such as some unclosed resources and
some null handling issues; yesterday's null annotation fixes only
addressed errors, not warnings.)
Change-Id: If75f7401a1cbeef1bf58b47ccaa9ad17bede7f91
|
|
|
|
|
|
|
|
|
|
|
| |
The ADT launcher has a cache of what device was used for a particular
launch, and reuses that device if the user has specified that the same
device should be used for future launches.
This patch moves that cache out to a separate class and reuses the
same cache for the NDK launcher as well.
Change-Id: I8aa266746e33dac82c9f16ca8877230e26c45c09
|
|
|
|
|
|
|
| |
If there is an error while launching gdbserver, display a hint
suggesting that NDK_DEBUG=1 should be added to the make command.
Change-Id: Ie563365019a5d40cfa403bccaa0e659f4a9f7bb9
|
|
|
|
|
|
| |
NDK plugin is under EPL.
Change-Id: I2af41f4e390511ed18474968c9f6de1bb6621774
|
|
|
|
| |
Change-Id: I41545372977a1505a6131238c92df16c91552317
|
|
|
|
| |
Change-Id: I47cb9636192005d91166a6949c8b40ef88d0905f
|
|
|
|
|
|
|
| |
This patch removes CDT's debugger tab and uses a custom debug
tab which provides only the options relevant to ndk-gdb.
Change-Id: Ia5273334bc39e5f5908d2d6d0f7702fe4f0655ce
|
|
|
|
| |
Change-Id: I7be205e4ee7ced2fa13c6a60ef0a554e2cb90db7
|
|
|
|
| |
Change-Id: I3877a7418da193cbe3759f25daafa3309bb8c05a
|
|
|
|
| |
Change-Id: Ia7ceed6297048779b9d591a518c2ae3c8cbfe60c
|
|
|
|
| |
Change-Id: I3906416a7b5a4bf7b7e2f86ee3155c22d93a3c2b
|
|
Change-Id: Ib340cec79f7aedab0309c707e70a9acb2438feb9
|