<!--$Id: intro.so,v 1.28 2008/05/05 05:22:43 alexg Exp $--> <!--Copyright (c) 1997,2008 Oracle. All rights reserved.--> <!--See the file LICENSE for redistribution information.--> <html> <head> <title>Berkeley DB Reference Guide: Building for VxWorks 5.4 and 5.5</title> <meta name="description" content="Berkeley DB: An embedded database programmatic toolkit."> <meta name="keywords" content="embedded,database,programmatic,toolkit,btree,hash,hashing,transaction,transactions,locking,logging,access method,access methods,Java,C,C++"> </head> <body bgcolor=white> <a name="2"><!--meow--></a> <table width="100%"><tr valign=top> <td><b><dl><dt>Berkeley DB Reference Guide:<dd>Building Berkeley DB for VxWorks systems</dl></b></td> <td align=right><a href="../build_wince/notes.html"><img src="../../images/prev.gif" alt="Prev"></a><a href="../toc.html"><img src="../../images/ref.gif" alt="Ref"></a><a href="../build_vxworks/intro6x.html"><img src="../../images/next.gif" alt="Next"></a> </td></tr></table> <p align=center><b>Building for VxWorks 5.4 and 5.5</b></p> <p>The build_vxworks directory in the Berkeley DB distribution contains a workspace and project files for Tornado 2.0/VxWorks 5.4 and Tornado 2.2/VxWorks 5.5.</p> <table border=1 align=center> <tr><th>File</th><th>Description</th></tr> <tr> <td align=left>BerkeleyDB20.wsp</td> <td align=left>Berkeley DB Workspace file for Tornado 2.0</td> </tr> <tr> <td align=left>BerkeleyDB20.wpj</td> <td align=left>Berkeley DB Project file for Tornado 2.0</td> </tr> <tr> <td align=left>BerkeleyDB22.wsp</td> <td align=left>Berkeley DB Workspace file for Tornado 2.2</td> </tr> <tr> <td align=left>BerkeleyDB22.wpj</td> <td align=left>Berkeley DB Project file for Tornado 2.2</td> </tr> <tr> <td align=left>dbdemo/dbdemo20.wpj</td> <td align=left><a href="../../ref/build_vxworks/notes.html">Demo program</a> project file for Tornado 2.0</td> </tr> <tr> <td align=left>dbdemo/dbdemo22.wpj</td> <td align=left><a href="../../ref/build_vxworks/notes.html">Demo program</a> project file for Tornado 2.2</td> </tr> <tr> <td align=left>db_*/*20.wpj</td> <td align=left><a href="../../ref/build_vxworks/notes.html">Support utilities</a> project files for Tornado 2.0</td> </tr> <tr> <td align=left>db_*/*22.wpj</td> <td align=left><a href="../../ref/build_vxworks/notes.html">Support utilities</a> project files for Tornado 2.2</td> </tr> </table> <b>Building With Tornado 2.0 or Tornado 2.2</b> <p>Open the workspace <b>BerkeleyDB20.wsp</b> or <b>BerkeleyDB22.wsp</b>. The list of projects in this workspace will be shown. These projects were created for the x86 BSP for VxWorks.</p> <p>The remainder of this document assumes that you already have a VxWorks target and a target server, both up and running. It also assumes that your VxWorks image is configured properly for your needs. It also assumes that you have an acceptable file system already available. See <a href="../../ref/build_vxworks/faq.html">VxWorks FAQ</a> for more information about file system requirements. See <a href="../../ref/build_vxworks/notes.html">VxWorks Notes</a> for more information about building a small footprint version of Berkeley DB.</p> <p>First, you need to set the include directories. To do this, go to the <i>Builds</i> tab for the workspace. Open up <i>Berkeley DB Builds</i>. You will see several different builds, containing different configurations. All of the projects in the Berkeley DB workspace are created to be downloadable applications.</p> <table border=1 align=center> <tr><th>Build</th><th>Description</th></tr> <tr> <td align=left>PENTIUM_debug</td> <td align=left>x86 BSP with debugging</td> </tr> <tr> <td align=left>PENTIUM_release</td> <td align=left>x86 BSP no debugging</td> </tr> </table> <p>You have to add a new build specification if you use a different BSP, want to add a build for the simulator or want to customize further. For instance, if you have the Power PC (PPC) BSP, you need to add a new build for the PPC tool chain. To do so, select the "Builds" tab, select the Berkeley DB project name, and right-click. Choose the <i>New Build...</i> selection and create the new build target. For your new build target, you need to decide whether it should be built for debugging. See the properties of the Pentium builds for ways to configure for each case. After you add this build you, you still need to configure correctly the include directories, as described in the sections that follow.</p> <p>If you are running with a different BSP, you should remove the build specifications that do not apply to your hardware. We recommend that you do this after you configure any new build specifications first. The Tornado tools will get confused if you have a PENTIUMgnu build specification for a PPC BSP, for instance.</p> <p>Select the build you are interested in, and right-click. Choose the <i>Properties...</i> selection. At this point, a tabbed dialog should appear. In this new window, choose the <i>C/C++ compiler</i> tab. In the edit box, you need to modify the full pathname of the <i>build_vxworks</i> subdirectory of Berkeley DB, followed by the full pathname of Berkeley DB. Then, click OK. Note that some versions of Tornado (such as the version for Windows) do not correctly handle relative pathnames in the include paths.</p> <p>To build and download the Berkeley DB downloadable application for the first time requires several steps: </p> <ol> <p><li>Select the build you are interested in, and right-click. Choose the <i>Set... as Active Build</i> selection. <p><li>Select the build you are interested in, and right-click. Choose the <i>Dependencies...</i> selection. Run dependencies over all files in the Berkeley DB project. <p><li>Select the build you are interested in, and right-click. Choose the <i>Rebuild All (Berkeley DB.out)</i> selection. <p><li>Select the Berkeley DB project name, and right-click. Choose the <i>Download "Berkeley DB.out"</i> selection. </ol> <p>Note that the output file listed about will really be listed as <i>BerkeleyDB20.out</i> or <i>BerkeleyDB22.out</i> depending on which version of Tornado you are running. You need to repeat this procedure for all builds you are interested in building, as well as for all of the utility project builds you want to run.</p> <table width="100%"><tr><td><br></td><td align=right><a href="../build_wince/notes.html"><img src="../../images/prev.gif" alt="Prev"></a><a href="../toc.html"><img src="../../images/ref.gif" alt="Ref"></a><a href="../build_vxworks/intro6x.html"><img src="../../images/next.gif" alt="Next"></a> </td></tr></table> <p><font size=1>Copyright (c) 1996,2008 Oracle. All rights reserved.</font> </body> </html>