Difference between revisions of "IoTGateway/BSP/Linux/Quark/Getting BSP from GitHub"
From ESS-WIKI
| Line 23: | Line 23: | ||
$ cd ~/adv-quark-bsp | $ cd ~/adv-quark-bsp | ||
$ repo init -u https://github.com/ADVANTECH-Corp/adv-quark-bsp -m ${INTEL_BSP_VER}.xml | $ repo init -u https://github.com/ADVANTECH-Corp/adv-quark-bsp -m ${INTEL_BSP_VER}.xml | ||
| + | $ repo sync | ||
$ cd meta-clanton_${INTEL_BSP_VER} | $ cd meta-clanton_${INTEL_BSP_VER} | ||
</syntaxhighlight></div> | </syntaxhighlight></div> | ||
Revision as of 03:43, 24 November 2016
Contents
Getting Started
Conventions
- ${INTEL_BSP_VER} : the Intel Quark BSP version
- e.g. v1.2.1.1
- ${BSP_HOME} : the home directory the BSP located to
- e.g. ~/adv-quark-bsp/meta-clanton_${INTEL_BSP_VER}
Supported version
Fetching the BSP
$ mkdir ~/adv-quark-bsp
$ cd ~/adv-quark-bsp
$ repo init -u https://github.com/ADVANTECH-Corp/adv-quark-bsp -m ${INTEL_BSP_VER}.xml
$ repo sync
$ cd meta-clanton_${INTEL_BSP_VER}
Prebuilt image pack
- There is no prebuilt image pack in the BSP fetched from GitHub, so creating all image files from the ground up.
setup.sh
- There is no setup.sh in the BSP fetched from GitHub, so there is no need to run setup.sh while creating one new build environment.