Last edited 6 months ago

Standard SDK directory structure

Applicable for STM32MP13x lines, STM32MP15x lines, STM32MP25x lines


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):
  • cortexa7t2hf-neon-vfpv4
  • cortexa35
<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