Onnowpurbo: New page: == Intro: Adding a new app to the build == So after completing a build, people have been asking how t...

2015-01-02T21:54:26Z

New page: <languages /> <translate> == Intro: Adding a new app to the build ==   So after completing a build, people have been asking how t...

New page

<languages />
<translate>
== Intro: Adding a new app to the build == 


So after [[Development#Learning_To_Build_CM|completing a build]], people have been asking how to add their own app(s) to the CyanogenMod .zip file.

=== The "easy" way-- Add it to the zip manually === 


One way to do this is to simply add the [[wikipedia:APK_(file_format)|.apk]] into the .zip and then edit the recovery installation script (written in a simple scripting language called "[[edify]]") to copy the file from the .zip to the device.

=== The "right" way: Make a part of the build repository so it auto-builds === 

==== Add app source to <code>/packages/apps</code> ==== 


You can do this manually, or you can do it via the <code>.repo/local_manifests/*.xml</code>. If you do it this way, a <code>repo sync</code> will update the source to your app from whatever git repository you name in the [[Doc:_Using_local_manifests|local manifest]]. It's pretty easy to use, and allows you to override/replace/add/remove any official CM repository with one or more of your own.

==== Determine the name of the project from <code>Android.mk</code> ==== 


Regardless of how you put the source in <code>packages/apps/</code>, assuming that the source for the app has an <code>Android.mk</code> [[wikipedia:Make_(software)|Makefile]], you can get it to automatically build and install the resulting file in your <code>$OUT</code> directory (and thus your <code>.zip</code>) by simply determining the name of the project, which is typically defined in <code>Android.mk</code> with this:


<code>LOCAL_PACKAGE_NAME := PackageName</code>

==== Add the project to <code>device.mk</code> (or whatever .mk) in the device folder ==== 


Then just add that project to be built in the <code>/device/[MANUFACTURER]/[CODENAME]/device.mk</code> file.


'''Example:'''


Let's look at the [[Grouper_Info|grouper]] device aka the [[Grouper_Info|Nexus 7]]. You want to find where the list of packages to build is for this device, in <code>device/asus/grouper/device-common.mk</code>.


{{note|note=For the nexus 7, the <code>device-common.mk</code> file is shared with the tilapia device (the Nexus 7 GSM version), so if you're building for another device that doesn't have <code>device-common.mk</code>, you'd probably make the edit to <code>device.mk</code> instead.}}


Now you have a choice. If <code>PRODUCT_PACKAGES</code> was previously defined, you can add a value like this:


<code>PRODUCT_PACKAGES += MyPackageName</code>


The <code>+=</code> part means to append it to the list.


Or, if it's simpler, you can just add it to the end an existing <code>PRODUCT_PACKAGES</code> list of projects by appending a "<code>\</code>" to the last item and then adding <code>MyPackageName</code> at the end. Notice that you can't put any commented lines (ie, lines starting with <code>#</code>) or even blank lines in the list of items to be built.


So if the list looks like this...


<code>PRODUCT_PACKAGES := \
lights.grouper \
audio.primary.grouper</code>


...you'd add it to the end:


<code>PRODUCT_PACKAGES := \
lights.grouper \
audio.primary.grouper \
MyPackage</code>


If the source for your app does not have the <code>Android.mk</code> makefile stuff, you'll need to add it. You can use any of the existing packages in <code>packages/apps</code> as a model for what needs to be done to build your particular app.


See [http://www.kandroid.org/ndk/docs/ANDROID-MK.html here for official documentation] on Android .mk files.
</translate>

==Referensi==

* http://wiki.cyanogenmod.org/w/Doc:_adding_your_own_app

ROM Android: Menambahkan builtin aplikasi - Revision history

Onnowpurbo: New page: == Intro: Adding a new app to the build == So after completing a build, people have been asking how t...