Mxsqlc and mxsqlco, Nsdee_sys_include_path, Mxsqlc and mxsqlco nsdee_sys_include_path – HP Integrity NonStop H-Series User Manual

Page 42: Project includes folder

Advertising
background image

on your Windows system, where RVU_ID is the ID of the RVU a particular set of tools was released
on. (For older installations, the location is C:\Program Files\Compaq ETK-NSE\

Here are two examples of actual COMP_ROOT locations:

C:\Program Files\HP NonStop\H06.24

(RVU H06.24 for TNS/E)

C:\Program Files\HP NonStop\G06.32

(RVU G06.32 for TNS/R)

NSDEE sets COMP_ROOT based on your choices using the following combo boxes when you create
a project:

The same combo boxes are available on the Tool Locations property page if you decide to change
cross compilers after project creation.

If you choose two tool chains for a project, COMP_ROOT will be defined differently for TNS/R and
TNS/E build configurations.

Managed builds always define COMP_ROOT. Having NSDEE define COMP_ROOT for unmanaged
builds is optional. Do not have NSDEE set COMP_ROOT if your makefile already does so.

MXSQLC and MXSQLCO

MXQLC

and MXSQLCO are set to the locations of the C and COBOL versions of the DLL for SQL/MX

preprocessing named mxsqlcnt.dll. These are set based on settings in the Tool Locations
property page.

NSDEE_SYS_INCLUDE_PATH

NSDEE uses the NSDEE_SYS_INCLUDE_PATH environment variable to define where the C/C++
indexer will look for system headers. NSDEE_SYS_INCLUDE_PATH is derived from the tools roots
used to set COMP_ROOT. For TNS/E, NSDEE_SYS_INCLUDE_PATH is set to
COMP_ROOT\user\include

, for TNS/R, it is set to COMP_ROOT\include.

The value of NSDEE_SYS_INCLUDE_PATH shows up under an Includes list which looks similar to
a top-level folder under a project as shown in

Example 1 “Project Includes folder”

.

Example 1 Project Includes folder

An important thing to note is that the indexer uses the NSDEE_SYS_INCLUDE_PATH associated
with the first build configuration set for a project. The indexer does not change where it looks for
system headers when you change the activate build configuration to one with a different tool chain
(even though the system headers will be different). The reason for this is that, depending on the
size of your project, it can be time consuming for the indexer to recreate its database every time
you change your active build configuration.

You can change where the indexer looks using the indexer property page for a project. At the
bottom of that page is the group box as shown previously in

Example 1 “Project Includes folder”

.

42

Concepts

Advertising
This manual is related to the following products: