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

@echo 'Finished building: $@'
@echo ' '
$(MAKE) --no-print-directory my-post-deploy
NSDEE does not create these targets for you. You must create them in a makefile.targets file
as a top-level file in your project. The main makefile will include the deploy targets you define in
this way.
Example 9 “Sample definitions of my-pre-deploy and my-post-deploy” shows sample definitions
that simply print some text, but you can define them 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
You can use NSDEE local projects 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's file repository into NSDEE's
NonStop Project Explorer for editing and building.
NSDEE saves all information it has about each of your projects in two files directly under the project
directory. These are .project and .cproject, both of which save information in XML format.
It is important that these two files are checked in to your SCM repository in addition to your source
files. The content of these files will be saved whenever you change project settings or add build
targets.
For remote projects, NSDEE saves very little information on your local Windows system, but what
it does save 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 116) . For an example of using NSDEE with SCM
tools, see “Using NSDEE with SCM tools: examples and procedures” (page 117) .
Note that, in addition to saving project files in an SCM repository, if you want to ensure full
repeatability of builds, consider also adding 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 Samba locations on NonStop systems that you've
mapped to a drive on Windows. These links appear as folders in your local projects. Creating a
linked folder enables you to drag and drop files to and from the mapped location on NonStop.
For more information on creating linked folders, see
“Creating a remote folder in a local project
via Samba” (page 119) .
Using NonStop projects with an SCM tool 61