This way, individual open-source device configurations can
publish device-specific configurations without having
to maintain those centrally in envsetup.sh
Bug: 2533998
Change-Id: I1377846d4d3ebe7abcd2f8279a08abe54039cdbb
Use the PWD= /bin/pwd trick used in getopt in mmm so that it can deal with a symlinked
root directory.
Change-Id: Ia8b5ef10cbd10ca05f2301db86f64fdf11ff2840
This makes runtest, in particular, happier, since it will now find that
its idea of the cwd actually matches with what's claimed in ANDROID_BUILD_TOP.
Change-Id: I485df382d9d314a73b410030bf2116215b6250f9
For debugging non-ANR weird states in the system server, it is incredibly handy
to be able to force a complete thread-stack dump of that process. Here's a
shell function that does so (creating the /data/anr/traces.txt file with the
usual permissions if it does not yet exist).
Depends on adb having been configured to run as root.
Change-Id: I01d9d733ef08ffefb00cb61968df36ecf62087f0
Merge commit 'bd1ee348a1891836cf3b5d0da72e75c0d256fa43'
* commit 'bd1ee348a1891836cf3b5d0da72e75c0d256fa43':
Also look in vendor/*/build for vendorsetup.sh
Merge commit 'a3896fbc15d32881d87e1ae8b7c6e2e7523008c7'
* commit 'a3896fbc15d32881d87e1ae8b7c6e2e7523008c7':
Change runtest env shortcut to point to runtest.py
People keep getting confused by the default products
in this list, which are almost never what they want,
because this list roughly corresponds to the DEVICES
and not the PRODUCTS.
Now that lunch works again, I'm not too worried about
choosecombo except for the couple of cases lunch can't
handle, like the simulator. Therefore, this change
just removes the list of suggested products, and you
have to know which one you're trying to build (which
seems like a resonable prerequisite).
This change does not affect device code.
Original author: brettchabot
Merged from: //branches/cupcake/...
Original author: android-build
Merged from: //branches/donutburger/...
Automated import of CL 143392
