NonStop Development Environment for Eclipse User Guide HP Part Number: 677973-001 Published: June 2012 Edition: NSDEE 3.0 and later versions, J06.10 and subsequent J-series RVUs, H06.
© Copyright 2012 Hewlett-Packard Development Company, L.P. Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor’s standard commercial license. Export of the information contained in this publication may require authorization from the U.S. Department of Commerce.
Contents 1 Introduction.............................................................................................10 Related documentation............................................................................................................10 2 Before you begin......................................................................................11 3 Getting Started........................................................................................12 Preparing the Workbench......................
NSDEE_DEPLOY_SYSTEM, NSDEE_DEPLOY_USER, NSDEE_DEPLOY_DEST, NSDEE_DEPLOY_FILENAME................................................................................................45 SQL/MX_COBOL_PREPROCESSOR_LOC..............................................................................46 Managed build makefiles........................................................................................................47 Handling dependencies in managed builds......................................................
Instructing NSDEE not to build source files...............................................................................100 Excluding a single COPY library........................................................................................100 Excluding all sources in a folder.........................................................................................101 Turning off SQL/MP builds for source files and folders...............................................................
Preferences..........................................................................................................................136 NonStop Development......................................................................................................136 Code Templates...............................................................................................................136 Network Connections......................................................................................................
Figures 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 Remote Makefile Project wizard.........................................................................................28 Build Settings wizard page................................................................................................29 Properties for MakeCar project..................................................................................
52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 Create New Configuration dialog......................................................................................91 Symbols tab of the Path and Symbols property page.............................................................96 Disabling record field errors..............................................................................................
11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 Remote Settings page settings (SQL/MX) ..........................................................................129 Remote Settings page settings (SQL/MP) ..........................................................................129 Import Existing Code wizard settings................................................................................130 Remote Makefile page settings....................................................................
1 Introduction The NonStop Development Environment for Eclipse (NSDEE) is a set of Eclipse plug-ins that extend Eclipse's C/C++ Development Tooling (CDT) to provide an integrated development environment (IDE) for developing NonStop applications on Windows. NSDEE supports building applications and editing source files both locally (on Windows) and remotely (on NonStop).
2 Before you begin IMPORTANT: NSDEE 3.0 has changed significantly since NSDEE 2.1. NSDEE 2.1 and NSDEE 3.0 local projects are not compatible. For details, refer to “What's New at NSDEE 3.0?” (page 148). NSDEE provides capabilities for building applications on both local Windows and remote NonStop systems. Local Windows-hosted builds require a make program (as provided by Cygwin or Msys) and cross compilers for building NonStop applications on Windows.
3 Getting Started This chapter provides an introduction to how to use NSDEE, from creating and building projects to enabling C/C++ features based on indexing.
Specifying Tool Locations There are three types of tools whose locations NSDEE must have access to before you can build on Windows: • NonStop cross compilers and linkers • SQL/MX preprocessors (only needed when building SQL/MX applications) • The location of a bin directory containing make and other tools (provided by Cygwin or Msys) If these tools are installed at standard locations, then NSDEE will automatically find them.
Configuring connections to NonStop systems NSDEE provides one place where you can define how you want to connect to NonStop systems when you transfer files or deploy build results to NonStop systems, or when you launch applications on NonStop systems from NSDEE; that place is the Network Connections preferences page. Using Network Connections preferences, you can create named connection configurations in the form system_name_or_IP (user_ID_or_alias).
This section also provides an example of how to create multiple managed projects to build a single application. NOTE: For the most detailed descriptions of project wizards, read the sections about creating projects from scratch. Other sections regarding project creation provide much less detail and, instead, focus on short descriptions of how to create projects. Creating a managed project from scratch Before creating a managed project, you need to decide what the primary language for the project will be.
4. 5. The Basic Settings page lets you configure author and copyright information to be placed in the comment header of the source file. It also lets you configure the text string used in the print statement of the source file. Finally, the Source field lets you set the name of the initial source directory. You can simply leave these fields unchanged. Select Next > to open the Initial Build Settings page.
The TNS/E tools root: combo box should automatically be set to the location of the latest TNS/E cross compilers and tools. If it is empty, refer to “Specifying Tool Locations” (page 13). If you select the Configure Locations... link to the right of the combo box, it will open Tool Location preferences to the Cross Compilers tab: 6. Select Next >. The resulting Remote Settings page provides a way for you to specify a location on a NonStop server where you'd like final build objects to be transferred.
The Advanced Settings... button opens project properties for the project you are about to create. Project properties let you change tool options, environment variables, and other project settings. These settings are available after you create a project by selecting your project in the NonStop Project Explorer view and then selecting Properties from the context menu. Leave this page unchanged for now. 8. Select Finish. NSDEE will now create your project.
uses a sample program named GeneralCpp. You can get the sources for both by unzipping the following file: eclipse install directory\plugins\com.hp.nsdee_3.0.n\Examples.zip The following examples assume you unzipped Examples.zip to C:\Examples, but you can use whatever location you prefer. NOTE: This section focuses on examples of creating projects from existing sources. For more detailed descriptions of project creation wizards, see “Creating a managed project from scratch” (page 15).
5. 6. Select Next >. If you would like to enter a remote system and location (so you can try deploying Car to a NonStop system), select a remote system and user now and specify a remote location. Select Finish. You should now see your Car project in the NonStop Project Explorer view.
Later, you can return to the C Element Filters dialog to hide .project and .cproject again, if desired. The .project and .cproject files define attributes of the Car project, including any customizations you make. If you save your projects in a Source Configuration Management system, it is important to save these files in addition to your source code. For information about how to build, deploy, and launch Car, skip ahead to “Building, deploying, and launching a project” (page 33).
5. 6. Select Next >. If you would like to enter a remote system and location (so you can try deploying GeneralCpp to a NonStop system), select a remote system and user now and specify a remote location. Select Finish. Now you need to import the sources for GeneralCpp into your project. To do so, perform the following steps: 1. Select the GeneralCpp project folder in the NonStop Project Explorer view. 2. Select Import...
To create the CarParts project, perform the following steps from the NonStop Development perspective: 1. Select New > C++ Project from the context menu of the NonStop Project Explorer view. 2. In the resulting NonStop C++ Project wizard, do the following: a. Enter the name CarParts for your project in the Project name: field b. Deselect the Use default location check box and enter this location: C:\Examples\MultiProjectCarApp\CarParts c. Select Empty Project in the NonStop Linkfile folder. d.
4. 5. In the Project References page on the right (and shown above), select the checkbox for CarParts. Select OK. The last bit of setup you need to do is a) point the Car project at include files in the CarParts project and b) have Car link in the build artifact (linkfile) created by CarParts. To do this setup, perform the following steps from the NonStop Development perspective: 1. Select the Car project in the NonStop Project Explorer view. 2.
9. To the right of Other objects, select the Add button ( ). 10. In the Add file path dialog, enter the following path in the File: field: ../../CarParts/Debug/CarParts.tlo 11. Select OK to dismiss the Add file path dialog and apply the change. 12. You need to make a similar change to the Release build configuration. In the Configuration: combo box at the top of the page, change the configuration to Release. 13.
TIP: The Console view keeps build output separate for each project. Since the Car project was built last, its build output is shown in the Console view. If you select CarParts in the NonStop Project Explorer view, the Console will switch to showing build output for CarParts. TIP: Building Car and CarParts produces more output than the default Console view can show. By default, the Console view limits output shown to 500 lines.
You will need to create your own directory, sources, and makefile. Creating a local makefile project from existing sources This section provides an example of creating a makefile project from existing sample sources for a simple application named Car. You can get the sources for Car by unzipping the following file: eclipse install directory\plugins\com.hp.nsdee_3.0.n\Examples.zip The following example assumes you unzipped Examples.zip to C:\Examples, but you can use whatever location you prefer.
how to build, deploy, and launch MakeCar, skip ahead to “Building, deploying, and launching a project” (page 33). Creating a remote makefile project Remote makefile projects are hosted on a NonStop system where the source files and makefiles reside. Creating a remote makefile project allows you to edit remote source files and launch builds from NSDEE.
7. 8. The Referenced remote makefile projects: list will be empty unless you previously created remote projects in your current workspace. The list lets you specify other remote projects that should be built before your current project is built. Select Next > to continue to the Build Settings wizard page (Figure 2 (page 29)). Figure 2 Build Settings wizard page 9.
Adding folders and files to projects NSDEE provides a number of different wizards for adding folders and files to a project. All of these wizards are available from the New sub-menu of the NonStop Project Explorer view context menu. Table 1 (page 30) summarizes the wizards available and their capabilities.
Figure 3 Properties for MakeCar project Not all project properties are specific to building your project. Those that are specific to builds typically have the Configuration: combo box shown in Figure 3 (page 31), which allow you to choose the configuration whose settings you want to view or modify. The entries under C/C++ Build allow you to configure different aspects of your builds. Table 2 (page 31) lists a brief summary of what you can configure using each entry under the C/C++ build node.
1. 2. 3. 4. 5. 6. 7. Select the Car or GeneralCpp project in the NonStop Project Explorer. Select Properties from the NonStop Project Explorer context menu to open the Properties dialog. In the Properties dialog, expand C/C++ Build and select Settings to open the Settings page. In the Settings page, select the Tool Settings tab (if the Tool Settings page is not already showing).
Building, deploying, and launching a project The steps for building, deploying, and launching a project are quite similar for all types of NSDEE projects, though, of course, a remote project need not be deployed to a NonStop system before launching it. Building a project To build a project, perform the following steps from the NonStop Development perspective: 1. In the NonStop Project Explorer, select the project you want to build. 2. Check which build configuration (typically Release or Debug) is active.
TIP: Hover your mouse over the deploy icon ( ) in the tool bar to see which project it will deploy. For example, if you've selected a project named Hello World and the active build configuration for that project is Debug, then the tool tip will read: "Deploy 'Debug' for project 'Hello World'". TIP: The pull-down menu next to the deploy icon lets you change the current build configuration and initiate a deploy in a single step.
4 Concepts This chapter supplements the "Concepts" chapter of the C/C++ Development User Guide, providing details specific to NonStop development. NSDEE overview NSDEE extends Eclipse's C/C++ Development Tooling (CDT) to enable its use for developing NonStop applications, including applications built with C, C++, COBOL, pTAL, SQL/MP, and SQL/MX.
• NonStop Linkfile— A project that manages builds of a linkfile, which is a collection of object files that can be linked into another project build. Linkfile projects allow you to break up your application into multiple projects. • NonStop Archive Library — A project that manages builds of an archive file using the ar tool. • NonStop User Library — A project that manages builds of a user library (TNS/R only). • NonStop Makefile Project — A project that does not manage builds.
Figure 4 NonStop Development perspective Views The views shown in Figure 4 (page 37) are: • The NonStop Project Explorer view, which provides access to your NonStop projects and their associated properties and files. You also use the NonStop Project Explorer view to select projects to build and to select build configurations to be used in builds. For details, see “NonStop Project Explorer view” (page 124).
Preferences Preferences allow you to change the default behavior of Eclipse. You can change preference settings using the Preferences dialog, which you can open by selecting Window > Preferences. Many preference settings in Eclipse apply to NSDEE, particularly those under the General and C/C++ categories in the Preferences dialog. Preferences specific to the NonStop Development perspective are available under the NonStop Development category.
Building NonStop projects Eclipse defines two build actions that you can invoke from several places in the IDE — Build Project and Clean actions. By default, these actions invoke make all and make clean respectively. In addition, Eclipse defines the actions Build All (to build all projects in your workspace) and Build Working Set (to build a predefined group of projects).
SQL managed builds NSDEE's managed builds support both SQL/MX and SQL/MP. To create a project with managed builds that will support SQL/MX or SQL/MP, you must select the SQL/MX or SQL/MP radio button on Initial Build Settings page of the new project wizard. When you create a project that supports SQL/MX or SQL/MP, NSDEE will add SQL tools to the tool chain for your project. For more information, see “Tool Chains” (page 51).
Table 3 Build Variables and Environment Variables (continued) Variable Name Type Local Projects Type PATH environment Managed, unmanaged (optional for unmanaged) Specifies where cross compilers and make program are located. Prepending the cross compiler bin location is optional for unmanaged projects. Prepending the make program bin location is optional for both managed and unmanaged projects. NONSTOPOSVERSION environment Managed, unmanaged Specifies the RVU (for example, H06.23 or G06.
on your Windows system, where RVU_ID is the ID of the RVU a particular set of tools was released on. (For older installations, the location is C:\Program Files\Compaq ETK-NSE\ Here are two examples of actual COMP_ROOT locations: C:\Program Files\HP NonStop\H06.24 (RVU H06.24 for TNS/E) C:\Program Files\HP NonStop\G06.32 (RVU G06.
Example 2 Indexer options By default, a fixed build configuration is used, but you can choose Use active build configuration if you want the indexer to rebuild its database each time you change target architectures. Or, you can select Use fixed build configuration if you'd like to continue using a fixed build configuration; but you can change which build configuration is used by changing the value in the combo box shown in Example 2 “Indexer options”.
If NSDEE_CONN_PORT is not set (as when you invoke make outside of NSDEE), Deploy.jar checks if $HOST_PASS pass is set. If it is, Deploy.jar uses its own copy of FTP or SFTP to transfer a file and uses $HOST_PASS as the password. nsdee-auth is a small program that also checks if NSDEE_CONN_PORT is set. If it is, it requests passwords from NSDEE via that port. If NSDEE already has the password, it simply returns it on the port; else, NSDEE prompts you for a password.
options that take oss or guardian as an argument (-Wsystype= for compiler and linker tools, -q for Deploy.jar). This is useful when you need to change the target platform for a build configuration. You need only change the variable value and not each and every instance of -Wsystype= and -q options across tools.
Figure 6 Settings for projects with SQL/MP compilation, SQL/MX compilation, and no SQL compilation SQL/MX_COBOL_PREPROCESSOR_LOC For COBOL projects with SQL/MX, NSDEE sets the environment variable SQLMX_COBOL_PREPROCESSOR_LOC to the location of the SQL/MX preprocessor for COBOL as specified in the Tool Locations project property page. SQLMX_COBOL_PREPROCESSOR_LOC is used in the -Wcobol="CONSULT..." argument in the Miscellaneous page of the COBOL Compiler tool to pass the location of esqlcli.
Figure 7 Setting the location of SQL/MX Preprocessor for COBOL Managed build makefiles When you initiate a build for a managed project, NSDEE generates makefiles before invoking make. Three of these makefiles are written to the top-level build directory. Typically there will be two build configurations per architecture you build for. If, for example, your application is built only for TNS/E, then the two top-level build directories will be named Debug and Release.
Figure 8 Layout of simple project Handling dependencies in managed builds To ensure C and C++ objects are rebuilt when header files they depend on are changed, NSDEE adds commands to build rules to generate dependency files.
NSDEE writes build rules such that the dependency list the compiler generates is piped to grep to remove system headers (-v -e '$(NSDEE_SYS_INCLUDE_PATH_ESC)') and the source file itself (-v -e 'Door.cpp'), as that dependency is specified for the .o file at the top of the build rule ("src/Door.o: ../src/Door.cpp"). NSDEE writes build rules such that the dependency list the compiler generates is piped to grep to remove system headers: (-e $(NSDEE_RVU)) and the source file itself (-e Door.
and you remove the file Wheel.h, the next build of CarTest.o will fail because make will be unable to locate Wheel.h. This is because dependency files are generated after object files are built. So NSDEE does a final pass over dependency files to address this issue by adding dummy rules for header files that resolve to nothing. At the same time, NSDEE cleans up the list of object files. The result on the above example would look like this: CarTest.o: ../src/Car.h ../../CarParts/src/Wheel.h ../..
Example 4 Sample build rule for testmx.c EC_DEPS += \ ./src/mxprog.dep src/testmx.c: ../src/testmx.ec @echo 'Building file: $<' @echo 'Invoking: C/C++ SQL/MX Preprocessor (TNS/E)' c89 -I"C:\Users\doon\workspace\testmx\mxheaders" -Wsystype=oss \ -Wsqlmx=preprocess_only -Wsqlmx_port=18650 -Wcall_shared \ -Wsqlhost=nonstopsystem.corp.net -Wsqluser=sdev.doon,\ `"C:/e3.7/eclipse/plugins/com.hp.nsdee_3.0/Tools/nsdee-auth.exe"\ invoke nonstopsystem.corp.net sdev.doon` -Wsqlmxadd='-c "$@" -V "$*.
Tools for a simple C project If you create a simple C project, the tool chain will consist of a C Linker, a C Compiler, and a Deploy Tool. (The Deploy Tool transfers the final build object of a project to a NonStop system using a program named Deploy.jar, which is part of NSDEE. Example 5 “A simple C tool chain for TNS/E” shows a TNS/E tool chain for a simple C project as it appears in the Tool Settings tab of the Settings property page.
Figure 9 Miscellaneous option category for the C Linker All tools include a Miscellaneous options page where you can specify most tool options. Explicitly defined tool options, such as the Verbose check box in Figure 9 (page 53), are for common options and are there for your convenience. But you also have the option of entering -Weld=-verbose directly in the additional options box. Use of option categories is required for the following entities: • Object files from other projects.
NOTE: If you select the Destination option group of the Deploy Tool, you will see that all the fields are disabled (though they may have values in them). This is due to a limitation in CDT's interface for specifying options. NSDEE works around this limitation by providing the Settings (Remote) property page, which you can use to change settings in the Destination options group.
Figure 11 Tools with SQL/MP settings NOTE: All options settings related to remote NonStop systems and locations are disabled on options pages. This is due to a CDT limitation. To change values for such settings, go to the Settings (Remote) property pages. TIP: You can turn off SQL preprocessing options for any source file or any source directory by selecting the source file or directory and opening the Settings page.
Figure 12 Creating a project with SQL/MX support Figure 13 (page 56) shows the tool chain for a simple C project with SQL/MX. Figure 13 Tool chain for simple C project with SQL/MX NOTE: All options settings related to remote NonStop systems and locations are disabled on options pages. This is due to a CDT limitation. To change values for such settings, go to the Settings (Remote) property pages. The C/C++ SQL/MX Preprocessor tool invokes the C compiler with options for preprocessing SQL/MX statements in .
build configuration. Figure 14 (page 57) shows where the sqlmx.c file is written for a Debug build of sqlmx.ec. Figure 14 Location of SQL/MX preprocessor output The C/C++ SQL/MX Compile tool invokes the C compiler with options for performing an SQL/MX compile. The deploy target for the main makefile or SQL/MX builds results in both an SQL/MX compile and an invocation of Deploy.jar.
Customizing managed builds Though managed builds generate makefiles for you, you can still customize managed builds. NSDEE provides two separate mechanisms for customizing managed builds. The first mechanism involves writing your own version of top-level makefile targets. The second mechanism involves using project properties to add commands to be invoked before and after Build Project and Deploy Project actions.
Figure 15 Adding pre-build and post-build steps Example 7 “Build Output with pre-build and post-build steps” shows the pre-build and post-build targets added to the main makefile on the next build as a result of setting the project properties. This example also shows how the "all" target depends on "pre-build", and the rule for the final executable (Car.txe in this case) invokes the post-build step (via $(MAKE) --no-print-directory post-build).
Example 7 Build Output with pre-build and post-build steps # All Target all: pre-build main-build # Main-build Target main-build: Car.txe # Tool invocations Car.txe: $(OBJS) $(USER_OBJS) @echo 'Building target: $@' @echo 'Invoking: C++ Linker (TNS/E)' c89 -Wcplusplus -Wsystype=guardian -Wcall_shared -o "Car.txe" $(OBJS) $(USER_OBJS) $(LIBS) @echo 'Finished building target: $@' @echo ' ' $(MAKE) --no-print-directory post-build . . . pre-build: -@echo 'Pre-build action' -echo "Build is starting...
@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.
5 Tasks This chapter provides step-by-step procedures for performing many common tasks in NSDEE. Configuring Tool Locations NSDEE project properties and new project wizards present you with a list of available tools to choose from. Figure 16 (page 62) shows an example of these settings as seen in the Tool Locations property page for a managed project that builds an SQL/MX application.
Figure 17 Add Cross Compiler Location dialog 3. The Location: field will contain the location under which all NonStop cross compilers are typically installed and the Auto-detect button will be selected. Select OK. 4. Back in the Tool Locations preference page, select OK. The locations of any newly installed compilers will be added to the list.
1. 2. 3. 4. Select Configure Tool Locations... from the NonStop Tools menu. In the Tool Locations preference page, select the Cygwin/Msys tab. In the Cygwin/Msys page, enter the path of a Cygwin bin directory in the Cygwin bin: field or the path of an Msys bin directory in the Msys bin: field. (Alternatively, select Browse... to open a directory browser which you can use to find the location.) Select OK.
Figure 20 Network Connections preferences page 2. 3. In the preference page, select Add/Remove... In the Add or Remove Connection Configurations dialog (Figure 21 (page 65)), type in an IP address or a system name in the System: field and click the Add button. TIP: If you have already configured one or more remote connections and you want to reuse the settings from an existing configuration, select it in the list of connection configurations, then select Copy, and then OK.
5. 6. 7. Enter a user name or alias in the User name: field. Select the protocol you prefer to use. Select SSH/SFTP to always use secure, encrypted authentication and for encrypted file transfers and remote program launches. See one of the following sections for information on how to change settings for the protocol you choose. Select OK to apply your changes and dismiss the Preferences dialog.
Changing Telnet and FTP settings To change Telnet and FTP settings, perform the following steps from the NonStop Development perspective: 1. Open the Network Connections preference page (Figure 20 (page 65)) by selecting NonStop Tools > Configure Connections... 2. Use the System: combo box to select a connection configuration whose Telnet/FTP settings you will change. 3. Open the Telnet/FTP Settings dialog (Figure 23 (page 67)) by selecting the Settings... button to the right of the Telnet/FTP button.
Table 4 Telnet/FTP settings (continued) 5. 6. Setting Description Service or window name: button Enter the name of a service (such as TACL or OSH) or a static window (such as #WIN05) NSDEE is to choose when logging in. Enter Choice> prompt: combo box Choose On if Telserv is configured to show the Enter Choice> prompt during login. Authentication: combo box Choose On if Telserv is configured to prompt for user name and password when you login.
Figure 24 Export Connection Configurations dialog 3. 4. 5. In the Export to: field, enter the path of the file where you want exported configurations written (or simply leave the default setting, which is the file connections in your home directory). Optional: Select Overwrite existing file without asking if you are not concerned about overwriting an existing file. Select Finish.
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.
If you run into problems with imported ETK projects that you can’t fix, HP encourages you to contact your HP Support representative. Importing one or more ETK projects To import one or more ETK projects associated with a solution, perform the following steps from the NonStop Development perspective: 1. Select Import ETK Projects... from the NonStop Tools menu. 2. In the Import ETK Projects wizard, enter the path of the solution file associated with the ETK projects (or select Browse...
NOTE: NSDEE 2.x local projects cannot share the same workspace with an NSDEE 3.0 project with the same name. To import an NSDEE 2.x project as an NSDEE 3.0 project, you must import the NSDEE 2.x project into another workspace. NOTE: NSDEE 2.0 remote projects cannot be directly imported into NSDEE 3.0. They must be imported into NSDEE 2.1 first, then imported into NSDEE 3.0. NOTE: NSDEE 2.1 remote projects have not changed at NSDEE 3.0. You can import them into an NSDEE 3.
5. 6. Select Add project to working sets if desired. (See the Eclipse Workbench Guide for information on working sets.) Select Finish to import all selected NSDEE 2.x projects as NSDEE 3.0 projects. If the import completes without errors or warnings, NSDEE displays this dialog (which you can dismiss by selecting OK). If the import completes with errors or warnings, NSDEE displays a dialog similar to that shown in Figure 30 (page 73). Select the link to the log file to open the log and view its contents.
Creating Windows-hosted projects with managed builds To create a Windows-hosted project with managed builds using cross compilers and tools, perform the following steps from the NonStop Development perspective: 1. Select one of the following menu items from the New submenu of the File menu: • C Project • C++ Project • COBOL Project • pTAL Project A new project wizard will be opened (such as the NonStop COBOL Project wizard shown in Figure 31 (page 74)) that is specific to the menu item you choose.
5. 6. Select either one or both tool chains in the Toolchains list, depending on whether you want to build for TNS/R, TNS/E, or both. Select Next > to continue to the Initial Build Settings page of the wizard: Figure 32 Initial Build Settings page (COBOL executable project) 7. In the Target platform: row, choose the platform you want to build the project for by selecting either the OSS or Guardian button.
13. In the SQL tools: row, select SQL/MX or SQL/MP if the project source will contain SQL statements. This results in SQL-specific tools being added to the tool chain for the project. 14. If you chose the SQL/MX button in step 13, the SQL/MX Preprocessor Locations group box will be enabled. The fields in the group box specify the location of the SQL/MX preprocessors for C/C++ and COBOL. If the fields are empty, select Configure locations... to establish their location. 15.
Figure 33 Select Configurations page (managed build project) 17. Select Finish to dismiss the wizard and create your project. Creating Windows-hosted makefile projects To create a Windows-hosted project for which you will supply the makefile, perform the following steps from the NonStop Development perspective: 1.
Figure 34 Initial Build Settings page (makefile project) 7. Depending on your tool chain selections, you will see a TNS/E tools root:row, a TNS/R tools root: row, or both. Select the root directories of the RVUs to be used to build your project for TNS/E and TNS/R. If a tools root combo box is empty, select the Configure locations... link to establish where cross compilers and tools are located on your system.
Figure 35 Select Configurations page (makefile project) 11. Select Finish to dismiss the wizard and create your project. Creating Windows-hosted projects from existing source To create a project using an existing source base, you can follow the steps in one of the following procedures: • “Creating Windows-hosted projects with managed builds” (page 74) • “Creating Windows-hosted makefile projects” (page 77) with a slight change to change to step 3.
Figure 36 Import Existing Code wizard 2. 3. 4. 5. 6. 7. Enter a name for your project in the field in the Project Name group box. Enter the location of your source base in the field in the Existing Code Location group box (or select Browse... to browse for the location). In the Tools root: row, select the root directory of the RVU to be used to build your project. If the tools root combo box is empty, select the Configure locations...
Figure 37 Remote Makefile Project wizard 2. 3. 4. 5. 6. 7. 8. Enter a project name in the Project name: field. Select the remote NonStop system that will host the project using the Build system: combo box. (To add systems to the combo box, select Edit... to open Network Connection preferences.) In the Platform: row, select OSS if your project will build using OSS tools, or Guardian if your project will build using Guardian tools.
Figure 38 Build Settings page 9. Optionally: set a non-default build command and non-default Build and Clean makefile target names. 10. If you don't already have an existing makefile under the remote project location, select the Create makefile check box to have NSDEE create an empty makefile for you. 11. If you selected the Guardian platform in step 4, select the editor you want to open Guardian source files with by default in the Default editor: combo box.
Figure 39 Run Configurations dialog Once you've created a run configuration, you can reuse it to run your application without having to respecify information you saved in the run configuration The following sections describe: • “Creating a run configuration” (page 83) • “Launching an application using a saved run configuration” (page 86) Creating a run configuration To create a run configuration, perform the following steps from the NonStop Development perspective: 1. Select Run Configurations...
d. e. Enter a path to the executable you want to run in the NonStop executable's path on NonStop system: field (or select Browse... to browse for executables on the remote system). Optional: If the program you want to run is on your local Windows system and you want to transfer it to the NonStop system prior to launching it, select the check box for Local executable to be transferred to NonStop path specified above:, then enter the local path of the executable (or select Browse...
Figure 41 Environment page for OSS launches Figure 42 Environment page for Guardian launches b. Select the top radio button if you want to enter environment variables settings (OSS) or DEFINEs, ASSIGNs, and PARAMs settings (Guardian) directly in the text box below it. For OSS, these settings will be issued directly in the shell.
NOTE: Standard Input and Output options and the Launch in background option are ignored for NSDEE projects. Those options are specific to applications run locally on Windows. 8. To save your new run configuration, you can select Run, which will both save the run configuration and launch your application. Alternatively, you can select Apply and then Close to save your run configuration but postpone launching your application.
1. 2. 3. In the NonStop Projects Explorer view, select a project that you want to change TARGET_SYSTYPE for. Select Properties from the context menu of the NonStop Projects Explorer view. Select the Build Variables entry under C/C++ Build (see Figure 45 (page 87)). Figure 45 Build Variables property page 4. Select the Show system variables check box, then select TARGET_SYSTYPE (see Figure 45 (page 87)). 5.
Figure 47 (page 88) shows the Tool Settings page for a C project with SQL/MX and managed builds. Figure 47 Tool Settings tabbed page When you select the main entry for a tool on the left of the Tool Settings page, the right side of the page displays the command the tool invokes as well as the options that will be passed to the tool. To edit options passed to a tool, select one of the categories below the tool on the left.
6. 7. 8. Select the Add button ( ) to open the Enter Value dialog. Enter –WIEEE_float in the Enter Value dialog, then select OK. Select OK to apply your change and dismiss the Properties dialog. Specifying DEFINES for SQL/MP tables Cross compilers provide the –Wdef_obey= option for passing in an Obey file which sets up DEFINEs. You can, for example, use ADD DEFINE statements to map logical SQL table names to physical table names and avoid hard coding SQL table names in source code.
9. Select the Add button ( ) to open the Enter Value dialog. 10. Enter –Wdef_obey=C:\mydefines.txt in the Enter Value dialog, then select OK. 11. Select OK to apply your change and dismiss the Properties dialog. Building for both OSS and Guardian When you create a project with managed builds, the initial project is set up to build for OSS or Guardian, but not both.
Figure 52 Create New Configuration dialog 4. 5. 6. 7. 8. 9. Enter a name for the build configuration (such as Debug Guardian) and optionally enter a description. Make sure Existing configuration is selected and that the configuration specified to the right of it is Debug. This will result in all settings in the Debug configuration being copied to your new configuration. Select OK to add the new configuration and dismiss the Create New Configuration dialog.
Example 10 Incorrect errors for new project source file You can remove the erroneous errors by forcing the indexer to run: 1. In the NonStop Project Explorer view, select the project associated with the source file. 2. Select Index > Rebuild from the NonStop Project Explorer view context menu. Erroneous errors and warnings for SQL Statements By default, CDT’s C/C++ code analysis marks SQL statements in C/C++ source with errors and warnings.
Example 11 Example of errors and warnings shown for SQL statements Unfortunately, the .sqlmxStatements.txt and .sqlmpStatements.txt are read only when Eclipse is started. So you must restart Eclipse after creating a project before erroneous errors will be removed from editors. Example 12 “Errors for get_dept_rec” shows the same editor and file as Example 11 “Example of errors and warnings shown for SQL statements” does, but after restarting Eclipse.
Example 12 Errors for get_dept_rec Example 13 “Errors for get_dept_rec removed” shows the same editor and file as Example 12 “Errors for get_dept_rec”, but after get_dept_rec has been added to .sqlmxStatements.txt. The editor still shows errors and warnings which the next two sections will show how to remove.
Example 13 Errors for get_dept_rec removed TIP: You can view the #define macros loaded by CDT by opening the Paths and Symbols project property page and selecting the Symbols tab, as shown in Figure 53 (page 96).
Figure 53 Symbols tab of the Path and Symbols property page Disabling specific code analysis errors and warnings You can selectively disable code analysis errors and warnings using project properties for code analysis. For example, Example 13 “Errors for get_dept_rec removed” in the previous section shows a C/C++ editor that marks SQL record fields as errors, as the code analyzer does not have definitions of those fields. To disable that type of error: 1.
Figure 54 Disabling record field errors Disabling erroneous syntax warnings When the C/C++ indexer shows erroneous syntax warnings (as shown in Example 13 “Errors for get_dept_rec removed”, you will not be able to disable the warnings using the Code Analysis property page as shown in the previous section. You have the option of disabling these warnings altogether or making them less obtrusive.
Figure 55 C/C++ Index Markers annotation preferences 4. 98 Tasks Deselect one or all of the check boxes for Vertical ruler, Overview ruler, and Text as. Figure 56 (page 99) shows the same editor and file shown in Example 13 “Errors for get_dept_rec removed” with the result of deselecting Text as but keeping the less obtrusive markers in the vertical and overview rulers so that legitimate syntax errors can still be detected.
Figure 56 Syntax warnings after “Text as” deselected 5. Select OK to apply your changes and dismiss the Preferences dialog. Specifying locations for C/C++ headers, COBOL COPY libraries, and pTAL source files For managed builds, NSDEE provides an Includes settings category for all cross compiler tools and SQL/MX preprocessor tools.
7. 8. Select OK to add the path. Figure 57 (page 100) shows the Includes page after adding a relative path. Select OK to apply the setting and close the Properties dialog. Figure 57 Includes settings page Instructing NSDEE not to build source files By default, managed builds build source files in a given project. You can exclude one or more source files from being built using source file properties.
Figure 58 Exclude a single COPY library from a build 5. Select OK to apply the change and dismiss the Properties dialog. The file excluded from the build is shown with a pin through it, as a reminder in Figure 59 (page 101): Figure 59 File excluded from build (pin indicator) Excluding all sources in a folder To exclude a folder containing only COBOL COPY libraries from a build, perform the following steps from the NonStop Development perspective: 1. Select the folder in the NonStop Project Explorer view.
Figure 60 Exclude a folder from a build 5. Select OK to apply the change and dismiss the Properties dialog. The folder that will be excluded from the build is shown with a tack in it following. (The tack indicates only that the folder has non-default properties set on it.
Figure 62 Specifying locations of COPY libraries to include in build (for COBOL compilers) 6. Select OK to apply the change and dismiss the Properties dialog. The file that will not be built with SQL/MP options is shown with a tack in it, as shown in Figure 63 (page 103). (The tack is shown for any file that has non-default settings.
Figure 64 Turn off SQL/MP folder 6. Select OK to apply the change and dismiss the Properties dialog. The folder that will not be built with SQL/MP options is shown with a tack in it, as shown in Figure 65 (page 104). (The tack is shown for any folder that has non-default settings.
4. In the Includes tabbed page of the Paths and Symbols page, select either C or C++ depending on whether the include directory contains C or C++ source. (Select C++ if the include directory contains both.) Figure 66 Paths and Symbols page with C++ selected 5. Select Add... to open the Add directory path dialog: 6. Enter the path of an include directory you want the C/C++ indexer to search. If you enter a project relative path, select the Is a workspace path check box.
Figure 67 Paths and Symbols dialog Changing the system headers indexed when changing build configurations By default, the C/C++ indexer does not regenerate the index when you change build configurations. This is reflected in the path shown for system headers under a project's top-level Includes directory. The index is not regenerated by default because, depending on the size of your code base, regenerating it may take several minutes, particularly when, say, you change from building for TNS/R to TNS/E.
5. Guide.) To change the configuration used by the indexer, select a different build configuration in the combo box in the Build configuration for the indexer group box. Select Apply, then OK, to apply the change and dismiss the Properties page. NOTE: effect.
Linking libraries in managed builds To link an application against libraries, use the normal mechanisms that compilers provide by putting the options in the list of Additional options in the Linker tool's Miscellaneous page. You also need to link against librld.so to enable your application to load dynamic libraries. For example, if your TNS/E C application needs to link against two shared libraries, one named stdll.tso in project StaticDLL and the other named dydll.
use the appropriate build directory, such as Release, that matches the build configuration you selected for the current project using the Configuration combo box.) 10. To add librld.so to the final link, select the Libraries entry under the C Linker (TNS/E) and select the Add button for Libraries (-l) to open the Enter Value dialog. 11. Enter rld in the Enter Value dialog as shown in Figure 72 (page 109).
Adding and customizing build targets You can add build targets to any type of NSDEE project, including projects that use managed builds. You can also customize predefined build targets for managed builds. How to add and customize build targets is described in the following sections: • “Creating a makefile.
1. 2. 3. Close the text editor open on makefile.targets. Select makefile.targets in the NonStop Project Explorer view. Select Open With > Other... from the context menu of the NonStop Project Explorer view to open the Editor Selection dialog: Figure 75 Editor Selection dialog 4. 5. In the Editor Selection dialog, select Makefile Editor. Select OK to dismiss the dialog and open makefile.targets in the Makefile editor. The Makefile editor will now be the default editor for makefile.
Figure 76 Create Make Target dialog 4. Select OK to add the target and dismiss the dialog. Figure 77 (page 112) shows a target named my_target added to the project Car in the Make Target view. Figure 77 Make Target View 5. Double-click the new target to launch a build with that target. For example, if you were to double-click the my_target target shown in the above figure, NSDEE would invoke make my_target.
1. 2. 3. 4. Select the project of interest in the NonStop Project Explorer view. Select Properties from the context menu for the NonStop Project Explorer view to open the Properties page for the selected project. Select C/C++ Build on the left to open the C/C++ Build page on the right of the Properties dialog. Select the Behavior tabbed page and replace clean with clean-all. Figure 78 Changing clean to clean-all 5. Select OK to apply the change and dismiss the Properties dialog.
Figure 79 Example of output form make clean-all Creating custom deploy targets You can create custom deploy targets for both local managed and makefile projects. The advantage of creating custom deploy targets is that, if you use, for example, sftp (an Open SSH program for file transfers available with Cygwin), you can create much more flexible and complex deploy targets.
Figure 80 Changing the default deploy target name 5. 6. 7. Select OK to save your change and close the Properties dialog. Create a top-level file named makefile.targets. (For details, see “Creating a makefile.targets file for managed builds” (page 110)). Add text similar to the following to makefile.targets (Don't forget to use a hard tab before the echo command): custom_deploy: all echo -e "put ./Car.
**** Build Finished **** The custom_deploy target above shows only a few of the many sftp commands available. Additionally, you can issue ssh commands to execute commands on NonStop servers if sftp does not provide all the commands you need. For custom Guardian deploy targets, sftp is not as flexible; however, you can combine both sftp and ssh commands to get the same custom_deploy target behavior. Example 14 “Custom Guardian deploy target” shows an example of a custom_deploy target from Guardian.
2. In the C Element Filters dialog, deselect .*resources. 3. Select OK in the C Element Filters dialog. Using NSDEE with SCM tools: examples and procedures You can use 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.
a. b. 4. Return to Eclipse and select the project you added files or directories to in the NonStop Project Explorer view. Select Refresh from the context menu. NSDEE will detect the new files and directories. When you need to check out changes to a project contributed by someone else: a. Use the SCM tool to update with the change. b. Select Refresh from the context menu of the NonStop Project Explorer view. NSDEE will detect any changed files and update them.
HelloWorld has been added to the repository.) That perspective is particularly useful for viewing file history and for comparing and merging file versions. To see HelloWorld in the SVN Repositories view (in the SVN Repository Exploring perspective): 1. In the SVN Repositories view, select file:///C:/svn-repository 2. Select Refresh from the context menu. 3. Expand file:///C:/svn-repository (if it isn't already expanded). 4. Select the HelloWorld directory under file:///C:/svn-repository. 5.
Creating a linked folder The New folder wizard provides the capability of creating project folders that appear to be under a local project but are actually links outside your workspace. You can use this capability to link to network drives mapped to Samba mount points so you can drag and drop folders and files between NonStop and your Eclipse project. This also allows you to open and edit remote files directly in Eclipse in the same manner you would open and edit local files.
Figure 84 Linked folder contents NOTE: Accessing OSS files via Samba imposes some restrictions on file names. For details, see the Samba on NonStop User Manual. Performance considerations for using Samba with Eclipse Samba is considered a chatty protocol. Though its performance is good in a local intranet, it can be slow over the internet.
6 Reference The NonStop Development perspective is an extension of the C/C++ perspective. This chapter provides reference information about the many ways in which the C/C++ perspective has been extended in NSDEE.
Table 5 NonStop views (continued) View Provider Description makefile.targets file for managed builds” (page 110)), you can add that target to the Make Target view as a named build icon. Then you can initiate a build of that target by double-clicking the named build icon in the Make Target view. CDT provides additional views for showing call hierarchies, type hierarchies, and more. To see all views available to you, select Window→Show View→Other... to open the Show View dialog.
Figure 86 Show View dialog with NonStop Development view NonStop Project Explorer view The NonStop Project Explorer view displays the contents of your projects, whether they are remote or local to Windows. Projects are displayed in a tree structure, where the root node is your project folder, and where your project folder contains additional folders and files which may or may not be in your local workspace.
Icon What it represents... pTAL source file Remote NonStop executable For more information about the C/C++ Project view, see the C/C++ Development User Guide. COBOL and pTAL editors COBOL and pTAL editors are text editors with language-specific syntax highlighting added. These editors provide basic Eclipse editor functionality and can be configured using Eclipse preferences.
Properties view The properties view shows properties for the currently selected item in the NonStop Project Explorer view. For details, see the C/C++ Development User Guide. New project wizards NSDEE provides separate project wizards for local and remote projects, as well as one import wizard that creates local makefile projects from existing source. This section describes each of these wizards. Local new project wizards There are four separate new project wizards for local projects.
Table 7 Project types (continued) Setting Description NonStop User Library Select Empty Project to create a managed project that creates a user library (TNS/R only). NonStop Makefile project Select Empty Project to create a makefile project where you supply the makefile. Basic Settings page The Basic Settings page appears only if you select a hello world executable project on the first wizard page.
Table 8 Initial Build Settings page settings (managed builds) (continued) Setting Description SQL tools: Select the SQL/MX or SQL/MP button if your project sources will include SQL, else select the None button. SQL/MX Preprocessor Locations The combo boxes in this group will only be enabled when you select the SQL/MX button. Use the combo boxes to specify the location of C/C++ and/or COBOL preprocessors.
Table 10 Remote Settings page settings (no SQL) (continued) Setting Description be passed separately to the -h and -u options, respectively. Target destination (-dir): Optional. Remote directory or subvolume where locally built object will be transferred to on the selected NonStop system (passed to -dir option for Deploy tool). Target file name (-r): Optional. File name that will be given to the remote copy of the transferred file (passed to –r option of Deploy tool).
Table 12 Remote Settings page settings (SQL/MP) (continued) Setting Description user can be passed separately to the –Wsqlhost and -Wsqluser options, respectively. Target file name (-Wsqlprog=): Optional. Specifies the file name given to the final build output when it is copied to a NonStop system (passed as argument to –Wsqlprog=). Working subvolume (-Wsqlwork=): Optional. Specifies the working directory to use on the NonStop system (passed as argument to –Wsqlprog=).
Table 14 Remote Makefile page settings Setting Description Project name: Enter name for top-level project folder. Build system: NonStop system where project files reside and where project is built. Project Location: Location of project on NonStop system. Platform: Choose the OSS or Guardian button based on the platform that your project sources reside on. Connect to Build System... Select this button to establish a connection to the system you select from the Build system: combo.
New File from Template The New File from Template wizard is an extension of the New File wizard by CDT which provides a choice of templates (initial file content) to be used when creating a file. NSDEE extends this wizard to work with remote NSDEE projects in addition to local projects. NOTE: This wizard can only create remote Guardian files using the default file type for the remote Guardian project. To create a file from a template for a non-default file type for Guardian, use the New Source File wizard.
New Source Folder The New Source Folder wizard creates a new source directory for projects with managed builds. It is important to use this wizard for projects with managed builds because it automatically precludes issues with nested folders in builds by setting filters for nested source folders. You can view and edit these filters from the Source Location tab of the Paths and Symbols property page. For details, see the C/C++ Development User Guide. NOTE: This wizard does not support remote projects.
where you enter details of where you want files transferred to. The lower Options group box provides various options for file transfer. Table 5 describes the selections you can make in each of the three areas. Table 17 Transfer Files wizard controls Control Description Project and file selection area Directories for project: combo and project directories tree Combo selection sets project shown in the project directory tree. Select a directory to show its files to the right.
Table 18 Import ETK Projects wizard settings Setting Description Solution file: Enter the path to an ETK solution file. Projects: Lists all projects associated with the ETK solution file you enter in the Solution file: field. Deselect any projects you don’t want to import. Copy projects into workspace Copy the files in the ETK projects into your workspace. If your ETK projects are not self-contained, not copying project files may be a better option.
Figure 88 Remote browsing for a Guardian file The Contents of: field at the top of the browser shows the directory, volume, or subvolume whose content (files and folders) is shown in the center of the dialog. You can edit the Contents of: field and select Return or the load contents button ( ) to see the contents of the location you enter.
Figure 89 Default COBOL source template Network Connections The Network Connections preference page provides a central place to configure connections to remote systems. Connections you configure using this page will appear in combo boxes in the form: systemName (userID) in project property pages, launchers, and other dialogs where you need to choose a NonStop system and user ID. Table 20 (page 137) describes the settings in the Network Connections preference page.
Add or Remove Connection Configurations dialog The Add or Remove Connection Configurations dialog lets you add, remove, and copy connection configurations. To open it, select the Add/Remove… button on the Network Connections preference page. Table 21 (page 138) describes the settings in the Add or Remove Connections Configurations dialog.
Table 23 Telnet/FTP settings Setting Description Telnet port: field Enter port NSDEE will use to connect to the Telnet server on the NonStop system. (Default is 23.) FTP port: field Enter port NSDEE will use to connect to FTP server on the NonStop system. (Default is 21.) Active FTP button Select to have NSDEE use active protocol when opening FTP ports. Passive FTP button Select to have NSDEE use passive protocol when opening FTP ports.
Table 25 Add Cross Compiler dialog settings (continued) Setting Description Use the above location as root folder* button Select to add a single RVU. The location specified must have an RVU ID as the name of the last directory in its path. Set the above non-standard location as root folder Select to specify a non-standard directory as the location of an for button RVU. Use the combo box to the right to select H06 or G06. Use the text box to the right of the combo to enter the RVU version number.
Cygwin/Msys Page settings The Cygwin/Msys page lists the bin locations for Cygwin and Mysys. Table 28 (page 141) describes the settings on this page. Table 28 Cygwin/Msys page settings Setting Description Cygwin bin: field Select if tools will be located in a Cygwin bin directory. Enter the path of the Cygwin bin directory. Select Browse... if tools will be located in a different bin. Mysys bin: field Select if tools will be located in a Mysys bin directory. Enter the path of the Mysys bin directory.
This section describes each of the property pages available from the Properties dialog when you select an item in the NonStop Project Explorer and then select Properties from the context menu. Resources The Resource property page shows file system attributes of a selected project, directory, file, or link. For details, see the C/C++ Development User Guide. Builders The Builders property page allows you to make changes to how project builders are run. For details, see the C/C++ Development User Guide.
Tool Settings page The Tool Settings tabbed page lets you configure options passed to compilers, SQL tools, and linkers during builds. The list of tools on the left of the Tool Settings page is determined by the tool chain and tool selections you made when you created your project. (For a description of NSDEE tool chains, see “Tool Chains” (page 51)). The left side of the Tool Settings page shows the tools used to build your project.
you expand a binary object in a project. Typically, you should not need to alter this page. For details, see the C/C++ Development User Guide. Error Parsers The Error Parsers page lets you choose which parsers are run on build output. These parsers look for errors and warnings and, when found, add them to the Problems view along with relevant information about the errors and warnings such as the source locations they are associated with. Typically, you should not need to alter this page.
Tool Chain Editor The Tool Chain Editor property page lists the tools used in managed builds. You can use this page to add tools to your build that were not added at project creation time. For details, see the C/C++ Development User Guide. WARNING! DO NOT select Restore Defaults and apply the change it makes. The "default" tool chain is all tools available for a given platform (TNS/E or TNS/R).
NonStop Tools menu The NonStop Tools menu in the NonStop Development perspective provides a single place where you can open dialogs, wizards, and preferences pages that are specific to NonStop application development. Many items on the NonStop Tools menu can be accessed in other ways. The Configure Tool Locations... menu item is a short cut to opening the Tool Locations preference page. Similarly, the Configure Connections... menu item is a short cut to opening the Network Configurations preference page.
Table 30 NonStop icons (continued) Icon Location Description Tool bar Opens New Source File wizard by default. Its drop-down menu allows selection of either a new source file, new header file, or new file wizard. Tool bar (pull-down) Shown in the new file icon pull-down menu, it opens the New Source File wizard. Tool bar (pull-down) Shown in the new file icon pull-down menu, it opens the New Header File wizard.
7 What's New at NSDEE 3.0? NSDEE 3.0 provides a completely new perspective called the NonStop Development perspective. It is a complete replacement for the NonStop perspective available at NSDEE 2.1. The NonStop perspective is still available at NSDEE 3.0, but it has "(Deprecated)" appended to its name to indicate that it is no longer supported. Why a New Perspective? The new NonStop Development perspective provides many new features, some of which are incompatible with the features available at NSDEE 2.1.
• Rename refactoring — Renames classes, types, methods, functions, and member names, applying the name change to all files in a project or across an entire workspace. • Per-project preferences for C/C++ preferences such as code formatting. All of the above features are described in the C/C++ Development User Guide.
Differing Properties for Compilers and Tools NSDEE 2.1 provided graphical equivalents for setting almost every command line option for cross compilers, linkers, and other tools. NSDEE 3.0 takes a different approach by providing graphical equivalents only for a few common tool options. All other tool options can be added simply by typing them in as they would appear on a command line. The NSDEE 3.0 approach simplifies the property pages and allows you to more easily see all command line settings for a tool.
One additional capability is that you do not have to initiate tool location detection as you did with the Configure Compilers dialog. Initial tool location detection occurs automatically. If you install additional compilers, however, you need to go to the Tool Locations preference page and select the Add button, and select OK in the Add Cross Compiler Location dialog to refresh the list.
8 Support and other resources Supported Release Version Updates (RVUs) This document supports NSDEE 3.0 and all subsequent versions of NSDEE until otherwise indicated in a replacement publication. Intended Audience This document is intended for developers who are using the NonStop Development Environment for Eclipse (NSDEE). New and Changed Information in This Edition This is a new manual. Related Information Refer to “Related documentation” (page 10).
A Tips on setting up password free logins with Open SSH If you install Open SSH with Cygwin, you can use the sftp program to provide more flexible and better performing deploy targets for both managed builds and makefile project builds. For details, see “Creating custom deploy targets ” (page 114). Using sftp in your deploy target, however, requires that you set up passphrase logins for SSH so the deploy target can run sftp in batch mode without having to supply a password.
% alter user swdev.doon, publickey key1 fingerprint f7:7a:7e:4b:e9:39:c4:85:9c:e5:22:e9:a0:75:07:08 % exit If the alter user command complains that it doesn't know your user ID, then you need to use the add user command. Here's an example: % alter user swdev.doon, publickey key1 fingerprint f7:7a:7e:4b:e9:39:c4:85:9c:e5:22:e9:a0:75:07:08 alter user swdev.doon, publickey key1 fingerprint f7:7a:7e:4b:e9:39:c4:85:9c:e5:22:e9:a0:75:07:08 Error, user swdev.doon not found % add user swdev.doon add user swdev.
Figure 91 Using Cygwin Open SSH settings with NSDEE 155
Index Symbols 256-bit encryption enabling for SSH, 68 A Add Cross Compiler, 139 Add SQL/MX Preprocessor, 140 Adding folders and files to projects, 30 B Basic Settings, 127 Binary Parsers page, 143 Binary tabbed page, 142 Browsing files, 135 Build Artifact page, 143 Build directory makefiles written to, 47 Build Settings page, 131 Build Steps page, 143 Build variables specifying, 32 Build Variables property page, 142 Builders property page, 142 Building projects, 33 Builds adding tools to, 145 Managed, 35
Error Parsers page, 144 Error parsers tabbed page, 142 ETK Import ETK Projects wizard, 134 importing projects, 69 Example files for NSDEE, 27 Exporting connection configurations, 68 F replaced, 149 Managed projects viewing and changing properties, 30 Menu NonStop Tools menu, 133 Migrating NSDEE 2.x to NSDEE 3.
Opening method definition from a call site, 29 Outline view in active C/C++ editor, 125 Overview NSDEE, 35 P Pages Basic Settings, 127 Binary Parsers, 143 Build Artifact, 143 Build Settings, 131 Build Steps, 143 Build Variables, 142 Builders property, 142 C/C++ Build property page, 142 Cross Compiler settings, 139 Discovery Options, 142 Environment, 142 Error Parsers, 144 Initial Build Settings, makefile projects, 128 Initial Build Settings, managed builds, 127 Logging, 142 Make Settings, 142 Properties, 1
Cross Compiler page, 139 Cygwin/Msys, 141 Deploy Target Settings group, 144 Import ETK Project wizard, 135 Import NSDEE 2.
