22.5 Procedure for Building with the Makefiles
This section describes how to build your application from the command line. If you are on Windows, you can also build the sample application using the generated workspace (MSVC 6) or solution (MSVC 7) file, as described in Section 22.7.
Make sure that you have set up your environment as described in Chapter 2, "Setup," in the Introduction to HydraExpress. On Windows, be sure you have set up your command window with the MSVC environment.
From the output, or code generation directory, simply run nmake (Windows) or make (Linux or UNIX) at the command prompt.
The project-level makefile builds any components created when the generator created the makefile. For example, invoking the generator with the -noserver option creates a makefile that does not build server components.
22.5.1 Building just a Client or Server
Top-level makefiles are generated with a target for the client or server, so you can easily build each separately if you wish. Just invoke the makefile as follows:
Win32 | nmake client //builds client only nmake server //builds server only |
UNIX/Linux | make client make server |
22.5.2 Location of Generated Libraries and Binary Files
The generated binary and library files are placed into top-level directories depending on your platform, as follows:
<project-directory>/ | |
lib/ | On Windows: all .lib files. On UNIX/Linux: all shared library .so files. |
bin/ | On Windows: all .exe and .dll files. On UNIX/Linux: all executable files. |
For each sub-directory, object files are placed into a special obj directory. For example:
project-directory/
app/
client/
obj/
server/
obj/
...
© Copyright Rogue Wave Software, Inc. All Rights Reserved. All Rights Reserved. Rogue Wave is a registered trademark of Rogue Wave Software, Inc. in the United States and other countries. HydraExpress is a trademark of Rogue Wave Software, Inc. All other trademarks are the property of their respective owners.
Contact Rogue Wave about documentation or support issues.