Launch the executable, select a workspace directory to hold your projects, and close the intro screen.The Eclipse main window will appear, as shown in Figure 5.1 below.
The path to this folder will be referred to as $ECLIPSE. In this case, you'll have to install CDT separately.ĭecompress the Eclipse archive and you'll find a folder containing the Eclipse executable. Scroll down to find the required version and download it to your computer. If the IDE requires an older version than the one listed, go to / eclipse/downloads/index.php. This comes with the CDT already installed. If the Cell IDE accepts the latest version, download the Eclipse offering called Eclipse for C/C++ Developers. To download Eclipse, go to page presents the most recent version of Eclipse, but this might not be the version required by the Cell IDE.To be sure, check the IDE documentation that comes with the SDK. The Cell IDE plug-ins customize Eclipse to build applications specifically for the Cell processor.
Eclipse consists of a small executable that draws its capabilities from code modules called plug-ins. Eclipse was originally conceived as an IDE for Java alone, but its language support has extended to C/C++, PHP, Python, Fortran, Cobol, and even Ada. But first, you need to install Eclipse and the C/C++ Development Tooling (CDT).This part in this series begins by explaining how this is done. It's not a separate application, but consists of plug-ins that augment an Eclipse installation.These plug-ins make it possible to create Cell-specific projects that can be built, debugged, and simulated with the SDK's tools.This discussion covers each of these tools and how to execute them through the Cell IDE. The Cell IDE is provided as one of the packages in IBM's SDK. Further, the operating system must have a suitable Java Runtime Environment (JRE) installed.The GNU port for Java, GCJ, isn't sufficient. The Cell's PPU isn't up to the task of rendering the GUI, so I recommend running the IDE on a general-purpose processor. It's possible to run the IDE on a Cell system, but the IDE is Java based and resource hungry. This last part in the series covers much of the same territory, but with a single graphical tool: the Cell SDK's integrated development environment, or the Cell IDE.Īt the time of the completion of the book, the Cell IDE runs only on Linux. In each case, the usage examples involve the command line: statements, flags, and scripts. Part 1, Part 2, Part 3 and Part 4 in this series have presented the Cell SDK's tools for building, debugging, and simulating applications.
0 kommentar(er)
