Skip to content
GitLab
Projects
Groups
Snippets
/
Help
Help
Support
Community forum
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in
Toggle navigation
Menu
Open sidebar
vesta
board-support-package
Commits
debf6592
Commit
debf6592
authored
Jun 15, 2017
by
Pete Tucker
Browse files
Merge branch 'node-red' into 'master'
Node red See merge request
!5
parents
28325b47
3b9f532a
Changes
2
Hide whitespace changes
Inline
Side-by-side
README.rst
View file @
debf6592
...
...
@@ -12,6 +12,12 @@ To install the essential Yocto Project host packages run the following command:
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*
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*
- 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*
...
...
@@ -28,7 +34,7 @@ Make sure that git is setup properly with the following commands below:
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
hydrogen
*
- *repo init -u https://git.rigado.com/vesta/board-support-package -b
node-red
*
- *repo sync -c -j1*
NOTE: without -j1 repo will appear to lock up when it is actually asking for your user name.
...
...
default.xml
View file @
debf6592
...
...
@@ -7,6 +7,7 @@
<remote
fetch=
"https://github.com/Freescale"
name=
"freescale"
/>
<remote
fetch=
"https://github.com/openembedded"
name=
"oe"
/>
<remote
fetch=
"https://git.rigado.com/vesta"
name=
"vesta"
/>
<remote
fetch=
"https://github.com/imyller"
name=
"nodejs"
/>
<project
remote=
"yocto"
revision=
"morty"
name=
"poky"
path=
"sources/poky"
/>
<project
remote=
"yocto"
revision=
"morty"
name=
"meta-freescale"
path=
"sources/meta-freescale"
/>
...
...
@@ -18,8 +19,11 @@
<project
remote=
"freescale"
revision=
"morty"
name=
"meta-freescale-distro"
path=
"sources/meta-freescale-distro"
/>
<project
remote=
"freescale"
revision=
"morty"
name=
"Documentation"
path=
"sources/Documentation"
/>
<project
remote=
"vesta"
revision=
"d46a4418e2d708e2ff05f8237d59ca80f8087891"
name=
"meta-vesta"
path=
"sources/meta-vesta"
/>
<project
remote=
"vesta"
revision=
"53febd5ba131a1d5cc01e8c4b79035fb2371ae0f"
name=
"meta-swupdate"
path=
"sources/meta-swupdate"
/>
<project
remote=
"nodejs"
revision=
"morty"
name=
"meta-nodejs"
path=
"sources/meta-nodejs"
/>
<project
remote=
"nodejs"
revision=
"morty"
name=
"meta-nodejs-contrib"
path=
"sources/meta-nodejs-contrib"
/>
<project
remote=
"vesta"
revision=
"master"
name=
"meta-vesta"
path=
"sources/meta-vesta"
/>
<project
remote=
"vesta"
revision=
"master"
name=
"meta-swupdate"
path=
"sources/meta-swupdate"
/>
<project
remote=
"vesta"
revision=
"master"
name=
"bsp-base"
path=
"sources/base"
>
<linkfile
dest=
"setup-environment"
src=
"setup-environment"
/>
</project>
...
...
Write
Preview
Supports
Markdown
0%
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment