Preparing to import etk projects, Etk import wizard – HP Integrity NonStop J-Series User Manual
Page 74

Figure 26 ETK import wizard
Eclipse and NSDEE projects have 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 external project files are referenced
in compiler and linker options and are not directly part of the project.
ETK project structures are 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 do not actually
exist under the project directory.
IMPORTANT:
Migration of Visual Studio or CORBA projects is not supported.
Preparing to import ETK projects
Before you use the Import ETK Projects wizard, plan the process for importing projects.
Before importing ETK projects, decide where the NSDEE projects will reside. Copying ETK projects
into your workspace only works well for ETK projects that are self-contained (with all project files
under a top-level project directory). If you want your NSDEE projects to point to files already under
source control, do not use the Copy projects into workspace option in the import wizard. Point your
project to the location of the files under source control instead. NSDEE does not change your
project structure, however it adds .project and .cproject as top-level project files.
HP recommends a trial run of importing ETK projects to NSDEE to identify outstanding issues after
the import process. After importing ETK projects, the import wizard points to a log file containing
errors or warnings. After resolving these log file issues, try building each imported project one at
a time and review issues, if any. Also verify that ETK macros are successfully mapped to NSDEE
equivalents, “build variables” in Eclipse. For information on viewing project build variables, see
“Setting build variables” (page 90)
NOTE:
The ETK macros SolutionExt, ETKInstallDir, and macro names that begin with
CORBA
are not supported and are not set in imported ETK projects.
74
Tasks