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.
The SDK RPMs follow typical RPM naming conventions including
version and revision, and standard name suffixes such as
devel for
development code and
debuginfo for GDB debugging data. The SDK includes
additional conventions that make is easier to identify what the RPM is used
for. The following table details these conventions:
Table 1. RPM naming
conventions| Convention |
Explanation |
|---|
| RPM version number |
For IBM-owned code the version number is always 3.0
or 3.0.0 to reflect this version of the SDK. |
| -source suffix |
The RPM contains source code, typically used for examples
built using the SDK rather than rpmbuild which uses a SRPM
(src.rpm). |
| -cross-devel suffix |
The RPM contains development code for a cross-build
environment (X86 or X86_64) rather than a native one. |
| -trace suffix |
The RPM contains libraries that have been enabled for
the IBM® Performance
and Debugging Tool (PDT). |
| -hybrid suffix |
The RPM contains libraries that are used in a hybrid
runtime environment where the host is an X86_64 platform and the accelerator
is a CBEA platform. |
| cell- prefix |
The RPM is oriented for CBEA platforms and can be used
to differentiate the RPM from a standard implementation. |
| ppu- prefix |
The RPM contains a PPU-only library. |
| spu- preifx |
The RPM contains a SPU-only library. |
The SDK RPMs also use a number of different RPM targets. They
are listed in the following table:
Table 2. SDK target platforms| Architecture/Platform |
Explanation |
|---|
| PPC, PPC64 |
A CBEA application can be either 32-bit or 64-bit. Regular PowerPC® platforms
are treated as native for CBEA code only for development. Execution of this
code still needs either a CBEA -compliant hardware platform or the Full-System
Simulator. |
| i386, i686 (X86) |
This is native code that executes on a 32-bit X86 platform. |
| X86_64 |
This native code only executes on a 64-bit X86 platform
and is used for the hybrid programming model. |
| noarch |
noarch is generally used to indicate an architecture-neutral
RPM. For the SDK, noarch has the additional meaning that the RPM contains
PPC or PPC64 target code that is to be installed on an X86 or X86_64 system
for cross compilation. The noarch target is used so that the file will install
without complaints from RPM or YUM. |
| src |
The source code for some SDK components are available
as SRPMs (src.rpm). |