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

Differing Properties for Compilers and Tools
NSDEE 2.1 provided graphical equivalents for setting almost every command line option for cross
compilers, linkers, and other tools. NSDEE 3.0 takes a different approach by providing graphical
equivalents only for a few common tool options. All other tool options can be added simply by
typing them in as they would appear on a command line.
The NSDEE 3.0 approach simplifies the property pages and allows you to more easily see all
command line settings for a tool. No need to peruse numerous property pages to hunt down an
option seen in tool documentation. You can simply add the option directly to the list of options you
want passed to the tool at build time.
Includes Folder Added to Local Projects
NSDEE 3.0 adds an Includes folder to all local projects. The Includes folder contains a link
to the system include directory for cross compilers and tools as well as links to include locations
you specify for you builds.
Makefile Changes
NSDEE 2.1 used a single, monolithic makefile. This makefile was regenerated for every build and
contained build targets for each and every source file in a project. Additionally, dependencies
were declared for every system header referenced by each source file in the project.
NSDEE 3.0 uses simpler and more efficient makefiles. NSDEE creates one top-level makefile (named
makefile
) and two top-level include makefiles (objects.mk and sources.mk). The top-level
makefile provides the "all", "clean", and "deploy" build targets.
NSDEE also creates one makefile per source directory named subdir.mk which provides build
targets for source files in the containing directory. Because NSDEE 3.0 uses one makefile per
source directory, it only needs to regenerate makefiles for directories that contain changed source
files.
Additionally, NSDEE now uses build macros in many instances so only one build rule can be used
for many source files, simplifying per-directory makefiles. Furthermore, NSDEE no longer specifies
system headers as dependencies, which greatly lessens the number of file change checks occurring
at build time. (System headers rarely change, so it is inefficient to list them all as dependencies. If
system headers really do change, then it's a good idea to do a complete rebuild.)
Different Project Creation Wizards
NSDEE 2.1 provided three wizards for creating local projects--Standard Make Project, Managed
Make Project, and Remote Standard Make Project wizards. NSDEE 3.0, on the other hand, provides
separate project creation wizards for C, C++, COBOL, and pTAL managed and unmanaged
(makefile) projects for local Windows-hosted builds. Choose the project type based on which
language contains the main entry point (for executables) or which language you will use primarily
(for libraries).
The Remote Standard Make project wizard is the same at NSDEE 3.0, but the name of the wizard
has been changed to Remote Makefile Project to better fit the newer CDT nomenclature.
Changes to NonStop Tools
Like NSDEE 2.1, NSDEE 3.0 provides a NonStop Tools menu, but the contents have changed.
The menu items Create/Modify Archive..., Create/Modify Remote DEFINE File..., and Create/Modify
DEFINE File... have been deprecated and are not available in the NonStop Development perspective.
Additionally, the Configure Compilers... menu item and the Configure Compilers dialog have been
replaced by a Configure Tool Locations... menu item and Tool Locations preferences, respectively.
Tool Locations preferences provide additional capabilities to those provided by the Configure
Compilers dialog.
150 What's New at NSDEE 3.0?