5.7 Building and Compiling
To build the generated classes, use the generated makefile.
To build the implemented application files discussed in this chapter, copy the provided files soap_main.cpp and trade_main.cpp into the soapExample\app\data before compiling, allowing them to overwrite the generated files of the same name. After compiling, copy the soap.xml and trade.xmlinto the soapExample\bin directory.
On UNIX, you must set your RWSF_HOME environment variable before using the makefiles. On Windows, be sure you have run the script rwsfvars.bat, and set up your command window with the MSVC environment.
From the top-level code generation directory, invoke the following command:
Windows nmake UNIX make This builds the shared library for all of your generated classes.
To build the libraries and the sample applications together, issue the make command and specify the sample soap and trade application targets:
Windows nmake soap_main.exe trade_main.exe UNIX make soap_main trade_main
The makefile builds any components created when the generator created the makefile, placing them into top-level bin and lib directories as follows:
| Windows | /bin | executables, DLLs |
| /lib | Import libraries (.lib) | |
| UNIX | /bin | executables |
| /lib | Shared libs (ext varies with OS) |
To run the example, first make sure that your environment is set up as described in Chapter 2, "Setup," in the HydraExpress User Guide. Change to the directory soapExample\app\data and run the soap_main or trade_main application at the command prompt, as shown here:
prompt> soap_main prompt> trade_main |
Copyright © Rogue Wave Software, Inc. All Rights Reserved.
The Rogue Wave name and logo are registered trademarks of Rogue Wave Software, and HydraExpress is a trademark of Rogue Wave Software. All other trademarks are the property of their respective owners.
Contact Rogue Wave about documentation or support issues.