The topic describes the components of the SDK and how
they are packaged. Use this information to understand what gets installed
and how to configure the installation for your own specific purposes.
SDK target platforms
The SDK can be installed on different target platforms. The development (build) platforms for cross compilation of Cell Broadband Engine Architecture (CBEA) code are X86 and X86_64 machines. The native development platforms are 64-bit PowerPC® and CBEA-compliant machines. There are essentially only two execution platforms, either CBEA hardware or the Full-System Simulator when available. Note that you can also run the Full-System Simulator on CBEA hardware to assist with debugging. Executables built on any development platform should run on any execution platform using the same operating system.
SDK directories
The SDK installs files into a number of different directories depending on the host platform and file type. This section describes the SDK standards for directories to help you understand where to find the parts of the SDK and how to best use the SDK development environment.
RPMs
The SDK is distributed as a set of Red Hat Package Manager (RPM) files that can be installed on the target platform. The list of available RPMs that can be installed depends on the host Linux® operating system, the target hardware platform, and the options chosen by the user when installing the SDK. The SDK also depends on a number of RPMs provided by the base Linux operating system.
SDK component descriptions
The SDK is divided into components, each of which is at a particular level of development. Some components are prototype code and others have been fully tested and are warranted by IBM® with the appropriate purchased license.
YUM groups
YUM provides the ability to group RPMs together to facilitate installing a number of RPMs simultaneously and for categorization in the Pirut GUI.
RPMs by component
This topic provides information about the list of RPMs for each component of the SDK.