No description, website, or topics provided.
Clone or download
mythi Merge pull request #336 from kraj/master
openblas: Upgrade to 0.2.20 and fix cross builds
Latest commit 299136d Apr 5, 2018
Failed to load latest commit information.
bitbake @ be393f2 Refkit CI: pull in the latest changes Oct 28, 2017
doc hardware.rst: drop Intel 570x Nov 13, 2017
docker CI adjust tar options to exclude correctly Sep 16, 2017
iot-web-layers @ 5338355 iot-web-layers: updated to latest HEAD. Sep 4, 2017
meta-clang @ 2c16196 Refkit CI: pull in the latest changes Oct 9, 2017
meta-flatpak meta-flatpak: update ostree to the latest tagged v2017.13. Nov 22, 2017
meta-intel @ c811c0b Pull meta-intel and update distro conf accordingly Dec 1, 2017
meta-intel-realsense @ 50c6863 refkit: update meta-intel-realsense Nov 27, 2017
meta-iotqa meta-iotqa: add qa basic tests for mraa-i2c Aug 22, 2017
meta-measured @ 5f88a6d refkit: tpm2.0-tools from meta-measured Dec 4, 2017
meta-oic @ 0006fbd refkit: upstream component update Jul 21, 2017
meta-openembedded @ 5d6d21e intel-iot-refkit: move to use mraa and upm from meta-oe Oct 27, 2017
meta-refkit-computervision intel-iot-refkit: pull in latest changes Aug 31, 2017
meta-refkit-core refkit: support whole-disk encryption with TPM 2.0 Dec 5, 2017
meta-refkit-extra openblas: Upgrade to 0.2.20 and fix cross builds Apr 1, 2018
meta-refkit-gateway intel-iot-refkit: move to use mraa and upm from meta-oe Oct 27, 2017
meta-refkit-industrial buildtools-tarball: add dependency on python3-lxml Sep 26, 2017
meta-refkit Merge pull request #326 from pohly/tpm2 Dec 5, 2017
meta-ros @ 198a68d meta-ros: pull in latest master branch Nov 16, 2017
meta-security @ de48d57 Refkit CI: pull in the latest changes Oct 28, 2017
meta-security-isafw @ 489abdc meta-security-isafw: update to latest HEAD. Jun 15, 2017
meta-yocto @ 2d8a572 Refkit CI: pull in the latest changes Oct 28, 2017
openembedded-core @ 3b413a8 Refkit CI: pull in the latest changes Oct 28, 2017
.gitignore .gitignore: move to top level of git repo May 23, 2017
.gitmodules refkit: tpm2.0-tools from meta-measured Dec 4, 2017
Jenkinsfile CI and local-build: enable build on openSUSE 42.3 Docker base Sep 1, 2017
LICENSE intel-iot-refkit: initial commit Feb 3, 2017
README.rst README: delete misspelled hyperlink tag Aug 1, 2017
oe-init-build-env refkit-init-build-env: rename to oe-init-build-env May 12, 2017
refkit-init-build-env refkit-init-build-env: rename to oe-init-build-env May 12, 2017



This README file contains information on setting up, building, and booting the IoT Reference OS Kit for Intel(r) Architecture project.

Only Linux development hosts are currently supported, as documented in the Yocto Project Quick Start Guide

Follow the instructions in this document when trying to get familiar with the IoT Reference OS Kit or when basing a new project on it. Alternatively, it is also possible to take a subset of the content and add it to other, existing projects or distributions. For information about the content, see :file:`doc/introduction.rst`.

Installing Docker on Linux

We recommend you build projects in a Docker container. Using Docker provides a packaged and controlled environment for building an image and can eliminate development environment issues that can occur with differing Linux OS distros and versions, different host compilers, and such. (We also describe building without docker in the instructions below.)

Instructions for installing Docker for common Linux distros on your development machine (including Fedora and Ubuntu) are available at:

Follow the instructions for your particular distro. You should also perform some of listed Optional Docker Configuration settings:

Building with Docker

These instructions assume you’ll be working with the sources in a ~/work/intel-iot-refkit directory that you’ll be creating.

Start by cloning the GitHub repos. If you have a previous copy of this repository without all the submodules, it would be best to remove all the content of workspace directory and clone it again:

$ export WORKSPACE=$HOME/work/intel-iot-refkit
$ mkdir -p $HOME/work
$ cd $HOME/work
$ git clone --recursive

When Docker is configured properly and all project code is cloned and available locally, it's time to trigger a build. To do this run the command from within the ~/work/intel-iot-refkit directory:

Build all pre-configured target images with test suites:

$ docker/

Specify one or more target image(s):

$ docker/ refkit-image-common

Building without Docker

While not recommended, you can also use Yocto Project bitbake directly. (Any issues you encounter building this way might not be easily reproducible and debuggable by other developers using a different distribution.)

Here are the basic preparation steps:

$ mkdir -p $HOME/work
$ cd $HOME/work
$ git clone --recursive
$ cd intel-iot-refkit
$ source oe-init-build-env

Edit conf/local.conf to select whether to build the production or the development image. More details about the choices in that file.

Basic build steps:

$ bitbake refkit-image-common

Updating Repositories

You may need to pull new content from the GitHub repo as it’s updated. Use the following commands:

$ git pull
$ git submodule update

For more information about Git submodule commands, check this link:

Installing the Images

See detailed instructions in how to install images.

Mailing Lists

The project has a mailing list for all project development related discussions.

The mailing list info/subscription page can be found here

Bug Tracking

The project uses the Yocto Project Bugzilla for feature/enhancement and bug tracking.

If you've found a bug or wish to file an enhancement request, go to Bugzilla and submit the tickets against Yocto Project Subprojects | IoT Reference OS Kit component.

Submitting Patches

The project is open to patches and bug fixes. The patches can be submitted as Github Pull requests in or to the project mailing list.

Please follow the common Yocto Project/OpenEmbedded Core Commit Message Guidelines.