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

•
Rename refactoring — Renames classes, types, methods, functions, and member names,
applying the name change to all files in a project or across an entire workspace.
•
Per-project preferences for C/C++ preferences such as code formatting.
All of the above features are described in the C/C++ Development User Guide.
New Features for Local Projects
New features for local projects with Windows-hosted builds include support for:
•
Multiple build targets for different architectures and platforms for a single project.
•
More flexible and better performing builds via multiple smaller and more concise makefiles.
•
Extending managed builds through the use of makefile includes. This allows you to create
custom makefile targets and modify build behavior while still having NSDEE manage builds
and create makefiles for you.
•
Creating a project with an existing source base outside of your workspace.
•
Initiating builds, deploying, and changing build configurations using tool bar icons in the
NonStop Development perspective.
•
Transferring project files from Windows to NonStop systems using a new, more flexible file
transfer wizard.
•
Adding Cygwin or Msys bin directory to your PATH at project build time. (No need to add
bin
to your Windows PATH unless you prefer to.)
•
Importing ETK and NSDEE 2.1 projects as NSDEE 3.0 projects.
•
Automatic detection of cross-compiler locations. No need to configure compiler locations
unless the compiler locations are non-standard.
•
Build output logging.
•
Accessing multiple build configurations in project property pages. No need to change build
configurations in order to edit their properties as was the case at NSDEE 2.1.
•
Most build property changes can be applied across multiple build configurations if desired.
Differences Between NSDEE 2.1 and NSDEE 3.0
In addition to the many new features available at NSDEE 3.0, there are other changes you may
be interested in if you've been using NSDEE 2.1 standard or managed make projects. There are
also changes to project creation wizards and to the NonStop Tools menu. These changes are
described in the following sections.
Standard Make and Managed Make Replaced
CDT documentation has not used the terms standard make and managed make since CDT 3.0.
NSDEE 2.1 was based on the CDT 3.0 build system and also used those terms.
NSDEE 3.0 extends CDT 8.0. CDT now uses the term managed build to indicate a property of a
project that specifies whether or not CDT should create makefiles and manage builds for you, or
if you will manage builds and makefiles without CDT or NSDEE being involved. You can toggle
this managed build attribute of a project on or off, giving you more flexibility in how to develop
your application.
For example, you now have the option of creating an NSDEE project with managed builds turned
on so that NSDEE creates makefiles and manages builds for you. Once your project is set up,
though, you can turn this attribute off and, in effect, take over management of the makefiles created
for you by NSDEE. You can even toggle this attribute back on later, but it will result in NSDEE
overwriting any changes you made to makefiles.
Differences Between NSDEE 2.1 and NSDEE 3.0 149