5f15e3e63c
* Root cause of the issue is improper naming of variables. Turns out,
there was no variable to even denote where the blob should have been
searched for, at "src".
* Previously there was one such variable, suggestively called "TARGET", that
was desperately trying to serve as both, depending on who +2d hacks harder.
* One such example is "c982836 extract_utils: Fix makefile generation issues".
That patch deliberately trimmed the "src:" from a spec (therefore
obviously breaking the search at src) but enabling the searching at
dst, via the good-for-all TARGET variable.
* This patch introduces the following variables:
- SRC_FILE: absolute path corresponding to SPEC_SRC_FILE in the
Android filesystem.
- DST_FILE: absolute path corresponding to SPEC_DST_FILE in the
Android filesystem. Somewhat analogous to the old TARGET variable,
but actually contains the leading / as well (/system/bin/adsprpcd
instead of system/bin/adsprpcd).
* Use existing common get_file() function (which previously was
impossible to use, because it was impossible to determine calling
arguments properly) to reduce complexity of handling adb and disk
image as blob sources.
* Via the new SRC_FILE and DST_FILE variables, search for a blob in all
possible locations (including paths stripped of "/system" which
transforms an absolute path in the Android filesystem into a proper
relative path to that file in a disk image).
Change-Id: Ic40fb4dc93541d8b3f33fde586b773199cf4ded2
Signed-off-by: Vladimir Oltean <olteanv@gmail.com>
LineageOS
===========
Submitting Patches
------------------
Patches are always welcome! Please submit your patches via LineageOS Gerrit!
You can do this by using these commands:
(From root android directory)
. build/envsetup.sh
(Go to repo you are patching, make your changes and commit)
lineagegerrit <for(new)/changes(patch set)> <branch/change-id>
repo start lineage-15.1 .
(Make your changes and commit)
repo upload .
Note: "." meaning current directory
For more help on using this tool, use this command: repo help upload
Make your changes and commit with a detailed message, starting with what you are working with (i.e. vision: Update Kernel)
Commit your patches in a single commit. Squash multiple commit using this command: git rebase -i HEAD~<# of commits>
To view the status of your and others' patches, visit [LineageOS Code Review](http://review.lineageos.org/)
Getting Started
---------------
To get started with Android/LineageOS, you'll need to get
familiar with [Repo](https://source.android.com/source/using-repo.html) and [Version Control with Git](https://source.android.com/source/version-control.html).
To initialize your local repository using the LineageOS trees, use a command like this:
repo init -u git://github.com/LineageOS/android.git -b lineage-15.1
Then to sync up:
repo sync
Please see the [LineageOS Wiki](http://wiki.lineageos.org/) for building instructions, by device.
For more information on this Github Organization and how it is structured,
please [read the wiki article](http://wiki.lineageos.org/w/Github_Organization)
Buildbot
--------
All supported devices are built nightly and periodically as changes are committed to ensure the source trees remain buildable.
You can view the current build statuses in the [Jenkins](http://jenkins.lineageos.org) tool.