meta-digi/meta-digi-dey
Tatiana Leon 7d2a07cf2f dey-image: create an sdk/toolchain dey version file with params to identify it
This commit creates a new file called 'dey-version-${REAL_MULTIMACH_TARGET_SYS}'
(for example, 'dey-version-cortexa7hf-neon-dey-linux-gnueabi') at the same level
as 'version-${REAL_MULTIMACH_TARGET_SYS}',
'site-config-${REAL_MULTIMACH_TARGET_SYS}', and
'environment-setup-${REAL_MULTIMACH_TARGET_SYS}' files.

The file contains the following parameters:
   * Machine. The name of the platform the toolchain was built for (ccimx6sbc,
     ccimx6ulsbc, ccimx6ulstarter).
   * Version: A versioning system for the generated toolchains. Currently is the
     distro version followed by the timestamp on which the current build started.
   * Image: The name of the image that triggered the population of the SDK
     (core-image-base, dey-image-aws, dey-image-qt-${GRAPHICAL_BACKEND})

The purpose of the 'dey-version-*' file is to be parsed by Eclipse so toolchains
can be autodetected.

This file is packaged with the rest of SDK/toolchain resources ('version-*',
'site-config-*', and 'environment-setup-*' files, and 'sysroots' directory)
when creating the SDK tarball and later the installation script.

The 'dey-version-*' file could also be created in a 'meta-environment.bbappend'
appending to the 'create_sdk_files()'. But from this recipe there is no access
to the name of the image that triggers the creation of the SDK (core-image-base,
dey-image-aws, dey-image-qt, etc.).

Currently, we are redefining 'SDK_POSTPROCESS_COMMAND' (from
'poky/meta/classes/populate_sdk_base.bbclass') to insert the generation of the
'dey-version-*' file just before creating the SDK tarball.

https://jira.digi.com/browse/DEL-5074

Signed-off-by: Tatiana Leon <tatiana.leon@digi.com>
2017-10-03 15:18:52 +02:00
..
classes dey-image: create an sdk/toolchain dey version file with params to identify it 2017-10-03 15:18:52 +02:00
conf libsoc: add generic recipe to build from GIT 2017-09-05 14:18:26 +02:00
custom-licenses custom-licenses: atmel: add copyright 2017-07-06 10:49:06 +02:00
recipes-aws greengrass: add support to preconfigure the package 2017-07-05 13:43:28 +02:00
recipes-connectivity networkmanager: enable the use of 'dnsmasq' server 2017-09-27 13:31:16 +02:00
recipes-core meta-digi-dey: add libdigiapix package 2017-09-06 11:01:26 +02:00
recipes-digi libdigiapix: add Digi APIX library recipe 2017-09-06 11:01:26 +02:00
recipes-graphics packagegroup-dey-qt: rework default installed packages 2017-08-10 11:33:46 +02:00
recipes-multimedia pulseaudio: disable memfd for CC6 2017-04-27 16:59:57 +02:00
recipes-qt qtsmarthome: move desktop launcher from qt5-demo-extrafiles recipe 2017-08-10 11:32:44 +02:00
recipes-sato packagegroup-core-x11-sato: fix gst-player package name 2017-03-01 15:32:11 +01:00
recipes-support dnsmasq: configure package to be used by NetworkManager 2017-09-27 13:31:16 +02:00
DIGI_EULA DIGI_EULA: Update Digi EULA file. 2017-08-29 12:23:22 +02:00
DIGI_OPEN_EULA meta-digi: Rename from DEL to DEY. 2013-06-12 13:18:37 +02:00
README meta-digi: change Freescale references to NXP 2017-03-22 19:58:32 +01:00

README

OpenEmbedded/Yocto Digi Embedded Linux layer
============================================

This layer provides the Digi Embedded Linux distribution images.

This layer depends on:

git://git.yoctoproject.org/poky.git
git://git.openembedded.org/meta-openembedded.git
git://git.yoctoproject.org/meta-freescale.git
git://github.com/Freescale/meta-fsl-demos.git

Digi's license agreements
-------------------------

All software is covered by Digi's general EULA and Digi's Open Source
EULA. To have the right to use the software in your images you need to
read and accept both EULAs at the DIGI_EULA and DIGI_OPEN_EULA files.

NXP Semiconductors' software license agreement
----------------------------------------------

Some platforms depends on libraries and packages that are covered by
NXP Semiconductors' EULA. To have the right to use those binaries in
your images you need to read and accept the EULA file in meta-freescale
Yocto layer.

Support
-------

This layer is provided 'as is' with no guarantee. However, some support
may be available from support@digi.com