diff options
Diffstat (limited to 'en/setup/develop/new-device.html')
| -rw-r--r-- | en/setup/develop/new-device.html | 30 |
1 files changed, 15 insertions, 15 deletions
diff --git a/en/setup/develop/new-device.html b/en/setup/develop/new-device.html index bd869f97..6f7b3e72 100644 --- a/en/setup/develop/new-device.html +++ b/en/setup/develop/new-device.html @@ -23,7 +23,7 @@ -<p>Use the information in this page to create the Makefiles for your device and +<p>Use the information in this page to create the makefiles for your device and product. Please note, unlike the other pages in this section, the contents here are applicable only when creating an entirely new device type and are intended for company build and product teams only.</p> @@ -51,7 +51,7 @@ simplifying maintenance.</p> product such as the modules to build, locales supported, and the configuration for various locales. In other words, this is the name of the overall product. Product-specific variables are defined in - product definition Makefiles. A product can inherit from other + product definition makefiles. A product can inherit from other product definitions, which simplifies maintenance. A common method is to create a base product that contains features that apply for all products, then creating product variants based on that base @@ -187,30 +187,30 @@ organize your source files and build the way you see fit. <p> Nexus 6 was implemented with a main device configuration named <code>shamu</code>. From this device configuration, a product is created with a -product definition Makefile that declares product-specific information about +product definition makefile that declares product-specific information about the device such as the name and model. You can view the <code>device/moto/shamu</code> directory to see how all of this is setup. </p> <h3 id="makefiles">Write the Makefiles</h3> <p> - The following steps describe how to set up product Makefiles in a way similar + The following steps describe how to set up product makefiles in a way similar to that of the Nexus 6 product line: </p> <ol> <li>Create a <code>device/<company_name>/<device_name></code> directory for your product. For example, <code>device/moto/shamu</code>. This directory will contain source code - for your device along with the Makefiles to build them. + for your device along with the makefiles to build them. </li> - <li>Create a <code>device.mk</code> Makefile that declares the files and modules needed for the + <li>Create a <code>device.mk</code> makefile that declares the files and modules needed for the device. For an example, see <code>device/moto/shamu/device.mk</code>. </li> - <li>Create a product definition Makefile to create a specific product based on the device. The - following Makefile is taken from <code>device/moto/shamu/aosp_shamu.mk</code> as an example. + <li>Create a product definition makefile to create a specific product based on the device. The + following makefile is taken from <code>device/moto/shamu/aosp_shamu.mk</code> as an example. Notice the product is inheriting from the <code>device/moto/shamu/device.mk</code> and - <code>vendor/moto/shamu/device-vendor.mk</code> files via the Makefile while + <code>vendor/moto/shamu/device-vendor.mk</code> files via the makefile while also declaring the product-specific information such as name, brand, and model. <pre class="devsite-click-to-copy"> @@ -235,12 +235,12 @@ PRODUCT_PACKAGES += \ <p> See <a href="#prod-def">Product Definition Variables</a> for additional product-specific - variables you can add to your Makefiles. + variables you can add to your makefiles. </p> </li> - <li>Create an <code>AndroidProducts.mk</code> file that points to the product's Makefiles. In - this example, only the product definition Makefile is needed. The example below is from + <li>Create an <code>AndroidProducts.mk</code> file that points to the product's makefiles. In + this example, only the product definition makefile is needed. The example below is from <code>device/moto/shamu/AndroidProducts.mk</code>: <pre class="devsite-click-to-copy"> # @@ -259,7 +259,7 @@ PRODUCT_MAKEFILES := \ </pre> </li> - <li>Create a <code>BoardConfig.mk</code> Makefile that contains board-specific configurations. + <li>Create a <code>BoardConfig.mk</code> makefile that contains board-specific configurations. For an example, see <code>device/moto/shamu/BoardConfig.mk</code>. </li> @@ -276,7 +276,7 @@ add_lunch_combo <var><PRODUCT_NAME></var>-userdebug </ol> <h3 id="prod-def">Set Product Definition Variables</h3> <p> - Product-specific variables are defined in the product's Makefile. Variables maintained in a + Product-specific variables are defined in the product's makefile. Variables maintained in a product definition files include: </p> <table> @@ -328,7 +328,7 @@ add_lunch_combo <var><PRODUCT_NAME></var>-userdebug <td> List of words like <code>source_path:destination_path</code>. The file at the source path should be copied to the destination path when building this product. The rules for the copy - steps are defined in config/Makefile + steps are defined in config/makefile </td> <td></td> </tr> |