aboutsummaryrefslogtreecommitdiffstats
path: root/build/tools.windows.atree
Commit message (Collapse)AuthorAgeFilesLines
* SDK: build 'monitor' tool and package it in the SDK.Raphael Moll2012-04-231-6/+7
| | | | | | | | | | | | | | | Fixed with Siva to use the 'ant' builder from Eclipse's baseBuilder jars. Changed to use: - the new external/eclipse-basebuilder for the basebuilder jars. - the rcp deltapack, located prebuilts/eclipse. - monitor scripts are now in sdk/monitor. - configuration is now in out/host/eclipse/rcp/build/configuration and doesn't change any existing repos. Requires change I7ab027ff6 from build.git Change-Id: I72fff09231fc9b3031c10eb42ff821c55af9b5d5
* Move stuff from prebuilt to prebuilts/toolsXavier Ducrohet2012-04-031-0/+8
| | | | | | | Also moved some atree copy from development to here where they belong. Change-Id: Ic08bed36b7de833e767d972156b2b9b7bf249aa7
* Fix build: disable monitor RCP in sdk.Raphael Moll2012-03-231-4/+5
| | | | Change-Id: Icd7081c1b6285b76e3e08307b125b6dbb546cfcb
* Build Monitor RCP as part of SDK (Mac, Linux and Win)Raphael Moll2012-03-211-0/+6
| | | | | | | | | | | | | | | | This adds a new SDK/tools/monitor[.bat] wrapper as well as SDK/tools/lib/monitor-x86[_64]/ directories that contain the actual RCP application. The monitor shell wrappers + bat have not been properly tested yet. The goal of this CL is just to build the RCP. In a following CL we'll adjust the wrapper and the actual binary location in the SDK. Cross-dependency: Requires build.git change Ifb31e2e3. Change-Id: I7afbd63badfb81fd5d3d899de672e02525a49bc2
* SDK: add find_lock.exe to atreeRaphael Moll2012-02-061-0/+2
| | | | Change-Id: If6ca019f644ed3d33d5ce7ceac68686430fa13c7
* Win SDK: fix build; build find_java for tools.atreeRaphael Moll2012-01-271-5/+8
| | | | Change-Id: I400ea2af6f749c1c4b2048a8cb4f7e2f173b5cf4
* SDK: use new find_java.exe in SDK bat filesRaphael2012-01-261-3/+2
| | | | Change-Id: I9f3fc572c3af6d8457a75cebae1aa6a850511afc
* SDK: remove find_java.exe from SDK.Raphael Moll2012-01-251-1/+2
| | | | | | That's just temporary till I fix the build. Change-Id: I27c5a9556265467d5317f1775703d7401ed1e079
* Windows: "find_java" exe and lib for android.batRaphael2012-01-251-1/+1
| | | | | | | | | | | | | | | | | | This adds a "find_java.exe" that will be packages in SDK/tools/lib. It will be used by android.bat and the other launchers to locate the best version of java to use for our tools (currently we have a find_java.bat that uses DOS commands to achieve something similar but more limited). In addition this creates a static "findjavalib" that is used by the NSIS installer to locate java and get its version (to complain in case we only find a Java 1.4 or lesser). The goal is for the installer to use the same logic as the tools will use to locate the java binary. Change-Id: Ic2efb388135087bab9687c3332882047fd041b1c
* SDK Windows: more ways to find java.Raphael2012-01-231-2/+0
| | | | | | | | | | | | | Also properly redirect command-line output to the parent shell console. This is experimental. This CL removes "android.exe" from the Windows tools and only keeps android.bat. However in a next CL android.bat will be changed to use 'find_java' to locate the best Java exe around (this is currently done in a bat script) Change-Id: I6e5485fdf59fde9838cf929ff333e1c611ea7bb4
* Upgrade bundled Proguard to version 4.7Tor Norbye2012-01-111-3/+3
| | | | | | | | | | | This changeset switches the build script from picking up the platform version of Proguard (in external/) to the new Proguard 4.7 library in the prebuilts/tools repository. (We now also include examples/ and docs/, but exclude src/ and build/ from the 4.7 distribution.) Change-Id: I6fd32cb568252bc80e85ddb7ae821bc02c22711a
* SDK: temporarily package both android.bat and android.exeRaphael Moll2011-12-011-2/+2
| | | | | | This is temporary as I continue working on android.exe Change-Id: I60d5206455798e70468c66930c6f3723e18c0198
* SDK: Switch back to android.bat.Raphael Moll2011-11-281-1/+3
| | | | | | | android.exe is not ready for usage yet. The local sdk parser can still detect both. Change-Id: I597f9b5553628b55703aa12282b2808c0b6d1fb1
* SDK: Switch from android.bat to android.exeRaphael2011-11-141-1/+1
| | | | Change-Id: I549340bdaaf78d6d314992ad2b91e9b45f97d2c2
* Remove layoutopt; replaced by the more generic "lint" tool.Tor Norbye2011-10-261-3/+0
| | | | Change-Id: Ia6dc357106aa49fa5c27c6283eac62c4cc19967b
* Static analyzerTor Norbye2011-10-201-0/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This changeset adds a static analyzer, "lint", which looks for various potential bugs in Android projects. It has 3 parts: (1) A library which performs the actual static checks. This library is standalone: it does not depend on Eclipse. (Technically the library has two halves: an API half, for use by third party developers to write additional detectors, and an actual implementation of a bunch of built-in checks.) (2) A command line driver, "lint", which runs the static checks and emits any warnings to standard out. This can be thought of as a replacement for the layoutopt tool. (3) Eclipse integration. Lint errors are added to the Problems view as well as shown as editor annotations. There's an options panel for controlling which detectors are enabled. There's also a quickfix for disabling errors directly within the editor and a marker resolution for disabling them via the Problems view. The static checks are run on an XML file right after it has been saved. (This is optional via a toggle on the same preference page as the detector list.) The static checks are also run when you export an APK, and if any fatal errors are found the export is abandoned. (This is also optional via an option). Finally you can run a full lint through the Android Tools menu, and there's also an action to clear all the lint markers there. There's also a new indicator on the layout editor which shows whether there are lint errors on the associated file, and when clicked brings up a dialog listing the specific errors. This changeset also includes a number of checks: * An accessibility detector which warns about images missing contentDescriptions * A drawable selector detector which warns about state lists where not all states are reachable (e.g. it is not the case that only the last item in the list omits a state qualifier) * A detector finding duplicate ids, not just in the current layout but across included layouts (transitively) as well * All the layoutopt ones ported to Java + DOM * Unit tests for the above. The focus here is on getting the infrastructure in place, and it currently focuses on XML resource files and analyzing them efficiently. See the comment in XmlVisitor for details on that. Change-Id: Ic5f5f37d92bfb96ff901b959aaac24db33552ff7
* SDK: fix typo in atreeRaphael Moll2011-10-061-1/+1
| | | | | | it's hprof, not hprov. sigh. Change-Id: I81a5cb107c18a94fa48c5643a57178407693b83c
* Build AVD Manager.exe as part of Windows SDK.Raphael Moll2011-09-191-2/+4
| | | | | | | Also make sure the sdk manager post install will update the AVD Manager as required. Change-Id: I969899adf69f0ed0ddb1ef079451683dd0ce567f
* Use atree for the Windows SDK. Strip binaries.Raphael2011-09-151-0/+95
This moves the copy/strip/rm logic for the Windows SDK fro mthe patch_windows_sdk.sh to a regular tools.windows.atree. The bash script is still here to invoke atree and do whatever cleanup we might want to do later. This should make it easier to maintain the Windows SDK by providing a structure similar to tools.atree. This change requires build.git Change-Id: I22aae7a8 to have rm/strip support in atree. Change-Id: Ie6c30979454fb71fc1cb26ab3f6c38acd47bae57
generated by cgit v1.1 at 2024-12-23 23:48:38 +0000