### Berkeley DB Reference Guide: Building Berkeley DB for VxWorks systems |

### VxWorks notes

Berkeley DB currently disallows the DB_TRUNC flag to DB->open. The operations that this flag represents are not fully supported under VxWorks.

The DB->sync function is implemented using an ioctl call into the file system driver with the FIOSYNC command. Most, but not all file system drivers support this call. Berkeley DB requires the use of a file system supporting FIOSYNC.

### Building and Running the Demo Program

The demo program should be built in a manner very similar to building Berkeley DB. If you want different or additional BSP build specifications you should add them by following the directions indicated in Building with Tornado 2.0 or Tornado 2.2.

The demo program can be downloaded and run by calling the entry function dbdemo with the pathname of a database to use. The demo program will ask for some input keys. It creates a database and adds those keys into the database, using the reverse of the key as the data value. When complete you can either enter EOF (control-D) or quit and the demo program will display all of the key/data items in the database.

### Building and Running the Utility Programs

The Berkeley DB utility programs can be downloaded and run by calling the function equivalent to the utility's name. The utility functions take a string containing all the supported arguments. The program will then decompose that string into a traditional argc/argv used internally. For example, to execute db_stat on a database within an environment you would execute the following from the windsh prompt. Obviously you would change the pathname and database name to reflect your system.

>     -> db_stat "-h /tmp/myenvhome -d mydatabase.db"

### Notes for VxWorks 5.4/5.5

The memory on VxWorks is always resident and fully shared among all tasks running on the target. For this reason, the DB_SYSTEM_MEM flag is implied for any application that does not specify the DB_PRIVATE flag. Additionally, applications must use a segment ID to ensure that different applications do not overwrite each other's database environments. See the DB_ENV->set_shm_key method for more information. Also, the DB_LOCKDOWN flag has no effect.

A default small footprint build is provided. This default provides equivalent to the --enable-smallbuild configuration option described in Building a small memory footprint library. In order to build the small footprint, you should move db_config.h aside and copy db_config_small.h to db_config.h. Then open up the appropriate small workspace file via Tornado and build as usual.

Copyright (c) 1996,2007 Oracle. All rights reserved.