Difference between revisions of "IoTGateway/BSP/Linux/Quark/Getting BSP from GitHub"
From ESS-WIKI
| Line 9: | Line 9: | ||
:<span style="color:purple">'''${INTEL_BSP_VER}'''</span> : the Intel Quark BSP version | :<span style="color:purple">'''${INTEL_BSP_VER}'''</span> : the Intel Quark BSP version | ||
| − | ::e.g. v1.2. | + | ::e.g. v1.2.0 |
:<span style="color:purple">'''${BSP_HOME}'''</span> : the home directory the BSP located to | :<span style="color:purple">'''${BSP_HOME}'''</span> : the home directory the BSP located to | ||
Revision as of 20:21, 23 January 2017
Contents
Getting Started
Conventions
- ${INTEL_BSP_VER} : the Intel Quark BSP version
- e.g. v1.2.0
- ${BSP_HOME} : the home directory the BSP located to
- e.g. ~/adv-quark-bsp/meta-clanton_${INTEL_BSP_VER}
Supported version
Fetching the BSP
- Please refer to this to setup repo first
$ 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.