怎样在workbench 下运行eXtremeDB的测试例子


第一个跑现成的例子,第二个建立新的工程。


VXWorksworkbench sample project creation and compiling

1.Quick setup the samples

In windriverworkbench, choose file\switch workspace\ then choose the target directory in the eXtremeDB samples as the workspacedirectory.

2.New project creation

1.1.Unpack the package

Unzip the package to a special directory. For example, extremedb_4.5_fusion_vxworks.6.8_dkm_PPC32e500v2gnu_sql_log_eval.ziptoc:\McObject\vxworks\extremedb_4.5_fusion_vxworks.6.8_dkm_PPC32e500v2gnu_sql_log_eval\

1.2.Creatingthe Project for the VxWorks Simulator

1.

Select File > New > Wind River Workbench Project. The Wind River Workbench New Project wizard appears.


2.

For the Target operating system, select WorkbenchVxWorks 6.x, and then click Next.


3.

For the Build type, select Downloadable Kernel Module, and then click Next.


4.

In the Project name field, type the project name:for example : here, Perf08.


5.

Keep Create project in workspace selected.



The default active build spec is for the VxWorks simulator, so you do not have to adjust any other settings.


6.

Click Finish.


1.3.ImportingSource Files Into Your Project

1.

Right-click the project folder, then select Import. The Import wizard appears.


2.

Double-click General, then select File system, then click Next. The File system page of the Import wizard appears.


3.

Click the Browse button next to the From directory field. The Import from directory page appears.


4.

Navigate to the directory the default is in C:\,like: c:\McObject\vxworks\extremedb_4.5_fusion_vxworks.6.8_dkm_PPC32e500v2gnu_sql_log_eval\samples\core\08-benchmarks-perf\ directory, file selected including .mco, .c, .h and *.makefile. ,then click OK

5,Include the common.h and common.c into current project in c:\McObject\vxworks\extremedb_4.5_fusion_vxworks.6.8_dkm_PPC32e500v2gnu_sql_log_eval\samples\core\common\ into the project.

1.4.Configthe project

1)Build support and specs for simulator:

spacer.gif

2)Add the include path in to the build path like:

-IC:/McObject/vxworks/extremedb_4.5_fusion_vxworks.6.8_dkm_PPC32e500v2gnu_sql_log_eval/include

-IC:/McObject/vxworks/extremedb_4.5_fusion_vxworks.6.8_dkm_PPC32e500v2gnu_sql_log_eval/samples/core/common

spacer.gif

3)There is some build Macro addition for items LIBS,like this for 08-perf:-lmcolib-lmcovtdsk -lmcosvxn -lmcomconv -lmcofvx -lmcotmursiw -lmcouwrt

spacer.gif

4)Libraries should add new lib path like : -LC:/McObject/vxworks/extremedb_4.5_fusion_vxworks.6.8_dkm_PPC32e500v2gnu_sql_log_eval/target/bin/SIMNTgnu

spacer.gif

1.5.Buildthe project

To build the perf08 project, dothe following:

1.

In the Project Explorer right-click the perf08 folder and select Build Project.


2.

Click Continue if asked if you want Workbench to generate include paths.

1.6.Toconnect to the target, do the following:

1. In the Remote Systems view, right-clickvxsim0 (Wind River VxWorks 6.x).

2. Choose Connect `vxsim0'.


A VxWorkssimulator shell opens inside the Target Console view that appears in thelower-right corner of the Workbench window, in the tabbed notebook. Theconnection details appear in the Remote Systems view.


NOTE: The Target Console is onlyavailable for VxWorks 6.8. Older versions of VxWorks will open an externalwindow to display the console. You can minimize the shell, but do not close it.

(Optional) To view the propertiesof kernel tasks or real time processes (RTPs), in the Remote Systems view,expand the target connection node to see the contents of the Kernel Tasks andReal Time Processes folders. Right-click a task or process, and select Show inProperties.

The Properties view appears, showing a list ofassociated properties and values.

1.7.Tostart the perf08 application using VxWorks, do the following:

1.

Expand the perf08 folder and select Build Targets.


2.

Right-click perf08.out in the Project Explorer and select Debug VxWorks Kernel Task.



The Debug Configurations dialog appears, with perf08.out already filled in as part of the name of the launch.


3.

Type main in the Entry Point field.


4.

Click Debug.


Workbench automatically builds the perf08 project and switches to the Device Debug perspective, with main.c open in the Editor. The Debug view shows the program stopped at main( ). The Breakpoint view appears with no breakpoints listed. The Variables view shows the values of the variables that have been defined to this point.

1.8.SettingUp the Device Debug Perspective

The action of the perf08 program is displayed by viewing the memory address of the grid global variable in the Memory Browser.


NOTE: You can also use the Memory view for this example; see Wind River Workbench User's Guide: Building and Debugging a Sample Project for those instructions.

To view the action of theperf08 program, do the following:

1.

If the Memory Browser is not already open, select Window > Show View > Other > Debug > Memory Browser, then click OK.



The Memory Browser appears in the lower-right corner of the Workbench window, in the tabbed notebook with the Variables and Expressions views.


2.

Click the title bar of the Memory Browser and drag it to the left, over the tabbed notebook containing the Tasks view and the Build Console. Wait for an icon of a set of stacked folders to appear at the cursor, then drop the view.

http://127.0.0.1:11728/help/topic/com.windriver.ide.doc.wr_workbench_vxworks/wr_workbench_vxworks_6_tutorial_3.2/html/p_w_picpaths/memoryDrag2.gif


3.

If the Expressions view is not already open, select Window > Show View > Other > Debug > Expressions, then do the following:


a.

Select the Expressions tab and expand it enough to see the Expression, Type, and Value columns.




b.


In the Expression column, click Add new expression.



c.

Type grid and press ENTER.



The memory address of the grid global variable appears in the value column. It can vary from one session to another if, for example, you compile with the GNU compiler instead of the Wind River Compiler.


The right half of the Device Debug perspective now appears approximately as shown:



http://127.0.0.1:11728/help/topic/com.windriver.ide.doc.wr_workbench_vxworks/wr_workbench_vxworks_6_tutorial_3.2/html/p_w_picpaths/DeviceDebugPerspective-Memory2.gif