HP Integrity NonStop J-Series - Manual (Page 49)

HOST_PASS — used if none of the above are set. HOST_PASS is the environment variable you
set if all tools use the same host and user settings (for simplicity).
If you fail to set one of the above environment variables when invoking make outside of NSDEE,
the command using nsdee-auth as an argument to, -Wsqluser (for example) fails and the
output includes a message such as the following from nsdee-auth:
C:\e3.7\eclipse\plugins\com.hp.nsdee_1.0.0\Tools\nsdee-auth.exe \
ERROR: Neither SQLMX_PASS nor HOST_PASS are set.
DependencyHandling
The DependencyHandling build variable allows you to modify how NSDEE generates header
file dependencies for source files in managed builds. You can set it to:
•
none to turn off generation of dependencies
•
makeonly to limit generation of dependencies to those that can be generated without using
NSDEE (as when invoking make outside of NSDEE)
•
full to generate a full list of dependencies (but not system header dependencies)
System header dependencies are not generated by default. NSDEE generates them if you specify
makeonly+systemHeaders
or full+systemHeaders. For details on how NSDEE generates
dependencies, see “Handling dependencies in managed builds” (page 52) .
TARGET_SYSTYPE
TARGET_SYSTYPE is a build variable set by NSDEE based on your choice of OSS or Guardian
radio buttons at project creation time. ${TARGET_SYSTYPE} is the default argument for all tool
options that take oss or guardian as an argument (-Wsystype= for compiler and linker tools,
-q
for Deploy.jar).
This is useful when changing the target platform for a build configuration. You need only change
the variable value and not each and every instance of -Wsystype= and -q options across tools.
NSDEE_DEPLOY_SYSTEM, NSDEE_DEPLOY_USER, NSDEE_DEPLOY_DEST,
NSDEE_DEPLOY_FILENAME
NSDEE defines the above four environment variables for local projects to create custom deploy
targets. (For an example of this, see
“Creating custom deploy targets ” (page 118) ). These variables
are set to the remote settings that you specify at project creation time or via the Settings (Remote)
property page.
The values set depend on whether your project builds do SQL/MX or SQL/MP compilation.
Figure 6 (page 50) shows which fields NSDEE uses to set environment variables for projects that
perform SQL/MP compilation, SQL/MX compilation, and projects that do not perform SQL
compilation.
Environment variables and build variables 49