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

@echo 'Finished building: $@'
@echo ' '
$(MAKE) --no-print-directory my-post-deploy
NSDEE does not create these targets. You must create these targets in a makefile.targets file
as a top-level file in the project. The main makefile includes the deploy targets defined with this
method.
Example 9 “Sample definitions of my-pre-deploy and my-post-deploy” shows sample definitions
that print some text, but can be defined in more useful ways.
Example 9 Sample definitions of my-pre-deploy and my-post-deploy
my-pre-deploy:
@echo "Pre-deploying . . ."
@echo "Pre-deploy complete!"
@echo ' '
my-post-deploy:
@echo "Post-deploying . . ."
@echo "Post-deploy complete!"
@echo ' '
Using NonStop projects with an SCM tool
NSDEE local projects can be used with a software configuration management (SCM) tool in one
of two ways. The first is to use an Eclipse plug-in provided for use with an SCM tool to check-in
and check-out files directly in Eclipse. Examples of such plug-ins include the Subclipse plug-in for
Subversion and the Eclipse CVS Client for CVS. The second is to use an SCM outside of Eclipse
to check-in and check-out files, and to import projects from the SCM file repository into the NSDEE
NonStop Project Explorer for editing and building.
NSDEE saves all project information in two files directly under the project directory. These files are
.project
and .cproject, which save information in XML format. These two files must be
checked in to your SCM repository in addition to your source files. The content of these files is
saved whenever you change project settings or add build targets.
For remote projects, NSDEE saves minimal information on your local Windows system. This saved
information is also written to .project and .cproject files.
To enable viewing .project and .cproject in the NonStop Project Explorer view, see “Filtering
NonStop Project Explorer view content” (page 120) . For an example of using NSDEE with SCM
tools, see “Using NSDEE with SCM tools: examples and procedures” (page 121) .
TIP:
To ensure full repeatability of builds, in addition to saving project files in an SCM repository also
add the following files to your SCM repository (typically after a final product build):
•
System headers provided in the cross compiler installation area.
•
Any files you copy to your PC to use in builds such as SPI headers, link libraries, and so on.
•
All makefiles (if you use makefile projects) or all makefile fragments you contribute to managed
builds such as makefile.targets.
Using Samba with NSDEE
NSDEE supports creating links in local projects to mapped Samba drives on NonStop systems.
These links appear as folders in your local projects. Creating a linked folder enables dragging
and dropping files to and from the mapped location on NonStop. For more information on creating
linked folders, see
“Using Samba with NSDEE” (page 65) .
Using NonStop projects with an SCM tool 65