Last edited 4 years ago

Standard SDK directory structure

The printable version is no longer supported and may have rendering errors. Please update your browser bookmarks and please use the default browser print function instead.

This article describes the structure of the OpenSTLinux standard SDK installation directory:

SDK
├── environment-setup-<target>-<distro>-linux-gnueabi  Environment setup script
├── site-config-<target>-<distro>-linux-gnueabi        Configuration file for the target
├── sysroots                                           Root file systems
│   ├── <target>-<distro>-linux-gnueabi                Target sysroot (libraries, headers, and symbols)
│   │   ├── bin
│   │   ├── boot
│   │   ├── config
│   │   ├── dev
│   │   ├── etc
│   │   ├── home
│   │   ├── lib
│   │   ├── media
│   │   ├── mnt
│   │   ├── proc
│   │   ├── run
│   │   ├── sbin
│   │   ├── sys
│   │   ├── tmp
│   │   ├── usr
│   │   └── var
│   └── <host machine>-<distro>_sdk-linux              Native sysroot (libraries, headers, and symbols)
│       ├── bin
│       ├── environment-setup.d
│       ├── etc
│       ├── lib
│       ├── sbin
│       ├── usr
│       └── var
└── version-<target>-<distro>-linux-gnueabi            Version file for the target

Where:

<target> Target architecture for cross-toolchain; examples (non exhaustive list):
  • cortexa7hf-neon-vfpv4
<distro> Distribution; examples (non-exhaustive list):
  • openstlinux_weston
<host machine> Host machine on which the SDK is installed; examples (non-exhaustive list):
  • x86_64 (64-bit host machine)

The installed SDK consists of:

  • an environment setup script for the SDK
  • a configuration file for the target
  • a version file for the target
  • the root file systems (sysroots) needed to develop objects for the target system