Specifications

1. Start the Nios II SBT for Eclipse.
2. On the File menu, click Import. The Import dialog box appears.
3. Expand the Nios II Software Build Tools Project folder, and select Import Nios II Software Build
Tools Project.
4. Click Next. The File Import wizard appears.
5. Click Browse and locate the directory containing the C/C++ application project to import.
6. Click OK. The wizard fills in the project path.
7. Specify the project name in the Project name box.
Note: You might see a warning saying "There is already a .project file at: <path>". This warning
indicates that the directory already contains an Eclipse project. Either it is an Eclipse project, or
it is a command-line project that is already imported into Eclipse. If the project is already in
your workspace, do not re-import it.
8. Click Finish. The wizard imports the application project.
After you complete these steps, the Nios II SBT for Eclipse can build, debug, and run the complete
program, including the BSP and any libraries. The Nios II SBT for Eclipse builds the project using the
SBT makefiles in your imported C/C++ application project. Eclipse displays and steps through applica‐
tion source code exactly as if the project were created in the Nios II SBT for Eclipse. However, Eclipse
does not have direct information about where BSP or user library code resides. If you need to view,
debug or step through BSP or user library source code, you need to import the BSP or user library.
Related Information
Import a Supporting Project on page 2-24
For more information about the process of importing supporting projects, such as BSPs and libraries.
Importing a Project with Absolute Source Paths
If your project uses an absolute path to refer to a source file, the SBT for Eclipse imports that source file as
a linked resource. In this case, the import wizard provides a page where you can manage how Eclipse
refers to the source: as a file, or through a parent directory.
Related Information
Absolute Source Paths and Linked Resources on page 2-13
For more information about managing linked resources.
Import a Supporting Project
While debugging a C/C++ application, you might need to view, debug or step through source code in a
supporting project, such as a BSP or user library. To make supporting project source code visible in the
Eclipse debug perspective, you need to import the supporting project.
If you do not need BSP or user library source code visible in the debugger, you can skip this task, and
proceed to debug your project exactly as if you had created it in Eclipse.
If you have several C/C++ applications based on one BSP or user library, import the BSP or user library
once, and then import each application that is based on the BSP or user library. Each application's
makefile contains the information needed to find and build any associated BSP or libraries.
Related Information
Import a Command-Line C/C++ Application on page 2-23
For more information about the steps for importing a supporting project.
2-24
Importing a Project with Absolute Source Paths
NII5V2
2015.05.14
Altera Corporation
Getting Started with the Graphical User Interface
Send Feedback