HP Integrity NonStop H-Series - Manual (Page 47)

Figure 7 Setting the location of SQL/MX Preprocessor for COBOL
Managed build makefiles
When you initiate a build for a managed project, NSDEE generates makefiles before invoking
make
. Three of these makefiles are written to the top-level build directory. Typically there will be
two build configurations per architecture you build for. If, for example, your application is built
only for TNS/E, then the two top-level build directories will be named Debug and Release. These
directories will be created when you first build using a debug or release build configuration.
This table lists the three automatically-generated makefiles that are written to the top-level build
directory:
Purpose Makefile
This is the primary makefile for a build configuration. It contains the build rules for "all",
"clean", and "deploy". makefile
This contains definitions of USER_OBJS and LIBS, two build macros that are set to
out-of-project object files and libraries, respectively, that are passed to the linker for the
final link step. objects.mk
This defines a list of source macros, such as C_SRCS, and all of the subdirectories that
contribute source code to the build. sources.mk
NSDEE also creates a makefile for each source directory containing sources to be built. The source
directory names and hierarchy are mirrored under a Debug or Release folder (depending on the
build configuration). For each such mirrored directory, NSDEE creates a subdir.mk file which
contains the rules for building the sources in the containing directory. Mirrored directories also
contain the build output of source built from the original source directory.
Figure 8 (page 48) shows
the layout of a simple project with one source directory named src and one top-level build directory
named Debug.
Managed build makefiles 47