Chapter 4. Building Berkeley DB for Android

Chapter 4. Building Berkeley DB for + Android

@@ -43,51 +45,63 @@

- Building the Drop-In Replacement for Android + Building the Drop-In Replacement + for Android

- Migrating from SQLite to Berkeley DB + Migrating from SQLite to + Berkeley DB

- Building the Android JDBC Driver + Building the Android JDBC + Driver

- Android Configuration Options + Android Configuration + Options + +

+ + Using the JDBC Driver in ADF Mobile for Android

- Berkeley DB provides support for the Android platform enabling you to - develop and deploy a wide range of mobile applications and services. - Android provides SQLite as the default database for developing - applications that need database support. Berkeley DB SQL API is fully - compatible with SQLite and can be used as a replacement. The - build_android directory in the Berkeley DB - distribution contains a makefile, Android.mk, for - building a drop-in replacement for SQLite. + Berkeley DB provides support for the Android platform + enabling you to develop and deploy a wide range of mobile + applications and services. Android provides SQLite as the + default database for developing applications that need + database support. Berkeley DB SQL API is fully compatible with + SQLite and can be used as a replacement. The + build_android directory in the Berkeley + DB distribution contains a makefile, + Android.mk, for building a drop-in + replacement for SQLite.

- Oracle offers two different solutions for building the - BDB SQL API for Android. The first creates a library - that can be used as a drop-in replacement for SQLite on - Android. The second creates a JDBC driver for Android. + Oracle offers two different solutions for building the BDB + SQL API for Android. The first creates a library that can be + used as a drop-in replacement for SQLite on Android. The + second creates a JDBC driver for Android.

Building the Drop-In Replacement for Android

Building the Drop-In Replacement + for Android

@@ -95,54 +109,68 @@

- Migrating from SQLite to Berkeley DB + Migrating from SQLite to + Berkeley DB

- This section describes how to build a library that can be used as a - drop-in replacement for SQLite on Android. +

+ This section describes how to build a library that can be + used as a drop-in replacement for SQLite on Android.

Note

+ A drop in replacement refers to replacing all instances + of SQLite in an Android OS build with Berkeley DB SQL. All + databases will be created in the Berkeley DB SQL format + including any created with the Java SQLite.* API. This + solution requires that users re-compile a custom Android + OS image (it is only relevant for platform/device + vendors). +

-
- Download and compile the Android source tree. +
+ Download and compile the Android source tree.
-
- The compiling process takes time but is a one time activity. - For information on downloading and compiling the Android source - code, see - http://source.android.com/source/download.html. +
+ The compiling process takes time but is a one time + activity. For information on downloading and compiling + the Android source code, see http://source.android.com/source/download.html.
- Copy the Berkeley DB code into the Android build tree. + Copy the Berkeley DB code into the Android build + tree.
```
$ cd <root>/external/sqlite/dist
 $ tar zxf ${DB_PATH} 
```
-
- where <root> is the root of the Android source tree and - ${DB_PATH} is the path where you saved the - db-xx.tar.gz version of the Berkeley DB - distribution. +
+ where <root> is the root of the Android + source tree and ${DB_PATH} is the path where you saved + the db-xx.tar.gz version of the + Berkeley DB distribution.
- Update the Android build file to identify Berkeley DB. + Update the Android build file to identify Berkeley + DB.
-
- Replace the Android.mk file with the one - from the Berkeley DB source tree by doing the - following: +
+ Replace the Android.mk file with + the one from the Berkeley DB source tree by doing the + following:
```
$ cd <root>/external/sqlite/dist
 $ mv Android.mk Android.mk.sqlite
 $ cp ${DB_INSTALL}/build_android/Android.mk ./ 
```
-
+
where ${DB_INSTALL} is the directory into which you installed the Berkeley DB library.
@@ -151,26 +179,27 @@ $ cp ${DB_INSTALL}/build_android/Android.mk ./
Tuning parameters.
-
- The configuration options for performance tuning can be - added/edited in the Android.mk file by - modifying LOCAL_CFLAGS located in the - build libsqlite replacement section. For - more information, see - Android Configuration Options. +
+ The configuration options for performance tuning + can be added/edited in the + Android.mk file by modifying + LOCAL_CFLAGS located in the + build libsqlite replacement + section. For more information, see Android Configuration + Options.
-
- It is also possible to change these settings using PRAGMA - commands or through the DB_CONFIG file. +
+ It is also possible to change these settings using + PRAGMA commands or through the DB_CONFIG file.
-
- Build the new Android image. +
+ Build the new Android image.
-
- To build the Android image with Berkeley DB SQL included, - do the following: +
+ To build the Android image with Berkeley DB SQL + included, do the following:
```
$ cd <root>
 $ . build/envsetup.sh
@@ -180,7 +209,7 @@ $ make snod
 
```
You can locate the new image in - <root>/out/target/product/generic. + <root>/out/target/product/generic.

@@ -189,23 +218,24 @@ $ make snod

Migrating from SQLite to Berkeley DB

Migrating from SQLite to + Berkeley DB

- This section describes how to enable automatic conversion of SQLite - format databases to Berkeley DB SQL when they are opened. To do - this, you must first make sure that the - -DBDBSQL_CONVERT_SQLITE option is added to - LOCAL_CFLAGS when you configure your Berkeley DB - database build. +

+ This section describes how to enable automatic conversion + of SQLite format databases to Berkeley DB SQL when they are + opened. To do this, you must first make sure that the + -DBDBSQL_CONVERT_SQLITE option is added + to LOCAL_CFLAGS when you configure your + Berkeley DB database build.

- Build a static SQLite shell for Android platform. + Build a static SQLite shell for Android platform.

Create a script, build_sqlite3_shell.sh, in the @@ -244,44 +274,45 @@ ${CC} -DANDROID -DOS_ANDROID --sysroot="${SYSROOT}" -mandroid \ -fPIC ${LDFLAGS} ${CFLAGS} \ sqlite3.c shell.c -o sqlite3orig -
- Ensure you adjust the variables as per your actual Android - environment. This script is suited for Android 2.2. +
+ Ensure you adjust the variables as per your actual + Android environment. This script is suited for Android + 2.2.
- Execute the build_sqlite3_shell.sh script and to get the - static sqlite3 shell utility - sqlite3orig. + Execute the build_sqlite3_shell.sh script and to + get the static sqlite3 shell utility - sqlite3orig.
-
- Change the system image file. +
+ Change the system image file.

- Use the xyaffs2 utiltiy to decompress - the system.img and get the directory - system. + Use the xyaffs2 utiltiy to + decompress the system.img and get + the directory system.
```
$ xyaffs2 ./system.img system
```
- Add static sqlite3 shell utility. + Add static sqlite3 shell utility.
```
$ cp <root>/external/sqlite/dist/sqlite3orig \
                       system/xbin/sqlite3orig
```
-
- Use the mkyaffs2image utility to rebuild - system.img from the changed directory - system. -
+
+ Use the mkyaffs2image utility to + rebuild system.img from the changed + directory system. +
```
$ mkyaffs2image -f $PWD/system system.img
```
Note
-
- To open the database in the SQLite - format use the sqlite3orig - command. +
+ To open the database in the + SQLite format use the + sqlite3orig command.

- +

Chapter 4. Building Berkeley DB for Android			Chapter 4. Building Berkeley DB for + Android
Prev	Home	Building the Android JDBC Driver	Building the Android JDBC + Driver