CE Workgroup Shared Embedded Linux Distribution Project

Transcription

1 CE Workgroup Shared Embedded Linux Distribution Project Yoshitake Kobayashi CE Workgroup, the Linux Foundation (Toshiba Corporation) Embedded Linux Conference Europe Oct, CE Workgroup, the Linux Foundation

2 Overview Introduction of CE Workgroup Introduction of Shared Embedded Linux Distribution Project 2

3 CE Workgroup Introduction of CE Workgroup The Linux Foundation 3 Copyright 2015, CE Workgroup, the Linux Foundation

4 Role of CEWG CE Workgroup Bridge between OSS (like Linux) developer communities and embedded system industry who wish to collaborate with those communities. Building the relation of trust and co-creation is so essential to realize the value of OSS However it is so difficult achieving such ideal relationship solely by any company because of the diversified, groval and huge scale of the active OSS communities CEWG is a community of people who belong to the industry that wish to become a citizen of grater OSS communities and perform co-creation of innovative software 4 Copyright 2015, CE Workgroup, the Linux Foundation

5 Industry domain CE Workgroup (Past) CEWG worked mainly for consumer electronics industry Through more than 10 years activities many technological challenges of OSS development went well and recently OSS is commonly used in CE industry (Now) CEWG extending the industry domain not only for consumer electronics but also for industrial appliances, medical equipment, transportation/traffic control system and more wider embedded system industry domain We are aiming at the wider use and collaboration of OSS for embedded systems CEWG will bridge to the OSS community and the unique technological challenges in each industry domain 5 Copyright 2015, CE Workgroup, the Linux Foundation

6 Governance Structure of CEWG CE Workgroup Steering Committee election approve Steering Committee Decide the budget, community supporting program and more Architecture Group Members Projects participation select Architecture Group Discussion board of the OSS technologies for the embedded systems Open Project candidates are selected by this group CEWG Projects Open Projects 6 Copyright 2015, CE Workgroup, the Linux Foundation

7 Activities of CEWG (elinux Wiki) CE Workgroup You will find bunch of precious technological information in the elinux Wiki CEWG supports for the site It is the technological information portal of OSS for embedded system developers 7 Copyright 2015, CE Workgroup, the Linux Foundation

8 Activities of CEWG (Linux, Long term support) CE Workgroup An extended support program based on industry requirement (Long Term Support Initiative) is carried out together with the Linux community Generally Linux community terminate supporting Linux when the next to next version released (it is about 5 month). It had been a great headache for the industry people who require the longer term support. The initiative pick up one release of Linux annually and extend the support term to 2 years The automated test environment have also been prepared and we are aiming at more sophisticated quality 8 Copyright 2015, CE Workgroup, the Linux Foundation

9 Activities of CEWG (Open Project) CE Workgroup CEWG Open Project is a open community funding program to reinforce the OSS development which worth for embedded system developers For example, we have funded a project up-streaming development result of Android to the original OSS development communities such as Linux community Solicit the project open to everyone The Architecture Group of CEWG select the solicited projects. Based on the Steering Committee approval, the funding will be carried out Some example of past projects Device tree documentation, Linux-tiny, DirectFB enhancement, Squashfs 9 Copyright 2015, CE Workgroup, the Linux Foundation

10 Activities of CEWG (CEWG Project) CE Workgroup CEWG Project aim to study and to solve issues on embedded system Linux in Civil Infrastructure ( was called Social Infrastructure ) Goals: Solve problems with Linux for use in civil infrastructure systems Status: Project scope presented at ELC 2015 and LinuxCon Japan 2015 Shared Embedded Distribution Goals: Create an industry-supported distribution of embedded Linux and provide support for long term Status: Created an Yocto layer by using Debian source code Presented at ELC, LCJ and ELCE Device Mainlining Goals: Study obstacles to mainlining, and work to reduce obstacles Status: SIG meetings at ELCE and ELC Presentations about overcoming obstacles at ELCE 2014, ELC 2015, and LCJ 2015 White paper (published at LCJ June 2015) 10 Copyright 2015, CE Workgroup, the Linux Foundation

11 Introduction of Shared Embedded Distribution For more information about this project Shared Embedded Linux Distribution CE Workgroup Linux Foundation 13

12 Motivation Linux is running on many kind of embedded systems Including the systems in civil infrastructure Things to be considered to choose a base distribution The number of supported packages Package versions Supported hardware Stability, number of bugs were fixed The frequency of security updates and supported timespan How to compile and customize packages 14

13 In our case What we want to do Make custom embedded Linux environments What we need Wider hardware support Stability Well tested packages are required Many embedded developer are still want to use stable version Long-term support Over 15 years support required, especially for security fixes (This is what we would like to contribute something) Fully customizable build system 15

14 Our solution Yocto Project "poky" One of the most popular reference distributions for embedded Linux Fully customizable build system Supports numerous embedded boards including modern ones Can be extended by meta-layer Debian GNU/Linux Support many kind of CPUs: x86, ARM, PowerPC, MIPS (32bit/64bit) Release a stable version after two years of testing Long-term support for 5 years by Debian-LTS project meta-debian 16

15 What is meta-debian? A meta layer for the Poky build system Main feature Allows cross-building Linux images using Debian source packages Implemented as an independent "layer" Completely separated from OpenEmbedded-Core and other layers Source code: 17

16 Build system structure (poky) Upstream source code Fetch poky build system meta (OpenEmbedded-Core) Board-specific metadata A B C Build A B C 18

17 Build system structure (poky + meta-debian) Upstream source code Debian source packages poky build system meta-debian meta (OpenEmbedded-Core) Board-specific metadata A B C Fetch Build A B C 19

18 Target versions of meta-debian Upstream source code Debian source packages Debian 8.0 jessie poky build system meta-debian Yocto Project 1.6 daisy meta (OpenEmbedded-Core) Board-specific metadata A B C Fetch Build A B C 20

19 Purpose of meta-debian Create embedded Linux environments with Wide embedded CPU support Stability Long-term support Fully customizable build system Provide a common place for developers having the same needs Contribute to upstream (Debian and Yocto Project) Especially for the Debian LTS project With Debian stable release + LTS With poky build system 21

20 Quick start 1. Download the build tools 2. Setup build directory 3. Build minimal Linux image 4. Run minimal Linux image on QEMU See also meta-debian/readme 22

21 Download build tools Download poky $ git clone git://git.yoctoproject.org/poky.git $ cd poky $ git checkout daisy Download meta-debian into the poky directory $ cd poky $ git clone $ cd meta-debian $ git checkout daisy meta-debian specific step 23

22 Setup build directory Change the default configuration Enable meta-debian layer Enable "debian" distro (DISTRO = "debian") The default target machine is "qemux86" (MACHINE = "qemux86") TEMPLATECONF is used by oe-init-build-env script $ export TEMPLATECONF=meta-debian/conf Run startup script This setup a build directory and environment variables automatically (builddir): name of build directory (optional) $ source /path/to/poky/oe-init-build-env (builddir) 24

23 Build minimal Linux image Run bitbake $ bitbake core-image-minimal Built images (case of qemux86) Output directly /path/to/builddir/tmp/deploy/images/qemux86 Kernel bzimage-qemux86.bin Root filesystem core-image-minimal-qemux86.ext3 core-image-minimal-qemux86.tar.gz 25

24 Run minimal Linux image on QEMU Run built images on QEMU environment qemux86 $ runqemu qemux86 nographic bootparams="init=/init root=/dev/sda" qemux86-64 $ runqemu qemux86-64 nographic bootparams="init=/init root=/dev/sda" qemuarm $ runqemu qemuarm nographic bootparams="init=/init console=ttyama0" qemuppc $ runqemu qemuppc nographic bootparams="init=/init" 26

25 How should we create recipe files? We need to create new recipes for Debian sources How? poky build system meta (OpenEmbedded-Core) recipe A recipe B recipe C recipe D Possible solutions Method 1: Modify OE-Core recipes directly Method 2: Add recipes into a new layer 27

26 Method 1: Modify OE-Core recipes We already tried this way previously,but Not the ideal solution Original OE-Core recipes are no longer available (Modified) Just a fork It becomes hard to catch up with the newest poky versions Difficult to convince other people to join our effort poky build system Modify directly meta (OpenEmbedded-Core) recipe A recipe B recipe C recipe D 28

27 Method 2: Add recipes into a new layer our solution The best way to add new recipes for specific purposes Original OE-Core recipes are still there Can be developed independently of OE-Core Enable / disable the layer easily like a module poky build system New layer meta-debian recipe A recipe B recipe C recipe X meta (OpenEmbedded-Core) recipe A recipe B recipe C recipe D 29

28 How should we create recipes in a layer? From scratch? Often takes time! Why? Need to create patches for supporting cross-build in poky We should follow the existing OE-Core recipes How? poky build system meta-debian recipe A recipe B recipe C recipe X How to follow? meta (OpenEmbedded-Core) recipe A recipe B recipe C recipe D 30

29 Method 1: "Include" OE-Core recipes Method 2: Use a part of OE-Core recipes 31

30 Method 1: "Include" OE-Core recipes We used to use this method before Unsuitable for our case Difficult to override some variables and functions Ex: already appended (_append) or prepended (_prepend) data Automatically follow "unneeded" OE-Core updates against our will Ex: Shown in the next slides poky build system 2. Override meta-debian recipe A recipe B recipe C recipe X meta (OpenEmbedded-Core) 1. Include recipe A recipe B recipe C recipe D 32

31 Method 1: "Include" OE-Core recipes binutils openssl binutils binutils CVE patches poky build system meta-debian openssl meta (OpenEmbedded-Core) openssl patches 33

32 Method 1: "Include" OE-Core recipes binutils Security patches applied twice openssl Difficult to maintain Target version was upgraded, and patches also upgraded Some upgraded patches conflict with Debian source poky build system meta-debian binutils openssl CVE conflict patches conflict meta (OpenEmbedded-Core) added Upgraded binutils openssl CVE patches patches 34

33 Method 1: "Include" OE-Core recipes binutils Security patches applied twice openssl Target version was upgraded Some upgraded patches conflict with Debian source Difficult to maintain poky build system Each recipe should create meta-debian for relative source code one binutils by one openssl CVE conflict patches conflict meta (OpenEmbedded-Core) added Upgraded binutils openssl CVE patches patches 35

34 Method 2: Use a part of OE-Core recipes Try to create recipes from scratch using Debian source packages Re-use the essential data from OE-Core patches, variables, functions for supporting cross-build our solution poky build system meta-debian recipe A recipe B recipe C recipe X meta (OpenEmbedded-Core) Partially copy recipe A recipe B recipe C patches variables functions recipe D 36

35 How should we implement recipes? LICENSE information Required files Source code initscripts, configs Patches Configure commands & options Compile commands & options How to installed files How to make the package file Package dependencies Recipe The following slide describes: Method 1: just re-use OE-Core recipes Method 2: Follow Debian s packaging 37

36 Method 1: re-use OE-Core (not a good solution) LICENSE information Required files Source code Debian initscripts, configs Patches Configure commands & options Compile commands & options Installed files and paths How to package files Dependencies between others OE-Core based Debian source Recipe files Build 38

37 Method 1: re-use OE-Core (not a good solution) LICENSE information Required files Source code Debian initscripts, configs Patches Configure commands & options Compile commands & options Installed files and paths How to package files Dependencies between others WHO IS THIS? OE-Core based Debian? poky? Debian source Recipe files Build 39

38 Method 1: re-use OE-Core (not a good solution) Bad results: conflicts of two distributions Compile fails Cause: missing configure options that Debian source requires Some programs fail to call commands or load data file Cause: installation paths differ from Debian s Cannot be used like Debian We should define some development "policy" for creating recipes 40

39 Policies for creating recipes our solution By default, follow Debian s packaging i.e. debian/rules For getting good affinity with Debian sources Customize for embedded system if necessary Disable features Remove dependencies Re-use only essential data from OE-Core for supporting cross-compile See "Method 2: Re-use OE-Core recipes" 41

40 Method 2: Follow Debian s packaging our solution LICENSE information Required files Source code initscripts, configs Patches Debian Configure commands & options Compile commands & options Installed files and paths How to package files OE-Core based Dependencies between others debian/rules Debian-based Debian source Recipe files Build Customize for embedded 42

41 How to create recipes (Sample: zlib) PR = "r0" inherit debian-package LICENSE = "Zlib" LIC_FILES_CHKSUM = "file://zlib.h;beginline=4;endline=23;md5=fde612df1e5933c428b73844a0c494fd" SRC_URI += "file://remove.ldconfig.call.patch" do_configure() {./configure --shared --prefix=${prefix} --libdir=${libdir} } do_compile () { oe_runmake } do_install() { oe_runmake DESTDIR=${D} install } do_install_append_class-target() { mkdir -p ${D}/${base_libdir} mv ${D}/${libdir}/libz.so.* ${D}/${base_libdir} tmp=`readlink ${D}/${libdir}/libz.so` ln -sf../../${base_libdir}/$tmp ${D}/${libdir}/libz.so } DEBIANNAME_${PN}-dbg = "${PN}1g-dbg" DEBIANNAME_${PN}-staticdev = "${PN}1g-staticdev" DEBIANNAME_${PN}-dev = "${PN}1g-dev" DEBIANNAME_${PN}-doc = "${PN}1g-doc" DEBIANNAME_${PN} = "${PN}1g" meta-debian/recipe-debian/zlib/zlib_debian.bb 43

42 Step1: Add recipe revision PR = "r0" inherit debian-package Define recipe revision: ${PR} LICENSE = "Zlib" LIC_FILES_CHKSUM = Increment every update "file://zlib.h;beginline=4;endline=23;md5=fde612df1e5933c428b73844a0c494fd" SRC_URI += "file://remove.ldconfig.call.patch" do_configure() {./configure --shared --prefix=${prefix} --libdir=${libdir} } do_compile () { oe_runmake } do_install() { oe_runmake DESTDIR=${D} install } do_install_append_class-target() { mkdir -p ${D}/${base_libdir} mv ${D}/${libdir}/libz.so.* ${D}/${base_libdir} tmp=`readlink ${D}/${libdir}/libz.so` ln -sf../../${base_libdir}/$tmp ${D}/${libdir}/libz.so } DEBIANNAME_${PN}-dbg = "${PN}1g-dbg" DEBIANNAME_${PN}-staticdev = "${PN}1g-staticdev" DEBIANNAME_${PN}-dev = "${PN}1g-dev" DEBIANNAME_${PN}-doc = "${PN}1g-doc" DEBIANNAME_${PN} = "${PN}1g" 44

43 Step2: Inherit debian-package.bbclass PR = "r0" inherit debian-package LICENSE = "Zlib" LIC_FILES_CHKSUM = "file://zlib.h;beginline=4;endline=23;md5=fde612df1e5933c428b73844a0c494fd" SRC_URI += "file://remove.ldconfig.call.patch" Debian based Setup Debian source package Define SRC_URI Apply Debian s patches (do_debian_patch) do_configure() {./configure --shared --prefix=${prefix} --libdir=${libdir} } do_compile () { oe_runmake } do_install() { oe_runmake DESTDIR=${D} install } do_install_append_class-target() { mkdir -p ${D}/${base_libdir} mv ${D}/${libdir}/libz.so.* ${D}/${base_libdir} tmp=`readlink ${D}/${libdir}/libz.so` ln -sf../../${base_libdir}/$tmp ${D}/${libdir}/libz.so } DEBIANNAME_${PN}-dbg = "${PN}1g-dbg" DEBIANNAME_${PN}-staticdev = "${PN}1g-staticdev" DEBIANNAME_${PN}-dev = "${PN}1g-dev" DEBIANNAME_${PN}-doc = "${PN}1g-doc" DEBIANNAME_${PN} = "${PN}1g" 45

44 Step3: Add license information PR = "r0" inherit debian-package LICENSE = "Zlib" LIC_FILES_CHKSUM = "file://zlib.h;beginline=4;endline=23;md5=fde612df1e5933c428b73844a0c494fd" SRC_URI += "file://remove.ldconfig.call.patch" do_configure() {./configure --shared --prefix=${prefix} --libdir=${libdir} } do_compile () { oe_runmake } do_install() { oe_runmake DESTDIR=${D} install } do_install_append_class-target() { mkdir -p ${D}/${base_libdir} mv ${D}/${libdir}/libz.so.* ${D}/${base_libdir} tmp=`readlink ${D}/${libdir}/libz.so` ln -sf../../${base_libdir}/$tmp ${D}/${libdir}/libz.so } LICENSE: License name Common license names are found in meta/files/common-licenses LIC_FILES_CHKSUM: Checksum of the license text Usually found in COPYING, LICENSE, or header of source files (.c,.h) DEBIANNAME_${PN}-dbg = "${PN}1g-dbg" DEBIANNAME_${PN}-staticdev = "${PN}1g-staticdev" DEBIANNAME_${PN}-dev = "${PN}1g-dev" DEBIANNAME_${PN}-doc = "${PN}1g-doc" DEBIANNAME_${PN} = "${PN}1g" 46

45 Step4: Append patches PR = "r0" inherit debian-package LICENSE = "Zlib" LIC_FILES_CHKSUM = "file://zlib.h;beginline=4;endline=23;md5=fde612df1e5933c428b73844a0c494fd" SRC_URI += "file://remove.ldconfig.call.patch" do_configure() {./configure --shared --prefix=${prefix} --libdir=${libdir} } Add patches into SRC_URI do_compile () { oe_runmake } do_install() { oe_runmake DESTDIR=${D} install } do_install_append_class-target() { mkdir -p ${D}/${base_libdir} mv ${D}/${libdir}/libz.so.* ${D}/${base_libdir} tmp=`readlink ${D}/${libdir}/libz.so` ln -sf../../${base_libdir}/$tmp ${D}/${libdir}/libz.so } Necessary for being built in cross-compile environment Copied from OE-Core (or create it from scratch) DEBIANNAME_${PN}-dbg = "${PN}1g-dbg" DEBIANNAME_${PN}-staticdev = "${PN}1g-staticdev" DEBIANNAME_${PN}-dev = "${PN}1g-dev" DEBIANNAME_${PN}-doc = "${PN}1g-doc" DEBIANNAME_${PN} = "${PN}1g" OE-Core based 47

46 Step5: Define configure options PR = "r0" inherit debian-package LICENSE = "Zlib" LIC_FILES_CHKSUM = "file://zlib.h;beginline=4;endline=23;md5=fde612df1e5933c428b73844a0c494fd" SRC_URI += "file://remove.ldconfig.call.patch" do_configure() {./configure --shared --prefix=${prefix} --libdir=${libdir} } do_compile () { oe_runmake } do_install() { Define configure commands oe_runmake DESTDIR=${D} install The same options as debian/rules } do_install_append_class-target() { } Some features should be disabled for embedded mkdir -p ${D}/${base_libdir} mv ${D}/${libdir}/libz.so.* ${D}/${base_libdir} tmp=`readlink ${D}/${libdir}/libz.so` ln -sf../../${base_libdir}/$tmp ${D}/${libdir}/libz.so DEBIANNAME_${PN}-dbg = "${PN}1g-dbg" DEBIANNAME_${PN}-staticdev = "${PN}1g-staticdev" DEBIANNAME_${PN}-dev = "${PN}1g-dev" DEBIANNAME_${PN}-doc = "${PN}1g-doc" DEBIANNAME_${PN} = "${PN}1g" Debian based 48

47 Step6: Define compile and install commands PR = "r0" inherit debian-package LICENSE = "Zlib" LIC_FILES_CHKSUM = "file://zlib.h;beginline=4;endline=23;md5=fde612df1e5933c428b73844a0c494fd" SRC_URI += "file://remove.ldconfig.call.patch" do_configure() {./configure --shared --prefix=${prefix} --libdir=${libdir} } do_compile () { oe_runmake } do_install() { oe_runmake DESTDIR=${D} install } do_install_append_class-target() { mkdir -p ${D}/${base_libdir} mv ${D}/${libdir}/libz.so.* ${D}/${base_libdir} tmp=`readlink ${D}/${libdir}/libz.so` ln -sf../../${base_libdir}/$tmp ${D}/${libdir}/libz.so } Define compile & install commands autotools.bbclass often replaces them DEBIANNAME_${PN}-dbg = "${PN}1g-dbg" DEBIANNAME_${PN}-staticdev = "${PN}1g-staticdev" DEBIANNAME_${PN}-dev = "${PN}1g-dev" DEBIANNAME_${PN}-doc = "${PN}1g-doc" DEBIANNAME_${PN} = "${PN}1g" 49

48 Additional Steps: Change library paths PR = "r0" inherit debian-package LICENSE = "Zlib" LIC_FILES_CHKSUM = "file://zlib.h;beginline=4;endline=23;md5=fde612df1e5933c428b73844a0c494fd" SRC_URI += "file://remove.ldconfig.call.patch" do_configure() {./configure --shared --prefix=${prefix} --libdir=${libdir} } do_compile () { oe_runmake } do_install() { oe_runmake DESTDIR=${D} install } do_install_append_class-target() { mkdir -p ${D}/${base_libdir} mv ${D}/${libdir}/libz.so.* ${D}/${base_libdir} tmp=`readlink ${D}/${libdir}/libz.so` ln -sf../../${base_libdir}/$tmp ${D}/${libdir}/libz.so } DEBIANNAME_${PN}-dbg = "${PN}1g-dbg" DEBIANNAME_${PN}-staticdev = "${PN}1g-staticdev" DEBIANNAME_${PN}-dev = "${PN}1g-dev" DEBIANNAME_${PN}-doc = "${PN}1g-doc" DEBIANNAME_${PN} = "${PN}1g" Debian based Move run-time libraries to the same directory as Debian 50

49 Additional Steps: Change package name PR = "r0" inherit debian-package LICENSE = "Zlib" LIC_FILES_CHKSUM = "file://zlib.h;beginline=4;endline=23;md5=fde612df1e5933c428b73844a0c494fd" SRC_URI += "file://remove.ldconfig.call.patch" do_configure() {./configure --shared --prefix=${prefix} --libdir=${libdir} } do_compile () { oe_runmake } do_install() { oe_runmake DESTDIR=${D} install } do_install_append_class-target() { mkdir -p ${D}/${base_libdir} mv ${D}/${libdir}/libz.so.* ${D}/${base_libdir} tmp=`readlink "libz" ${D}/${libdir}/libz.so` => "zlib1g" ln -sf../../${base_libdir}/$tmp ${D}/${libdir}/libz.so } Change the default binary package name to Debian s DEBIANNAME_${PN}-dbg = "${PN}1g-dbg" DEBIANNAME_${PN}-staticdev = "${PN}1g-staticdev" DEBIANNAME_${PN}-dev = "${PN}1g-dev" DEBIANNAME_${PN}-doc = "${PN}1g-doc" DEBIANNAME_${PN} = "${PN}1g" Debian based 51

50 Build results (zlib packages) zlib1g /lib/i386-linux-gnu/libz.so.1 /lib/i386-linux-gnu/libz.so /usr/share/doc/zlib1g/... zlib1g-dev /usr/include/i386-linux-gnu/zconf.h /usr/include/zlib.h /usr/lib/i386-linux-gnu/libz.so /usr/lib/i386-linux-gnu/pkgconfig/zlib.pc /usr/share/doc/... /usr/share/man/... /usr/lib/i386-linux-gnu/libz.a zlib1g-dbg zlib1g-udeb Debian 8.0 jessie lib32z1* lib64z1* libn32z1* zlib1g /lib/libz.so.1 /lib/libz.so meta-debian zlib1g-dev /usr/include/zconf.h /usr/include/zlib.h /usr/lib/libz.so /usr/lib/pkgconfig/zlib.pc zlib1g-doc /usr/share/man/... zlib1g-staticdev /usr/lib/libz.a zlib1g-dbg Ignore non-essential files 52

