diff --git a/pdk/docs/guide/build_new_device.jd b/pdk/docs/guide/build_new_device.jd index 21105d991..e320ff3f1 100755 --- a/pdk/docs/guide/build_new_device.jd +++ b/pdk/docs/guide/build_new_device.jd @@ -13,15 +13,15 @@ pdk.version=1.0

The directions below describe how to configure make files for new mobile devices and products.

    -
  1. Create a company directory in //device/partner.
    +
  2. Create a company directory in //vendor/.
    -  mkdir device/partner/<company_name>
  3. + mkdir vendor/<company_name>
  4. Create a products directory beneath the company directory you created in step 1.
    -  mkdir device/partner/<company_name>/products/
  5. -
  6. Create a product-specific make file, called device/partner/<company_name>/products/<first_product_name>.mk, that includes the following code:
    + mkdir vendor/<company_name>/products/
  7. +
  8. Create a product-specific make file, called vendor/<company_name>/products/<first_product_name>.mk, that includes the following code:
    -  $(call inherit-product, target/product/generic.mk)
    +  $(call inherit-product, $(SRC_TARGET_DIR)/product/generic.mk)
       #
       # Overrides
       PRODUCT_NAME := <first_product_name>
    @@ -43,8 +43,8 @@ pdk.version=1.0
         $(LOCAL_DIR)/first_product_name.mk \
  9. Create a board-specific directory beneath your company directory that matches the PRODUCT_DEVICE variable <board_name> referenced in the product-specific make file above. This will include a make file that gets accessed by any product using this board.
    -  mkdir device/partner/<company_name>/<board_name>
  10. -
  11. Create a product_config.mk file in the directory created in the previous step (device/partner/<company_name>/<board_name>). If this directory does not include a product_config.mk file, the build will fail.
    + mkdir vendor/<company_name>/<board_name>
  12. +
  13. Create a product_config.mk file in the directory created in the previous step (vendor/<company_name>/<board_name>). If this directory does not include a product_config.mk file, the build will fail.
       # These definitions override the defaults in config/config.make for <board_name>
       #
    @@ -52,7 +52,7 @@ pdk.version=1.0
       # TARGET_HARDWARE_3D := false 
       #
       TARGET_USE_GENERIC_AUDIO := true
  14. -
  15. If you wish to modify system properties, create a system.prop file in your <board_name> directory(device/partner/<company_name>/<board_name>).
    +
  16. If you wish to modify system properties, create a system.prop file in your <board_name> directory(vendor/<company_name>/<board_name>).
       # system.prop for 
       # This overrides settings in the products/generic/system.prop file
    @@ -64,7 +64,7 @@ pdk.version=1.0
       PRODUCT_MAKEFILES := \
         $(LOCAL_DIR)/first_product_name.mk \
         $(LOCAL_DIR)/second_product_name.mk
  17. -
  18. device/partner/<company_name>/<board_name> must include an Android.mk file with at least the following code:

    +
  19. vendor/<company_name>/<board_name> must include an Android.mk file with at least the following code:

       # make file for new hardware  from 
       #
    @@ -82,15 +82,15 @@ pdk.version=1.0
       #
       # no boot loader, so we don't need any of that stuff..  
       #
    -  LOCAL_PATH := partner/<company_name>/<board_name>
    +  LOCAL_PATH := vendor/<company_name>/<board_name>
       #
       include $(CLEAR_VARS)
       #
       # include more board specific stuff here? Such as Audio parameters.      
       #
  20. -
  21. To create a second product for the same board, create a second product-specific make file called device/partner/company_name/products/<second_product_name>.mk that includes:
    +
  22. To create a second product for the same board, create a second product-specific make file called vendor/company_name/products/<second_product_name>.mk that includes:
    -  $(call inherit-product, partner/google/products/generic.mk)
    +  $(call inherit-product, $(SRC_TARGET_DIR)/product/generic.mk)
       #
       # Overrides
       PRODUCT_NAME := <second_product_name>
    @@ -98,12 +98,10 @@ pdk.version=1.0
     

By now, you should have two new products, called <first_product_name> and <second_product_name> associated with <company_name>. To verify that a product is properly configured (<first_product_name>, for example), execute the following:

-  cd device
-  . ./envsetup.sh
-  partner_setup <first_product_name>
+  . build/envsetup.sh
   make PRODUCT-<first_product_name>-user
 
-

You should find new build binaries located in device/out/target/product/<board_name>. +

You should find new build binaries located in /out/target/product/<board_name>.

New Product File Tree

@@ -127,4 +125,4 @@ pdk.version=1.0 -

\ No newline at end of file +