ADHOC/replicant-vendor_replicant
3
0
Fork 0
Code Issues 6 Pull Requests Releases Activity
1,122 Commits 2 Branches 0 Tags 430 MiB
CSS 35.3%
JavaScript 25.2%
Shell 21.2%
C# 8.4%
Makefile 7.8%
Other 2%
11d5cdb86f
Go to file
Diogo Ferreira 11d5cdb86f vendor: Externalize common version and release names 
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
2011-10-14 15:32:49 +01:00
overlay Add Motorola Atrix 2011-10-13 05:04:10 +00:00
prebuilt Update modelid_cfg.sh to copy correct firmware for ace nam 2011-10-07 08:57:46 -04:00
products vendor: Externalize common version and release names 2011-10-14 15:32:49 +01:00
tools leo: update leoupdate 2011-09-28 01:05:04 +01:00
.gitignore
Android.mk Use only present proprietary files 2011-07-10 20:08:26 +02:00
CHANGELOG
CHANGELOG.mkdn Encore: update fingerprint and add 7.1 changelog 2011-10-09 13:56:04 -07:00
extract-gapps-files Add a script to extract gapps files from downloaded zip file. 2010-10-29 23:49:13 +08:00
extract-google-files
get-rommanager update get-rommanager url 2011-06-05 00:49:56 -07:00
LICENSE Add LICENSE file 2011-01-30 21:10:08 -05:00
prelink-linux-arm-hero.map HERO: updated prelink map 2011-01-24 10:56:26 +11:00
prelink-linux-arm-msm722x.map cm: Clean up prelink maps 2011-01-18 00:54:37 -05:00
README.mkdn cm: Update README 2011-01-16 03:57:45 -06:00
vendorsetup.sh Add Motorola Atrix 2011-10-13 05:04:10 +00:00

README.mkdn

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

Getting Started

To get started with Android/CyanogenMod, you'll need to get familiar with Git and 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 for building instructions.

For more information on this Github Organization and how it is structured, please read the wiki article

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