4. Create SDK

If you have speed in mind, it is possible to install the SDK on a native Ubuntu machine (other Linux distributions may support this SDK with minor changes but won’t be supported). This chapter will guide you on how to clone the entire SDK, to setup the SDK for one board or just OpenEmbedded/Yocto for Pengwyn board.

4.1. Installation

Architech’s Yocto based SDK is built on top of Ubuntu 12.04 32bit, hence all the scripts provided are proven to work on such a system.

If you wish to use another distribution/version you might need to change some script option and/or modify the scripts yourself, remember that you won’t get any support in doing so.

4.1.1. Install a clone of the virtual machine inside your native machine

To install the same tools you get inside the virtual machine on your native machine you need to download and run a system wide installation script:

  Host    select
git clone -b dizzy https://github.com/architech-boards/machine_installer.git
cd machine_installer
./machine_install -g -p

where -g option asks the script to install and configure a few graphic customization, while -p option asks the script to install the required packages on the machine. If you want to install the toolchain on a machine not equal to Ubuntu 12.04 32bit then you may want to read the script, install the required packages by hand, and run it without options. You might need to recompile the Qt application used to render the splashscreen.

At the end of the installation process, you will get the same tools installed within the virtual machine, that is, all the tools necessary to work with Architech’s boards.

4.1.2. Install just one board

If you don’t want to install the tools for all the boards, you can install just the subset of tools related to Pengwyn:

  Host    select
git clone -b dizzy https://github.com/architech-boards/pengwyn-splashscreen.git
cd pengwyn-splashscreen
./run_install

This script needs the same tools/packages required by machine_install

4.2. Yocto

If you have launched machine_installer or run_install.sh script, yocto is already installed. The following steps are useful for understood how the sdk works “under the hood”.

4.2.1. Installation with repo

The easiest way to setup and keep all the necessary meta-layers in sync with upstream repositories is achieved by means of Google’s repo tool. The following steps are necessary for a clean installation:

  1. Install repo tool, if you already have it go to step 4
  Host    select
mkdir -p ~/bin
sudo apt-get install curl
curl http://commondatastorage.googleapis.com/git-repo-downloads/repo > ~/bin/repo
chmod a+x ~/bin/repo
  1. Make sure directory ~/bin is included in your PATH variable by printing its content
  Host    select
echo $PATH
  1. If ~/bin directory is not included, add this line to your ~/.bashrc
  Host    select
export PATH="$PATH:${HOME}/bin"
  1. Open a new terminal
  2. Change the current directory to the directory where you want all the meta-layers to be downloaded into
  3. Download the manifest
  Host    select
repo init -u https://github.com/architech-boards/pengwyn-manifest.git -b dizzy -m manifest.xml
  1. Download the repositories
  Host    select
repo sync

By the end of the last step, all the necessary meta-layers should be in place, anyway, you still need to edit your local.conf and bblayers.conf to compile for pengwyn machine and using all the downloaded meta-layers.

4.2.2. Updating with repo

When you want your local repositories to be updated, just:

  1. Open a terminal
  2. Change the current directory to the directory where you ran repo init
  3. Sync your repositories with upstream
  Host    select
repo sync

4.2.3. Install Yocto by yourself

If you really want to download everything by hand, just clone branch dizzy of meta-pengwyn:

  Host    select
git clone -b dizzy https://github.com/architech-boards/meta-pengwyn.git

and have a look at the README file.

To install Eclipse, Qt Creator, cross-toolchain, NFS, TFTP, etc., read Yocto/OpenEmbedded documentation, along with the other tools one.