Книга: Embedded Linux development using Eclipse

NAB Project Properties

While building a native application is an instructive exercise, the real power of WideStudio/MWT and the NAB plug-in is the ability to rebuild the project for an embedded target environment. The target environment is configured and described in the project Properties dialog.

When you select Properties for an NAB project, you’ll find three additional entries in the navigation panel:

• NAB/MWT Platform SDK Environment

• NAB/MWT Project Class Library Settings

• NAB/MWT Project Settings

For now, we’ll take a look at the Project Settings dialog shown in Figure 6.18. There are three tabs. Target Settings has three items. Encoding lets you specify a character encoding if one is not explicitly specified in the program. Application type is one of Normal Application, Class Library, Netscape Plugin, or Console Application.

Figure 6.18: NAB/MWT Project Settings dialog.

The Target drop-down brings up a very extensive list of all the platforms supported by WideStudio/MWT (Figure 6.19). Of course, selecting anything other than Native assumes you have the appropriate cross-development tool chain, and have built the corresponding MWT runtime libraries.

Figure 6.19: NAB/MWT targets.

The Compiler Settings (Figure 6.20) and Linker Settings tabs take the place of the C/C++ Build?Settings dialog for ordinary C/C++ projects. This is because NAB creates its own makefiles. Here is where you would specify a cross compiler for your embedded target. Note also that this is where Debug mode is enabled.

Figure 6.20: NAB project Compiler Settings.

The NAB/MWT Platform SDK Environment settings are an artifact of the original WideStudio IDE and are likely to be deleted in the next major update, according to the NAB project lead. Its functionality has effectively been supplanted by the Project Settings. Incidentally, T-Engine is a popular embedded platform in Japan that grew out of the TRON project.

Оглавление книги