51 Directory structure poky meta recipes-xxx pkg pkg_1.0.bb classes files conf meta-debian recipes-xxx pkg pkg_debian.bb files classes debian-package.bbclass conf layer.conf distro debian.conf 53

52 Directory structure poky meta recipes-xxx pkg pkg_1.0.bb classes conf files Partially copy meta-debian recipes-xxx pkg pkg_debian.bb Core recipes classes Data for supporting cross-compile is partially copied from original recipes debian-package.bbclass files conf layer.conf distro debian.conf 54

53 Directory structure poky meta recipes-xxx pkg pkg_1.0.bb classes files conf meta-debian recipes-xxx pkg pkg_debian.bb Inherited by each recipe files classes debian-package.bbclass Provides debian specific functions and variables Fetch a source package automatically conf Apply Debian s patches automatically distro debian/patches/* layer.conf debian.conf 55

54 Directory structure poky meta recipes-xxx pkg pkg_1.0.bb classes files conf Defines configurations of distro Distro name = "debian" Common server URIs Features System managers meta-debian recipes-xxx pkg pkg_debian.bb classes Ex: init manager = busybox Ex: device manager = udev debian-package.bbclass files Exported to recipes conf layer.conf distro debian.conf 56

55 Build flow bitbake tasks do_fetch() do_unpack() do_debian_patch() do_patch() do_configure() do_compile() do_install() do_package()... pkg.git poky localfiles localfiles localfiles Download directory: ${DL_DIR} Working directory: ${WORKDIR} 57

56 Build flow bitbake tasks do_fetch() do_unpack() do_debian_patch() do_patch() do_configure() do_compile() do_install() do_package()... git clone --bare pkg.git poky localfiles localfiles localfiles Download directory: ${DL_DIR} git2 pkg.git quilt.git.done localfiles localfiles.done Check files Working directory: ${WORKDIR} 58

57 Build flow bitbake tasks do_fetch() do_unpack() do_debian_patch() do_patch() do_configure() do_compile() do_install() do_package()... pkg.git poky Download directory: ${DL_DIR} git2 pkg.git quilt.git.done localfiles localfiles localfiles localfiles localfiles.done Copy git checkout Working directory: ${WORKDIR} git localfiles localfiles localfiles 59

58 Build flow bitbake tasks do_fetch() do_unpack() do_debian_patch() do_patch() do_configure() do_compile() do_install() do_package()... pkg.git poky Download directory: ${DL_DIR} git2 pkg.git quilt.git.done localfiles localfiles localfiles localfiles localfiles.done Working directory: ${WORKDIR} git localfiles localfiles localfiles Apply debian/patches/* 60

59 Build flow bitbake tasks do_fetch() do_unpack() do_debian_patch() do_patch() do_configure() do_compile() do_install() do_package()... pkg.git poky Download directory: ${DL_DIR} git2 pkg.git quilt.git.done localfiles localfiles localfiles localfiles localfiles.done Apply patches for supporting cross-build Working directory: ${WORKDIR} git localfiles localfiles localfiles 61

60 Build flow bitbake tasks do_fetch() do_unpack() do_debian_patch() do_patch() do_configure() do_compile() do_install() do_package()... pkg.git poky localfiles localfiles localfiles Download directory: ${DL_DIR} git2 pkg.git quilt.git.done localfiles localfiles.done Install into the same paths as Debian Working directory: ${WORKDIR} Install directory: ${D} localfiles localfiles Built files git Configure & compile with same options as Debian localfiles localfiles localfiles 62

61 Build flow bitbake tasks do_fetch() do_unpack() do_debian_patch() do_patch() do_configure() do_compile() do_install() do_package()... Package by the same way as Debian pkg.git poky Download directory: ${DL_DIR} git2 pkg.git quilt.git.done Working directory: ${WORKDIR} localfiles localfiles localfiles localfiles localfiles.done localfiles localfiles.deb Install directory: ${D} localfiles localfiles Built files git localfiles localfiles localfiles 63

62 Current status Supported CPUs x86 32bit x86 64bit ARM PowerPC Kernel LTSI User land busybox-based minimal system Number of available packages: around 200 Recipe implementation is still ongoing implementing more recipes to support other packages 64

63 Current development status Meta-debian Poky version Debian version for source code Kernel Distribution Support Status Daisy Debian 8 (Jessie) LTSI 3.10 and RT patch Debian 8 (Jessie) Under development Number of packages Approx. 200 BSPs QEMU(X86, X86_64, ARM, PowerPC) RasberryPi MinnowBoard..etc. - Recipe development is ongoing to increase packages 65

64 Conclusions What is Shared Embedded Linux distribution Share the work of maintaining long-term support for an embedded distribution, by leveraging the work of the Debian project Metadata for building embedded Linux systems using Debian source packages Implemented as an independent layer of OpenEmbedded-Core meta-debian is intended to provide Wide embedded CPU support Stability Long-term support Fully customizable Linux 66

65 Conclusions Policies for creating recipes Debian based configs & packaging + customization for embedded For getting affinity with Debian sources Re-use OE-Core data for supporting cross-build Examples How to build & run a tiny Linux image How to create recipes 67

66 Future work Support more features and packages (over 200) LTSI + RT kernel, Wayland, Qt, etc. Support more embedded boards Testing: improve the quality of the system and packages LTP, LTP-DDT, POSIX test suite, ptest, etc. Contribute to the LTSI test project (JTA) [3] Keep following updates of poky and Debian 68

67 Please give us feedback Repository 69

68 Questions? 70

69 References 1. Poky meets Debian: Understanding How to Make an Embedded Linux by Using an Existing Distribution's Source Code YOSHI-PokyDebian_0.pdf 2. LTSI Test Project 3. Yocto Project Manuals

70 Thank you

71 remove.ldconfig.call.patch When /etc/ld.so.cache is writeable by user running bitbake then it creates invalid cache (in my case libstdc++.so cannot be found after building zlib(-native) and I have to call touch */libstdc++.so && /sbin/ldconfig to fix it. So remove ldconfig call from make install-libs Upstream-Status: Inappropriate [disable feature] diff -unr zlib orig/makefile.in zlib-1.2.6/makefile.in --- zlib orig/makefile.in :48: zlib-1.2.6/makefile.in :38: ,7 rm -f $(DESTDIR)$(sharedlibdir)/$(SHAREDLIB) $(DESTDIR)$(sharedlibdir)/$(SHAREDLIBM); ln -s $(SHAREDLIBV) $(DESTDIR)$(sharedlibdir)/$(SHAREDLIB); ln -s $(SHAREDLIBV) $(DESTDIR)$(sharedlibdir)/$(SHAREDLIBM); - ($(LDCONFIG) true) >/dev/null 2>&1; fi cp zlib.3 $(DESTDIR)$(man3dir) chmod 644 $(DESTDIR)$(man3dir)/zlib.3 73

72 recipes-extended/newt/files/cross_ar.patch... Makefile.in 3 ++configure.ac files changed, 6 insertions(+), 1 deletion(-) --- a/makefile.in ,6 CFLAGS LDFLAGS CPPFLAGS = GNU_LD +AR VERSION TAG = -95,7 whiptcl.so: $(WHIPTCLOBJS) $(LIBNEWTSH) $(CC) -shared $(SHCFLAGS) $(LDFLAGS) -o whiptcl.so $(WHIPTCLOBJS) - L. -lnewt $(LIBTCL) -lpopt $(LIBS) $(LIBNEWT): $(LIBOBJS) - ar rv $@ $^ + $(AR) rv $@ $^ newt.o $(SHAREDDIR)/newt.o: newt.c Makefile... 74

73 qt4-embedded_git.bb require qt4-libs.inc PR = "r0" QT_CONFIG_FLAGS = " -v -embedded ${QT_ARCH} -release -opensource -make libs -nomake tools -nomake examples -nomake demos... 75