summaryrefslogtreecommitdiff
path: root/README
blob: d4cdc2533a1fcca57374a05db360bbcaf0b77289 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
Toradex oe-core Setup
=====================

To simplify installation we provide a repo manifest which manages the different git repositories 
and the used versions. (more on repo: http://code.google.com/p/git-repo/ )

Install the repo bootstrap binary:

  mkdir ~/bin
  PATH=~/bin:$PATH
  curl http://commondatastorage.googleapis.com/git-repo-downloads/repo > ~/bin/repo
  chmod a+x ~/bin/repo

Create a directory for your oe-core setup to live in and clone the meta information.

  mkdir oe-core
  cd oe-core
  repo init -u http://git.toradex.com/toradex-bsp-platform.git -b master
  repo sync

Optionally create a development branch in all git repositories

  repo start mybranch --all

Source the file export to setup the environment. On first invocation this also copies a sample 
configuration to build/conf/*.conf.

  . export

Adapt build/conf/local.conf to your needs. At least check the variables BB_NUMBER_THREADS, 
PARALLEL_MAKE, and MACHINE. Set MACHINE to a preferred value and when you need a different 
one override it from the command line.

For Toradex modules the following machines exist:

  apalis-t30
  colibri-t20
  colibri-t30
  colibri-vf50

e.g. set in local.conf

  MACHINE ?= "colibri-t30"

and then if you want to build for Apalis T30 instead, use the following command line:

  MACHINE=apalis-t30 bitbake angstrom-lxde-image

More information on our developer website:

  http://developer.toradex.com/software-resources/arm-family/linux/board-support-package/openembedded-(core)

For Toradex use:
To generate a manifest from what is currently checked out:
repo manifest -r -o manifest.xml