m4_comment([$Id: intro.so,v 1.7 2007/07/10 16:54:16 bostic Exp $])m4_ref_title(Building m4_db for BREW,    Building for BREW, @building for BREW, debug/printlog, build_s60/intro)m4_p([dnlThis page has general instructions for building the m4_db libraryand applets for the BREW platform.])m4_section([Building m4_db for the BREW simulator])m4_p([dnlThe m4_path(build_brew) directory in the m4_db distribution containsproject files for Microsoft Visual C++:])m4_table_begin(, _center)m4_table_header(Project File, Description)m4_table_element(_left, bdb_brew.dsw, Visual C++ 6.0 workspace)m4_table_element(_left, bdb_brew.dsp, Visual C++ 6.0 project)m4_table_endm4_p([dnlThe project file can be used to build the m4_db library for the BREWplatform. Both BREW SDK versions 2 and 3 are supported.  By default, thebuild is for BREW SDK version 2.])m4_p([dnlThe steps for building the m4_db library for the BREW Simulator are asfollows:])m4_nlistbeginm4_nlist([dnlInstall the BREW SDK and BREW SDK Tools.])m4_nlist([dnlTo build for BREW SDK version 3, edit the m4_db source distribution filem4_path(build_brew/db_config.h) file and m4_bold(remove) the line"#define HAVE_BREW_SDK2".  No changes are required to build for BREW SDKversion 2.])m4_nlist([dnlSelect m4_italic(File -__GT__ Open Workspace).  Look in the build_brewdirectory for Workspaces, select m4_italic(bdb_brew.dsw), and selectm4_italic(Open).])m4_nlist([dnlThe BREW SDK creates an environment entry "BREWDIR" after the SDKinstallation. Confirm the entry exists, and if not, create anenvironment entry which points to the BREW SDK's root directory.])m4_nlist([dnlFor the BREW platform, only the project "bdb_brew" is available.  Setthe bdb_brew project as the active project and select the appropriateoption for the build_all project (Debug or Release). Then selectm4_italic(OK).])m4_nlist([dnlTo build, press F7.])m4_nlistendm4_p([dnlThe build results are placed in a subdirectory of build_brew named afterthe selected configuration (for example, m4_path(build_brew\Release) orm4_path(build_brew\Debug)).])m4_p([dnlWhen building the application during development, you should normallyuse compile options "Debug Multithreaded DLL" and link againstm4_path([build_brew\Debug\bdb_brew.lib]). You can also build using arelease version of the m4_db libraries and tools, which will be placedin m4_path([build_brew\Release\bdb_brew.lib]). When linking against therelease build, you should compile your code with the "ReleaseMultithreaded DLL" compile option. You will also need to add them4_path(build_brew) directory to the list of include directories of yourapplication's project, or copy the m4_db include files to anotherlocation.])m4_section([Building a BREW applet with m4_db library])m4_p([dnlBuilding a m4_db application in the BREW environment is similar tobuilding in a Windows environment.  Ensure that m4_path(db.h) is in thebuild include path and m4_path(bdb_brew.lib) is in the build librarypath (alternatively, you can add project dependencies to them4_path(bdb_brew) project).])m4_p([dnlBREW applets require a few minor additions:])m4_nlistbeginm4_nlist([dnlThe m4_bold(BDBApp) structure must be extended -- the extendeddefinition of BDBApp is found in the include file m4_path(db.h).])m4_nlist([dnlBefore any m4_db operations are performed, the applet must call the "intbrew_bdb_begin(void)" function.  This function returns 0 on success, andnon-zero on failure.])m4_nlist([dnlAfter the last m4_db operation is performed, the applet must call the"void brew_bdb_end(void)" function.  Note that the brew_bdb_end functioncannot be called in the applet "cleanup" function.  If that is arequirement, use the following code instead:m4_indent([dnlBDBApp *pMe=(BDBApp *)po;if (pMe-__GT__db_global_values != NULL)	FREE(pMe-__GT__db_global_values);])])m4_nlistendm4_section([Building a BREW applet for the physical device])m4_p([dnlThe binaries linked with the m4_db library for the BREW simulator arenot target files that can run on the physical device.  In order to buildfor the physical device, an ARM compiler is needed: the recommended ARMcompiler is ARM Developer Suite 1.2.])m4_p([dnlThe steps for building a BREW applet for the physical device are asfollows:])m4_nlistbeginm4_nlist([dnlSet the target BREW Applet project as the active project.])m4_nlist([dnlSelect "Generate ARM Make file" in the BREW tool bar for VC6, and a makefile will be generated (if this step does not work, confirm your ADS wascorrectly installed).])m4_nlist([dnlThe m4_db library must then be manually added to this make file.  See them4_path(build_brew\bdbread.mak) file in the m4_db distribution for anexample.])m4_nlist([dnlSelect m4_italic(Tools -__GT__ BREW Application 'Make') to build.])m4_nlistendm4_p([dnlThe target .mod file will be created in the build directory, and thisis the file which should be uploaded to the physical device.])m4_page_footer