diff options
| author | Adrian Dudau <adrian.dudau@enea.com> | 2016-03-30 16:45:16 +0200 |
|---|---|---|
| committer | Adrian Dudau <adrian.dudau@enea.com> | 2016-03-30 16:46:02 +0200 |
| commit | b9ca1a2a5f1dd0a19d9acef95621e5ae902a8b4f (patch) | |
| tree | 49bae198a746ad08c1ce3a562c89fc0e80788d74 /README | |
| download | meta-enea-networking-b9ca1a2a5f1dd0a19d9acef95621e5ae902a8b4f.tar.gz | |
initial commit
Create layer
Signed-off-by: Adrian Dudau <adrian.dudau@enea.com>
Diffstat (limited to 'README')
| -rw-r--r-- | README | 62 |
1 files changed, 62 insertions, 0 deletions
| @@ -0,0 +1,62 @@ | |||
| 1 | meta-enea-networking | ||
| 2 | =================================================================== | ||
| 3 | |||
| 4 | This layer is contains Enea customizations for the Networking profile. | ||
| 5 | |||
| 6 | Dependencies | ||
| 7 | ============ | ||
| 8 | |||
| 9 | This layer depends on: | ||
| 10 | |||
| 11 | URI: git://git.enea.com/linux/meta-enea-base | ||
| 12 | branch: master | ||
| 13 | revision: HEAD | ||
| 14 | |||
| 15 | URI: git://git.yoctoproject.org/meta-fsl-ppc | ||
| 16 | branch: master | ||
| 17 | revision: HEAD | ||
| 18 | |||
| 19 | Source code | ||
| 20 | =========== | ||
| 21 | |||
| 22 | git://git.enea.com/linux/meta-enea-networking.git | ||
| 23 | |||
| 24 | |||
| 25 | Patches | ||
| 26 | ======= | ||
| 27 | |||
| 28 | Please submit any patches against the enea-networking layer to the | ||
| 29 | linux-maintainers mailing list: linux-maintainers@enea.com | ||
| 30 | |||
| 31 | Maintainers: Enea Linux Team <linux-maintainers@enea.com> | ||
| 32 | |||
| 33 | |||
| 34 | Table | ||
| 35 | ================= | ||
| 36 | |||
| 37 | I. Adding the enea-networking layer to your build | ||
| 38 | II. Misc | ||
| 39 | |||
| 40 | |||
| 41 | I. Adding the enea-networking layer to your build | ||
| 42 | ================================================= | ||
| 43 | |||
| 44 | In order to use this layer, you need to make the build system aware of | ||
| 45 | it. | ||
| 46 | |||
| 47 | Assuming the enea-networking layer exists at the top-level of your | ||
| 48 | yocto build tree, you can add it to the build system by adding the | ||
| 49 | location of the enea-networking layer to bblayers.conf, along with any | ||
| 50 | other layers needed. e.g.: | ||
| 51 | |||
| 52 | |||
| 53 | BBLAYERS ?= " \ | ||
| 54 | /path/to/yocto/meta \ | ||
| 55 | /path/to/yocto/meta-poky \ | ||
| 56 | /path/to/yocto/meta-enea-base \ | ||
| 57 | /path/to/yocto/meta-fsl-ppc \ | ||
| 58 | /path/to/yocto/meta-enea-networking \ | ||
| 59 | " | ||
| 60 | |||
| 61 | II. Misc | ||
| 62 | ======== | ||
