Commit 6ce9b2b1 authored by Vladimir Petrigo's avatar Vladimir Petrigo Committed by David Mondou
Browse files

Clean up text formatting

parent f226332c
......@@ -2,70 +2,76 @@
Rigado Vesta Gateway BSP
------------------------
.. role:: bash(code)
:language: bash
This document assumes the development environment is being built on a clean install of Ubuntu 14.04 and the user is comfortable with using the Linux command line. Complete the following steps from the Linux command line.
To fetch the latest package available in the Ubuntu repositories:
- *sudo apt-get update*
- Update your system: *sudo apt-get upgrade -y*
- :bash:`sudo apt-get update`
- Update your system: :bash:`sudo apt-get upgrade -y`
To install the essential Yocto Project host packages run the following command:
- *sudo apt-get install gawk wget git-core diffstat unzip texinfo gcc-multilib build-essential chrpath socat libsdl1.2-dev*
- :bash:`sudo apt-get install gawk wget git-core diffstat unzip texinfo gcc-multilib build-essential chrpath socat libsdl1.2-dev`
To install the i.MX layers host packages run the following command:
- *sudo apt-get install libsdl1.2-dev xterm sed cvs subversion coreutils texi2html docbook-utils python-pysqlite2 help2man make gcc g++ desktop-file-utils libgl1-mesa-dev libglu1-mesa-dev mercurial autoconf automake groff curl lzop asciidoc u-boot-tools git*
- :bash:`sudo apt-get install libsdl1.2-dev xterm sed cvs subversion coreutils texi2html docbook-utils python-pysqlite2 help2man make gcc g++ desktop-file-utils libgl1-mesa-dev libglu1-mesa-dev mercurial autoconf automake groff curl lzop asciidoc u-boot-tools git`
To install the Node.js host packages run the following command:
- For compiling for 32-bit ARM with x86_64 host you need to enable x86 packages/libraries. For Ubuntu it might be done with the following command: *sudo dpkg --add-architecture i386*
- Update *apt-get* cache: *sudo apt-get update*
- Install Node.js dependencies: *sudo apt-get install g++-multilib libssl-dev:i386 libcrypto++-dev:i386 zlib1g-dev:i386 bluetooth bluez libbluetooth-dev libudev-dev*
- For compiling for 32-bit ARM with x86_64 host you need to enable x86 packages/libraries. For Ubuntu it might be done with the following command: :bash:`sudo dpkg --add-architecture i386`
- Update :bash:`apt-get` cache: :bash:`sudo apt-get update`
- Install Node.js dependencies: :bash:`sudo apt-get install g++-multilib libssl-dev:i386 libcrypto++-dev:i386 zlib1g-dev:i386 bluetooth bluez libbluetooth-dev libudev-dev`
- Previous command also includes necessary libraries and packages to build the Noble package for Node-RED
To install the `repo` utility, run the following commands:
- *mkdir ~/bin*
- *curl http://commondatastorage.googleapis.com/git-repo-downloads/repo > ~/bin/repo*
- *chmod a+x ~/bin/repo*
To install the :bash:`repo` utility, run the following commands:
- :bash:`mkdir ~/bin`
- :bash:`curl http://commondatastorage.googleapis.com/git-repo-downloads/repo > ~/bin/repo`
- :bash:`chmod a+x ~/bin/repo`
Add the following line to the .bashrc file to ensure that the ~/bin folder is in your PATH variable:
- *export PATH=~/bin:$PATH*
Add the following line to the :bash:`.bashrc` file to ensure that the :bash:`~/bin` folder is in your :bash:`PATH` variable:
- :bash:`export PATH=~/bin:$PATH`
Make sure that git is setup properly with the following commands below:
- *git config --global user.name "Your Name"*
- *git config --global user.email "Your Email"*
- *git config –list*
- :bash:`git config --global user.name "Your Name"`
- :bash:`git config --global user.email "Your Email"`
- :bash:`git config –list`
Initialize the repo with the master branch of the repository with the following commands:
- *mkdir vesta-gateway-bsp*
- *cd vesta-gateway-bsp*
- *repo init -u https://git.rigado.com/vesta/board-support-package -b master*
- *repo sync -c -j1*
- :bash:`mkdir vesta-gateway-bsp`
- :bash:`cd vesta-gateway-bsp`
- :bash:`repo init -u https://git.rigado.com/vesta/board-support-package -b master`
- :bash:`repo sync -c -j1`
NOTE: without -j1 repo will appear to lock up when it is actually asking for your user name.
NOTE: without :bash:`-j1` repo will appear to lock up when it is actually asking for your user name.
Set up the environment with the following command substituting MACHINE_TYPE for the correct MACHINE:
- *MACHINE=<MACHINE TYPE> DISTRO=poky source setup-environment build*
Set up the environment with the following command substituting :bash:`MACHINE_TYPE` for the correct :bash:`MACHINE`:
- :bash:`MACHINE=<MACHINE TYPE> DISTRO=poky source setup-environment build`
Below is the list of the different MACHINE types supported:
- vesta-100
- vesta-200
- vesta-300
- :bash:`vesta-100`
- :bash:`vesta-200`
- :bash:`vesta-300`
Example with MACHINE type vesta-300:
- *MACHINE=vesta-300 DISTRO=poky source setup-environment build*
Example with :bash:`MACHINE` type :bash:`vesta-300`:
- :bash:`MACHINE=vesta-300 DISTRO=poky source setup-environment build`
NOTE: This next instruction will take several hours to build.
To start the build run the following command:
- *bitbake vesta-image-developer*
- :bash:`bitbake vesta-image-developer`
At the last step you may meet an issue with wrong locales:
::
.. code:: bash
~/vesta-gateway-bsp/build$ bitbake vesta-image-developer
Please use a locale setting which supports utf-8.
Python can't change the filesystem locale after loading so we need a utf-8 when python starts or things won't work.
To fix that you need to issue commands below:
::
.. code:: bash
sudo locale-gen "en_US.UTF-8"
sudo dpkg-reconfigure locales
export LC_ALL=en_US.UTF-8
......@@ -73,5 +79,3 @@ To fix that you need to issue commands below:
export LANGUAGE=en_US.UTF-8
After a build is complete, the created image will reside in veta-gateway-bsp/build/tmp/deploy/images. Each image build creates a U-Boot, kernel, and rootfs.
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment