Importing a BSP or other QNX source packages

QNX BSPs and other source packages (e.g. DDKs) are distributed as .zip archives. The IDE lets you import these packages into the IDE:

When you import a: The IDE creates a:
QNX BSP source package System Builder project and a C or C++ project
BSP source package from Foundry27 System Builder project (see Importing a BSP package from Foundry27)
QNX C/C++ source package C or C++ application or library project

Step 1: Use File > Import…

You import a QNX source archive using the standard Eclipse import dialog:

Import BSP

The Import wizard.

Note: If you're importing a source package or BSP, select QNX Source Package and BSP.

You can choose to import either a QNX BSP or a source package. Although a BSP is, in fact, a package that contains source code, the two types are structured differently and generate different types of projects. If you try to import a BSP archive as a QNX Source Package, the IDE won't create a System Builder project.

Step 2: Select a method to use for import

Select the method that you want to use to import the package or BSP: from a local file archive, or from a SVN repository on Foundry27.

Select the method used to import the source package

Selecting the method to use to import the source package.

If you select a package archive file, you'll need to specify a name in the File Name field, or click Browse to locate and select a file. After you choose the archive file type, by default the wizard presents you with a list of the packages on your host:

Select BSP

Choosing a package to import.

Notice that as you highlight a package in the list, the IDE shows a description for that package.

If you select a file from a SVN repository on Foundry27, you'll need to select a package:

Select BSP

Choosing a package to import from Foundry27.

To add more packages to the list, click the Select Package. . . button, and then select the .zip source archive you want to add.

Step 3: Select the source projects

Each source package contains several components (or projects, in IDE terms). For the package you selected, the wizard gives you a list of each source project contained in the archive.

You can decide to import only certain parts of the source package; simply uncheck the entries you don't want (they're all selected by default). Again, as you highlight a component, you'll see its description in the bottom pane.

Step 4: Select a working set

The last page of the import wizard lets you name your source projects. You can specify:


To specify settings for the project being created, do the following tasks:


If this is the first time you perform a checkout from Foundry27, the SVN New Repository Wizard is displayed.

Importing from Foundry27 for the first time

You'll need to specify your user ID and password that correspond to your Foundry27 account. In addition, you'll need to be successfully authenticated before you can proceed to the next panel in the wizard.

Click Finish to begin importing the package.

Imported BSP package from Foundry27

The IDE sets up the required project properties (compiler options, build targets, and so on) so that the projects are able to build after the checkout process. In addition, the IDE maintains the source tree layout (to preserve the current status of the checked out source), sets up prebuilt and staging areas for the project, when necessary, and also creates the BSP project.

If you plan to import a BSP into the IDE, remember to give each project a different name.

Note:

If you import dual-endian BSPs, the wizard shows this informational message:

BSP import message

If you add build variants, you need to copy the CPU-specific files to the new variant's build directories.

Step 5: Build

When you finish with the wizard, it creates all the projects and brings in the source from the archive. After the checkout of the source package completes, right-click on the BSP project and select Build; the src project will be auto-built by the BSP project. The IDE will build all of the source under one project. Because the IDE creates a dependency between the BSP project and the src project, you don't need to build the src project; only the BSP project.

Note:

If you answer Yes, the IDE begins the build process, which may take several minutes (depending on how much source you've imported).

Both the source project and the System Builder project build a bootable IFS image.

If you decide not to build now, you can always do a Rebuild All from the main toolbar's Project menu at a later time.

If you didn't import all the components from a BSP package, you can bring in the rest of them by selecting the System Builder project and opening the import wizard (right-click the project, and then select Import…). The IDE detects your selection and then extends the existing BSP (rather than making a new one).

Related concepts
SVN and the IDE
CVS and the IDE
Local history feature
Project files (.project and .cproject)
Using the core Eclipse source control documentation in the IDE
Importing existing source code into the IDE
Using container projects
Exporting projects