diff --git a/pdk/docs/guide/audio.jd b/pdk/docs/guide/audio.jd index 0467d897e..14e80bb45 100755 --- a/pdk/docs/guide/audio.jd +++ b/pdk/docs/guide/audio.jd @@ -23,7 +23,7 @@ Solid elements represent Android blocks and dashed elements represent partner-sp

Building an Audio Library

-

To implement an audio driver, create a shared library that implements the interface defined in AudioHardwareInterface.h. You must name your shared library libaudio.so so that it will get loaded from /system/lib at runtime. Place libaudio sources and Android.mk in partner/acme/chipset_or_board/libaudio/.

+

To implement an audio driver, create a shared library that implements the interface defined in AudioHardwareInterface.h. You must name your shared library libaudio.so so that it will get loaded from /system/lib at runtime. Place libaudio sources and Android.mk in vendor/acme/chipset_or_board/libaudio/.

The following stub Android.mk file ensures that libaudio compiles and links to the appropriate libraries:

diff --git a/pdk/docs/guide/camera.jd b/pdk/docs/guide/camera.jd
index f4c9c8503..083f43afd 100755
--- a/pdk/docs/guide/camera.jd
+++ b/pdk/docs/guide/camera.jd
@@ -21,7 +21,7 @@ pdk.version=1.0
 
 

Building a Camera Library

-

To implement a camera driver, create a shared library that implements the interface defined in CameraHardwareInterface.h. You must name your shared library libcamera.so so that it will get loaded from /system/lib at runtime. Place libcamera sources and Android.mk in partner/acme/chipset_or_board/libcamera/.

+

To implement a camera driver, create a shared library that implements the interface defined in CameraHardwareInterface.h. You must name your shared library libcamera.so so that it will get loaded from /system/lib at runtime. Place libcamera sources and Android.mk in vendor/acme/chipset_or_board/libcamera/.

The following stub Android.mk file ensures that libcamera compiles and links to the appropriate libraries:

 LOCAL_PATH := $(call my-dir)
diff --git a/pdk/docs/guide/gps.jd b/pdk/docs/guide/gps.jd
index 3af7d7d16..f2ce11c16 100755
--- a/pdk/docs/guide/gps.jd
+++ b/pdk/docs/guide/gps.jd
@@ -18,7 +18,7 @@ pdk.version=1.0
 
 

Building a GPS Library

-

To implement a GPS driver, create a shared library that implements the interface defined in gps.h. You must name your shared library libgps.so so that it will get loaded from /system/lib at runtime. Place GPS sources and Android.mk in partner/acme/chipset_or_board/gps/ (where "acme" is your product name and "chipset_or_board" is your hardware target).

+

To implement a GPS driver, create a shared library that implements the interface defined in gps.h. You must name your shared library libgps.so so that it will get loaded from /system/lib at runtime. Place GPS sources and Android.mk in vendor/acme/chipset_or_board/gps/ (where "acme" is your organization name and "chipset_or_board" is your hardware target).

The following stub Android.mk file ensures that libgps compiles and links to the appropriate libraries:

diff --git a/pdk/docs/guide/intro_source_code.jd b/pdk/docs/guide/intro_source_code.jd index 100f3ee5b..d391b0f57 100755 --- a/pdk/docs/guide/intro_source_code.jd +++ b/pdk/docs/guide/intro_source_code.jd @@ -163,7 +163,7 @@ Tools for building and debugging Android (of particular interest for porting are

You can develop Android applications with the same standard tools you use to develop any Java application. The Android core libraries provide the functionality needed to build rich mobile applications and the Android development tools are designed to simplify running, debugging, and testing your applications.

-

Add project-specific source code to the Android source tree under the partner directory in a directory specific to the application or service you are building. For example, all Google-specific applications would be placed under device/partner/google/. A Google search application would be placed under device/partner/google/apps/Search. +

Add project-specific source code to the Android source tree under the partner directory in a directory specific to the application or service you are building. For example, all Google-specific applications would be placed under vendor/google/. A Google search application would be placed under vendor/google/apps/Search.

See Building Android for a new Mobile Device for detailed instructions.