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

Figure 26 ETK import wizard
Eclipse and NSDEE projects have much more constrained structures than ETK projects. NSDEE
projects are typically confined to the directory structure under the top-level directory of the project.
Build output is typically written to a subdirectory of the project and files external to the project are
referenced in compiler and linker options and are not directly part of the project.
The structures of ETK projects, on the other hand, are much less constrained and can vary greatly
among solutions. Build output is often written outside of projects, and the files shown as part of the
project often don’t actually exist under the project directory.
Preparing to import ETK projects
Before you use the Import ETK Projects wizard, plan how you want to go about importing projects.
One thing you need to decide before importing ETK projects is where you want the NSDEE projects
to reside. Unless your ETK projects are self-contained (with all project files under a top-level project
directory), having the import wizard copy ETK projects into your workspace will not work well.
Also, if you want your NSDEE projects to point to files already under source control, it is best not
to use the import wizard’s Copy projects into workspace option. Your project should point into the
location of the files under source control instead. NSDEE will not change your project structure,
though it will add .project and .cproject as top-level project files.
HP recommends you do a trial run of importing ETK projects to NSDEE to find out what obstacles
may be left after the import process. After importing ETK projects, the import wizard will point you
at a log file where it records errors or warnings. After addressing issues in the log file, try building
each imported project one at a time to see what sort of issues, if any, occur during builds. You
might also want to check if ETK macros were mapped to NSDEE equivalents (called “build variables”
in Eclipse) in a way that works with your project structure. For information on viewing project build
variables, see
“Setting build variables” (page 86) .
NOTE: The ETK macros SolutionExt, ETKInstallDir, and macro names that begin with
CORBA are not supported and are not set in imported ETK projects.
70 Tasks