beautypg.com

Creating a local makefile project from scratch – HP Integrity NonStop J-Series User Manual

Page 30

background image

TIP:

The Console view separates build output for each project. Because the Car project built

last, its build output is shown in the Console view. If you select CarParts in the NonStop Project
Explorer view, the Console shows build output for CarParts.

TIP:

Building Car and CarParts produces more output than the default Console view can display.
By default, the Console view limits output shown to 500 lines. Increase this from the preference
page available from Window

→Preferences→C/C++→Build→Console.

For information on how to deploy and run Car.txe from NSDEE, see

“Building, deploying, and

launching a project” (page 36)

.

Creating a local makefile project from scratch

Create a makefile project using one of the following methods:

Create a makefile project

Create a managed project as described in

“Creating a managed project from scratch” (page

16)

so that the initial makefiles are created for you. To manage the generated makefiles,

deselect Generate Makefiles automatically in the C/C++ Build page of the project properties.

This section focuses on creating a makefile project. To create a local makefile project from scratch,
select one of the new project actions from the context menu of the NonStop Project Explorer view
for either the C, C++, COBOL, or pTAL. For makefile projects, the resulting project is the same
regardless of the language associated with the new project wizard. The following example uses
the NonStop C Project wizard.

To create a local makefile project from scratch:

1.

From the context menu of the NonStop Project Explorer view, select New

→Makefile Project

with Existing Code. This opens the Import Existing Code wizard.

2.

In the Import Existing Code wizard:
a.

Enter Makecar in the Project name: field.

b.

Optionally, deselect the Use default location check box and enter a location to store your
project. By default, if a location is not specified NSDEE stores your project in a top-level
directory in your workspace directory.

c.

Select Empty Project under the NonStop Makefile Project folder.

d.

Under Toolchains:, select C-C++ TNS-E Tools. For Makefile projects, tool chains define
where the C/C++ indexer looks for system headers. Optionally, NSDEE sets up
COMP_ROOT

(which cross compilers use to find headers) based on your tool chain

selections.

By default, one build configuration named Default is created for each tool chain you
select.

3.

Select Next > to open the Initial Build Settings dialog.

4.

In the Initial Build Settings dialog, select the tools root the C/C++ indexer uses to find symbols
in system headers. To have NSDEE to set the COMP_ROOT environment variable (and you do
not plan to set it in your makefile), select the check box labeled Set COMP_ROOT and update
PATH based on tools root above.

5.

Select Finish.

NSDEE creates your project. The NonStop Explorer view shows the root of your project using a
project folder icon

followed by the project name. To see the project content, expand the folder

which initially contains only an Includes folder. The Includes folder is a link to the system
include directory of the cross compilers and tools indicated during project creation. CDT uses this
link to help build a database of C and C++ symbols. For more information, see

“Ensuring the

C/C++ indexer runs” (page 33)

.

30

Getting started

This manual is related to the following products: