%poky; ] >

This chapter is going to cover details about the installed SDK and perhaps stuff on locating it (e.g. the naming scheme used to identify the .sh installation script. The idea here is to gather all the current information in the regular YP doc set that describes how to locate, download, or build out the SDK. One thing that needs discussed is any differences between getting the standard SDK as compared to the extended SDK. Do we have pre-build extensible SDKs laying around? Where do we get any pre-built SDKs from? Show the methods by which the user builds out the SDK?

The following figure shows the resulting directory structure after you install the Standard SDK by running the .sh SDK installation script: The installed SDK consists of an environment setup script for the SDK, a configuration file for the target, a version file for the target, and the root filesystem (sysroots) needed to develop objects for the target system. Within the figure, italicized text is used to indicate replaceable portions of the file or directory name. For example, install_dir/version is the directory where the SDK is installed. By default, this directory is /opt/poky/. And, version represents the specific snapshot of the SDK (e.g. &DISTRO;+snapshot). Furthermore, target represents the target architecture (e.g. i586) and host represents the development system's architecture (e.g. x86_64). Thus, the complete names of the two directories within the sysroots could be i586-poky-linux and x86_64-pokysdk-linux for the target and host, respectively.