Importing existing source files into Nsight, Eclipse Edition

Using the CVS Repository Exploring perspective, you can check out modules or directories into existing projects, or create new projects. A common scenario that you may encounter when starting to use Nsight, is determining how to bring existing source files into workspace. There are a number of ways to do this. The scenarios described below are recommended approaches.

Creating a project from source files in CVS

If your existing source tree is managed in CVS, you can use the CVS Repository perspective to "Checkout As..." any folder in the repository. The first time you "Checkout As...", the New Project wizard launches and you need to create a C or C++ project for the folder. For more information, see Creating a project, Creating a project via a project template and Working with project files.

After you perform a checkout operation, a CVS checkout of the project occurs into the project's location. It is recommended that you eventually add and commit the CDT project files back into CVS. These files include .project, .cdtproject, and .cdtbuild (for Managed Build projects) and are located at the root folder of each project.

Bringing code into the IDE from CVS differs slightly, depending on what you're importing:

• an existing project
• existing code that isn't part of a project
• existing code that needs to be added to an existing project

Importing an existing project from CVS

To check out an existing project from the CVS repository into your workspace, right-click the project in the CVS Repositories view, and select Check Out from the menu. A project with the same name as the CVS module is checked out in to your workspace.

Importing source code from CVS

To check out existing source code that is not part of a project:

1. Right-click the module or directory in the CVS Repositories view and choose Check Out As... from the menu.

   The Check Out As wizard displays.

2. Choose how to check out this project:
   • as a project configured using the New Project wizard

     or:

   • as a new project in the workspace

     or:

   • as a Standard Make C/C++ Project - if you need to create your own Makefile to integrate with an existing build process

   Choose the workspace location for this project, then the CVS tag to check out.

3. Click Finish to exit the Check Out As dialog.

4. Click Next to continue.

Importing source code into an existing project

To import a directory full of C/C++ code into an existing project:

1. Right-click the module or directory in the CVS Repositories view and choose Check Out As from the menu.

   The IDE displays the Check Out As dialog.

2. Choose Check out into an existing project, and then click Next. The IDE displays the Check Out Into dialog:
3. Select an existing project from the list, and then click Finish to add the code from CVS to the selected project.

Creating new projects from existing source roots

1. Identify a "root folder" of your source code tree.
2. Create a new C/C++ project using the New Project Wizard, and specify the "root folder" as a non-default location of the new project.

Typically, existing projects will have their own makefiles, so you should create a new Make C/C++ project. For more information see Creating a project and Working with project files.

To help you to identify a root folder for your project, consider the following guidelines:

• all source code for the project is available on or beneath the root folder
• the build results are also produced in or beneath the root folder
• there is often a makefile in the root folder. In complex projects, the makefile in the root folder calls other makefiles in other directories to produce the build results.
• external header files and library files do not need to be in or beneath the root folder.

The resources for the project are maintained in the remote location specified, not in the workspace folder for Eclipse. However, your existing folder structure is displayed in the C/C++ Projects view. Meta data for the project, such as the index for the project and the link to the existing source, is stored in the metadata directory in the workspace folder. For more information on the workspace folder, see Workbench User Guide > Tasks > Upgrading Eclipse.

Import your C/C++ source file system

Another approach would be to create a C/C++ Project and then import your existing file system. For more information about importing, see Workbench User Guide > Tasks > Importing > Importing resources from the file system.

This approach copies the files from your file system to an Eclipse Workbench project or folder. Your original source files remain unchanged and it is the copies of the files that will be edited, built and debugged using Nsight.  When you have successfully imported your existing file system, the folder structure is displayed in the C/C++ Projects view. Again, you should identify an appropriate "root folder" to import from.

Tip:

• Importing your existing file system can consume significant disk space depending on the size of your files.
• Your files may become detached from an existing source control system that previously referenced the original file location such as a ClearCase view.

Overview
 Projects

Working with project files

Project properties