Yocto Project - User contributions [en]

Yocto Project Summit 2019

2019-11-12T12:00:37Z

Alexander Kanavin: add a link to slides

== Slides ==

Slides are here: https://wiki.yoctoproject.org/wiki/YP_Summit_Lyon_2019

== Yocto Project® Summit 2019 ==

The Yocto Project will be running its 1st Summit in 2019, the event will be co-located with the [https://events.linuxfoundation.org/events/embedded-linux-conference-europe-2019/ Embedded Linux Conference Europe].

* '''DATE''': Thursday, October 31 - Friday, November 1, 2019
* '''TIME''': 9:00 am – 5:00 pm
* '''LOCATION''': [https://www.google.com/maps/place/Palais+des+congr%C3%A8s+de+Lyon/@45.7851957,4.8532323,17z/data=!4m8!1m2!2m1!1slyon+convention+center!3m4!1s0x47f4eac0a2068105:0x601302e66888357d!8m2!3d45.7850013!4d4.8546238 Lyon Convention Center]

== Details ==

The Yocto Project Summit, scheduled for October 31-November 1, 2019 at the Lyon Convention Centre, Lyon, France, is a technical conference for engineers, open source technologists, students and academia in the OSS space. Organized in conjunction with ELCE 2019, this 2-day event is where individuals will learn about Yocto Projects’ direction -- including, but not limited to, new releases, development tools, features -- get training on the next wave of embedded Linux technologies (segment previously known as Yocto Project Developer Day), and network with their industry peers, Yocto Project maintainers and experts.

For the first time, the Yocto Project Developer Day has expanded its scope to include both the workshop for engineers building customized Linux distributions and applications, as well as an open forum where maintainers, trainers, and users present papers on how the project is evolving and how they are using it.

== Why Attend? ==

Learn how Yocto Project-based software and new features, never seen before in the community, can help harness the power of automation and cross-compiling to overcome development barriers and formulate efficient approaches to follow CI/CD models, DevOps practices, cybersecurity requirements and more.

Summit attendees will:
* Hear from Yocto Project maintainers about current release topics such as automated testing, optimized builds, automated CVE analysis, SPDX license identifiers, automated recipe upgrades
* Attend sessions on DevOps, cybersecurity, containers, edge computing
* Gain hands-on experience with the Yocto Project infrastructure and tools

Attending the Yocto Project Summit will provide you with a strong base of knowledge around the Yocto Project developer tools and how they are being used in the industry.

== Registration Cost ==

* Early Registration: $179 (through August 23, 11:59 pm PST)
* Standard Registration: $209 (August 24 – September 27, 11:59 pm PST)
* Late Registration: $249 (September 28 – Event)

== Program ==

* Day 1: Keynote and general sessions on Yocto Project technology and usage (CFP open, see information below)
* Day 2: Breakout sessions containing 2 tracks
** Track 1: Yocto Project workshop-hackathon
** Track 2: Yocto Project and OpenEmbedded maintainers meeting

Lunch and snacks are offered on both days.

== Social Event ==

Day 1: Join us for an evening reception with drinks and appetizers.

== Who Can Benefit ==

* System/Software Developers
* Tech Leads / Development Leads
* Software Architects
* Chief Engineers
* System Engineers
* Development Engineers
* Embedded Engineers / Programmer
* DevOps / System Administrators
* Application Engineers
* Open Source Technologists

== Call for papers (CFP) ==

* Submit your proposals to [mailto:conferences@yoctoproject.org conferences@yoctoproject.org].
* Proposals should contain topic, speaker, title, and abstract.

Schedule

* '''CFP Opens''': Monday, August 12
* '''CFP Closes''': 11:59 PM PST on Monday, September 16
* '''CFP Notifications''': Monday, September 23
* '''Schedule Announcement''': Thursday, September 30
* '''Slides Due Date''': Monday, October 21

List of topics

* DevTool
* Layer quality: e.g. creating robust layers, safely using existing layers
* Future languages (e.g. Rust)
* Productivity tricks and tools
* Security
* Reproducibility
* Init systems: pros and cons, selection, configuration
* Leveraging the new runqueue optimizations for mirrors, reproducible builds
* Supporting the Application Developer
* DevOps
* Working with/creating BSPs
* Practical use of the Yocto Project

== Contact==

If you have any questions about the Yocto Project Summit or are considering becoming a sponsor please contact us at [mailto:conferences@yoctoproject.org conferences@yoctoproject.org].

Releases

2019-02-05T13:55:59Z

Alexander Kanavin:

== Release Activity==

{| class="wikitable" border="2"
!Codename
!Yocto Project Version
!Release Date
!Current Version
!Support Level
!Poky Version
!BitBake branch
|-
|Zeus
|2.8
|October 2019
|
|Planning
|22.0
|1.44
|-
|Warrior
|2.7
|April 2019
|
|Development
|21.0
|1.42
|-
|Thud
|2.6
|November 2018
|2.6.0
|Stable
|20.0
|1.40
|-
|Sumo
|2.5
|April 2018
|2.5.2
|Stable
|19.0
|1.38
|-
|Rocko
|2.4
|Oct 2017
|2.4.4
|Stable
|18.0
|1.36
|-
|Pyro
|2.3
|May 2017
|2.3.4
|Community
|17.0
|1.34
|-
|Morty
|2.2
|Nov 2016
|2.2.4
|Community
|16.0
|1.32
|-
|-
|Krogoth
|2.1
|Apr 2016
|2.1.3
|Community
|15.0
|1.30
|-
|Jethro
|2.0
|Nov 2015
|2.0.3
|Community
|14.0
|1.28
|-
|Fido
|1.8
|Apr 2015
|1.8.2
|Community
|13.0
|1.26
|-
|Dizzy
|1.7
|Oct 2014
|1.7.3
|Community
|12.0
|1.24
|-
|Daisy
|1.6
|Apr 2014
|1.6.3
|Community
|11.0
|1.22
|-
|Dora
|1.5
|Oct 2013
|1.5.4
|Community
|10.0
|1.20
|-
|Dylan
|1.4
|Apr 2013
|1.4.3[https://lists.yoctoproject.org/pipermail/yocto/2014-July/020699.html *]
|Community
|9.0
|1.18
|-
|Danny
|1.3
|Oct 2012
|1.3.2
|Community
|8.0
|1.16
|-
|Denzil
|1.2
|Apr 2012
|1.2.2
|Community
|7.0
|1.15
|-
|Edison
|1.1
|Oct 2011?
|1.1.2
|Community
|6.0
|1.13
|-
|Bernard
|1.0
|??? 2011?
|1.0.2
|Community
|5.0
|1.11
|-
|Laverne
|0.9
|??? 2010?
|
|
|4.0
|1.11
|-
|Purple
|N/A
|??? ????
|
|
|3.2
|
|-
|Pinky
|N/A
|??? ????
|
|
|3.1
|
|-
|Blinky
|N/A
|??? ????
|
|
|3.0
|
|-
|Clyde
|N/A
|??? ????
|
|
|2.0
|
|-
|Inky
|N/A
|??? ????
|
|
|1.0
|
|}

'''Note:''' see also [[Stable branch maintenance]], [[Linux Yocto]], [[Planning]] and [[Release Feature Table]] pages.

== Releases Links==
{| class="wikitable" border="2"
| align="center" style="background:#f0f0f0;"|'''Yocto Project Release'''
| align="center" style="background:#f0f0f0;"|'''Code Name'''
| align="center" style="background:#f0f0f0;"|'''Poky version'''
| align="center" style="background:#f0f0f0;"|'''Maintainer'''
| align="center" style="background:#f0f0f0;"|'''Features'''
| align="center" style="background:#f0f0f0;"|'''Schedule'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''QA Test Plan'''
| align="center" style="background:#f0f0f0;"|'''QA Test Report'''
| align="center" style="background:#f0f0f0;"|'''Release notes'''
|-valign="top"
| Yocto Project 2.6
| Thud
| 20.0
| Richard Purdie
| [[Yocto_2.6_Features]]
| [[Yocto_2.6_Schedule]]
| [[Yocto_Project_v2.6_Status]]
| [[Yocto_Project_2.6_Release_Test_Plan | Yocto_2.6_Overall_Test_Plan]]
| [[Yocto_Project_2.6_Release_Test_Plan#Execution_History | 2.6 qa run history]]
| [https://lists.yoctoproject.org/pipermail/yocto-announce/2018-November/000147.html 2.6 release notes]
|-
|-valign="top"
| Yocto Project 2.5
| Sumo
| 19.0
| Armin Kuster
| [[Yocto_2.5_Features]]
| [[Yocto_2.5_Schedule]]
| [[Yocto_Project_v2.5_Status]]
| [[Yocto_Project_2.5_Release_Test_Plan | Yocto_2.5_Overall_Test_Plan]]
| [[Yocto_Project_2.5_Release_Test_Plan#Execution_History | 2.5 qa run history]]
| [https://lists.yoctoproject.org/pipermail/yocto-announce/2018-May/000136.html 2.5 release notes]
|-
|-valign="top"
| Yocto Project 2.4
| Rocko
| 18.0
| Armin Kuster
| [[Yocto_2.4_Features]]
| [[Yocto_2.4_Schedule]]
| [[Yocto_Project_v2.4_Status]]
| [[Yocto_Project_2.4_Release_Test_Plan | Yocto_2.4_Overall_Test_Plan]]
| [[Yocto_Project_2.4_Release_Test_Plan#Execution_History | 2.4 qa run history]]
| [https://lists.yoctoproject.org/pipermail/yocto-announce/2017-October/000125.html 2.4 release notes]
|-
|-valign="top"
| Yocto Project 2.3
| Pyro
| 17.0
| Armin Kuster
| [[Yocto_2.3_Features]]
| [[Yocto_2.3_Schedule]]
| [[Yocto_Project_v2.3_Status]]
| [[Yocto_Project_2.3_Release_Test_Plan | Yocto_2.3_Overall_Test_Plan]]
| [[Yocto_Project_2.3_Release_Test_Plan#Execution_History | 2.3 qa run history]]
| [https://lists.yoctoproject.org/pipermail/yocto-announce/2017-May/000112.html 2.3 release notes]
|-
|-valign="top"
| Yocto Project 2.2
| Morty
| 16.0
| Armin Kuster
| [[Yocto_2.2_Features]]
| [[Yocto_2.2_Schedule]]
| [[Yocto_Project_v2.2_Status]]
| [[Yocto_2.2_Overall_Test_Plan]]
| [[Yocto_Project_2.2_Release_Test_Plan#Execution_History | 2.2 qa run history]]
| [https://lists.yoctoproject.org/pipermail/yocto-announce/2016-November/000101.html 2.2 release notes]
|-
|-valign="top"
| Yocto Project 2.1
| Krogoth
| 15.0
| Armin Kuster
| [[Yocto_2.1_Features]]
| [[Yocto_2.1_Schedule]]
| [[Yocto_Project_v2.1_Status]]
| [[Yocto_2.1_Overall_Test_Plan]]
| [[2.1 qa run history]]
| [https://lists.yoctoproject.org/pipermail/yocto-announce/2016-May/000089.html 2.1 release notes]
|-
|-valign="top"
| Yocto Project 2.0
| Jethro
| 14.0
| Robert Yang
| [[Yocto_1.9_Features]]
| [[Yocto_1.9_Schedule]]
| [[Yocto_Project_v1.9_Status]]
|
| [[1.9 qa run history]]
| [https://lists.yoctoproject.org/pipermail/yocto-announce/2015-November/000076.html 2.0 release notes]
|-valign="top"
| Yocto Project 1.8
| Fido
| 13.0
| Joshua Lock
| [[Yocto_1.8_Features]]
| [[Yocto_1.8_Schedule]]
| [[Yocto_Project_v1.8_Status]]
| [[Yocto_1.8_Overall_Test_Plan]]
| [[1.8 qa run history]]
| [https://lists.yoctoproject.org/pipermail/yocto-announce/2015-April/000062.html 1.8 release notes]
|-
| Yocto Project 1.7
| Dizzy
| 12.0
| Community
| [[Yocto_1.7_Features]]
| [[Yocto_1.7_Schedule]]
| [[Yocto_Project_v1.7_Status]]
| [[Yocto_1.7_Overall_Test_Plan]]
| [[1.7 qa run history]]
| [https://lists.yoctoproject.org/pipermail/yocto-announce/2014-October/000053.html 1.7 release notes]
|-
| Yocto Project 1.6
| Daisy
| 11.0
| Community
| [[Yocto_1.6_Features]]
| [[Yocto_1.6_Schedule]]
| [[Yocto_Project_v1.6_Status]]
| [[Yocto_1.6_Overall_Test_Plan]]
| [[1.6 qa run history]]
| [https://lists.yoctoproject.org/pipermail/yocto-announce/2014-April/000045.html 1.6 release notes]
|-
| Yocto Project 1.5
| Dora
| 10.0
| Community
| [[Yocto_1.5_Features]]
| [[Yocto_1.5_Schedule]]
| [[Yocto_Project_v1.5_Status]]
| [[Yocto_1.5_Overall_Test_Plan]]
| [[1.5 qa run history]]
| [https://lists.yoctoproject.org/pipermail/yocto-announce/2013-October/000037.html 1.5 release notes]
|-
| Yocto Project 1.4
| Dylan
| 9.0
| Community
| [[Yocto_1.4_Features]]
| [[Yocto_1.4_Schedule]]
| [[Yocto_Project_v1.4_Status]]
| [[Yocto_1.4_Overall_Test_Plan]]
| [[Yocto_1.4_Milestone_Test_Report]]
| [https://lists.yoctoproject.org/pipermail/yocto-announce/2013-April/000027.html 1.4 release notes]
|-
| Yocto Project 1.3
| Danny
| 8.0
| Community
| [[Yocto_1.3_Features]]
| [[Yocto_1.3_Schedule]]
| [[Yocto_Project_v1.3_Status]]
| [[Yocto_1.3_Overall_Test_Plan]]
| [[Yocto_1.3_Milestone_Test_Report]]
| [https://lists.yoctoproject.org/pipermail/yocto-announce/2012-October/000020.html 1.3 release notes]
|-
| Yocto Project 1.2
| Denzil
| 7.0
| Community
| [[Yocto_1.2_Features]]
| [[Yocto_1.2_Schedule]]
| [[Yocto_Project_v1.2_Status]]
| [[Yocto_1.2_Overall_Test_Plan]]
| [[Yocto_1.2_Milestone_Test_Report]]
| [https://lists.yoctoproject.org/pipermail/yocto-announce/2012-April/000009.html 1.2 release notes]
|-
| Yocto Project 1.1
| Edison
| 6.0
| Community
| [[Yocto_1.1_Features]]
| [[Yocto_1.1_Schedule]]
| [[Yocto_Project_v1.1_Release_Criteria]]
| [[Yocto_1.1_Overall_Test_Plan]]
| [[Yocto_1.1_Milestone_Test_Report]]
|
|-
| Yocto Project 1.0
| Bernard
| 5.0
| Community
| [[Yocto_Features]]
| [[Yocto_1.0_Schedule]]
| [[Yocto_Project_v1.0_Release_Criteria]]
| [[Yocto_1.0_Overall_Test_Plan]]
|
|
|}

FutureMigrationGuide

2018-02-27T13:45:30Z

Alexander Kanavin:

{| style="color:black; background-color:#ffffcc" width="100%" cellpadding="10" class="wikitable"
|This page should be used to keep track of items which should be added to the [http://www.yoctoproject.org/docs/latest/ref-manual/ref-manual.html#migration migration guide] in the YP Reference Manual. It's a living document for the life of a development cycle and by M4 should represent a significant proportion of items that are worthy of note in the migration guide.

Once the migration guide for a release has been completed the contents of this page should be cleared out.
|}

=2.5 Migration Guide items=

* kernel.bbclass now supports multiple kernel packages. If your kernel recipe/bbappend mentions packaging at all then you will need to replace "kernel" with "${KERNEL_PACKAGE_NAME}". For example if you disable automatic installation of the kernel image using RDEPENDS_kernel-base = "" then to avoid warnings you will now need to use RDEPENDS_${KERNEL_PACKAGE_NAME}-base = "" instead.
* We removed the fetchall and checkuriall tasks, "bitbake X --runall=fetch" and "bitbake X --runall=checkuri" replace them. --runonly option added to bitbake which behaves like the older --runall option.
* meson build system support has been added via meson.bbclass. Extra options defined via EXTRA_OEMESON. Ask AlexK for more details.
* package postinst support has been reworked. On-target postinsts should be defined via pkg_postinst_ontarget(), explicit deferral via 'postinst_intercept defer_to_first_boot'. The relevant section in the yocto docs needs to be adjusted. Ask AlexK for more details.
* The buildhistory class sets BUILDHISTORY_COMMIT to "1" by default, since this is the most sensible default. In the unlikely event that you were relying upon the default to not commit history to a git repository on every build, you'll now need to explicitly set BUILDHISTORY_COMMIT = "0" in your configuration.
* pax recipe has been removed, commit: http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=1dd146d5acd6bb4c0d65045071e2fd27590b8df4

FutureMigrationGuide

2018-02-14T14:29:33Z

Alexander Kanavin: /* 2.5 Migration Guide items */

{| style="color:black; background-color:#ffffcc" width="100%" cellpadding="10" class="wikitable"
|This page should be used to keep track of items which should be added to the [http://www.yoctoproject.org/docs/latest/ref-manual/ref-manual.html#migration migration guide] in the YP Reference Manual. It's a living document for the life of a development cycle and by M4 should represent a significant proportion of items that are worthy of note in the migration guide.

Once the migration guide for a release has been completed the contents of this page should be cleared out.
|}

=2.5 Migration Guide items=

* kernel.bbclass now supports multiple kernel packages. If your kernel recipe disables automatic installation of the kernel image using RDEPENDS_kernel-base = "" then to avoid warnings you will now need to use RDEPENDS_${KERNEL_PACKAGE_NAME}-base = "" instead.
* We removed the fetchall and checkuriall tasks, "bitbake X --runall=fetch" and "bitbake X --runall=checkuri" replace them. --runonly option added to bitbake which behaves like the older --runall option.
* meson build system support has been added via meson.bbclass. Extra options defined via EXTRA_OEMESON. Ask AlexK for more details.
* package postinst support has been reworked. On-target postinsts should be defined via pkg_postinst_ontarget(), explicit deferral via 'postinst_intercept defer_to_first_boot'. The relevant section in the yocto docs needs to be adjusted. Ask AlexK for more details.

TipsAndTricks/DebugNativeRecipeWithGdb

2017-02-15T14:16:59Z

Alexander Kanavin: update by Alex

=How to debug native recipes with gdb=

I recently had the need to debug a crash in a native binary that a layer I was working on invokes during the build.

To debug the crash with gdb I had to do two things; 1) have the build system generate a binary with debug symbols and 2) not have them stripped during installation to sysroot.

To enable debug symbols, usually one needs to add "-g" to the list of compiler flags. Unforunately how this is done is specific to each project - you need to inspect the
source code tree and look for clues. For autoconf-based projects adding to CFLAGS environment variable is enough.

After the build has completed, inspect the compilation log to verify that -g is indeed there.

To ensure that the binaries in the sysroot don't have their debugging symbols stripped you need to set <code>INHIBIT_SYSROOT_STRIP = "1"</code> in your local.conf

Alternatively you might want to only inhibit stripping for specific recipes, this can be achieved using recipe OVERRIDES such as:

INHIBIT_SYSROOT_STRIP_pn-swupd-server-native = "1"

I used the former as it allowed me to be certain of having all debugging symbols available.

Note: you'll need to ensure any binaries you wish to debug are (re-)staged into the sysroot after changing this setting.

For more information on the gdb commands above see the gdb manual section [https://sourceware.org/gdb/current/onlinedocs/gdb/Files.html#Files "Commands to Specify Files"]