No description
11d5cdb86f
We have been using a system where each vendor makefile needed to be updated for each release. This leads to both redundancy and inconsistency across devices. This patch externalizes version code to the common_versions.mk. As we all know CyanogenMod versioning works as such: MAJOR.MINOR.MAINTENACE.DEVICE_SPECIFIC (i.e. 7.1.0.1) common_versions.mk now contains the first three in the form of the following variables: PRODUCT_VERSION_MAJOR, PRODUCT_VERSION_MINOR, PRODUCT_VERSION_MAINTENANCE. Additionally, each device makefile contains two additional flags which control both the release name (the name that appears in the generated zip) and the device-specific version (empty by default, to be bumped on a per device basis), example: PRODUCT_RELEASE_NAME := XperiaArc-LT15i PRODUCT_VERSION_DEVICE_SPECIFIC := .1 Change-Id: I15d18e27b89ea00109a61cb66e3bffbb061a2ed4 |
||
---|---|---|
overlay | ||
prebuilt | ||
products | ||
tools | ||
.gitignore | ||
Android.mk | ||
CHANGELOG | ||
CHANGELOG.mkdn | ||
extract-gapps-files | ||
extract-google-files | ||
get-rommanager | ||
LICENSE | ||
prelink-linux-arm-hero.map | ||
prelink-linux-arm-msm722x.map | ||
README.mkdn | ||
vendorsetup.sh |
CyanogenMod =========== Submitting Patches ------------------ Patches are always welcome! Please submit your patches via CyanogenMod 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) cmgerrit <for(new)/changes(patch set)> <branch/change-id> repo start gingerbread . (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 [CyanogenMod Code Review](http://review.cyanogenmod.com/) Getting Started --------------- To get started with Android/CyanogenMod, you'll need to get familiar with [Git and Repo](http://source.android.com/download/using-repo). To initialize your local repository using the CyanogenMod trees, use a command like this: repo init -u git://github.com/CyanogenMod/android.git -b gingerbread Then to sync up: repo sync Please see the [CyanogenMod Wiki](http://wiki.cyanogenmod.com/) for building instructions. For more information on this Github Organization and how it is structured, please [read the wiki article](http://wiki.cyanogenmod.com/index.php/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 at [buildbot.teamdouche.net](http://buildbot.teamdouche.net/)