Yocto Project - User contributions [en]

File:Crops-generator.mp4

2023-06-28T14:56:06Z

Tim Orling: Demo of running crops-generator and configuring a build of the Yoe Distro.

== Summary ==
Demo of running crops-generator and configuring a build of the Yoe Distro.

YP DevDay Prague 2023

2023-06-25T10:39:55Z

Tim Orling:

This page contains slides for the talks in the Yocto Project DevDay, EOSS/ELCE Prague 2023

Starting at 9:00am, 26 June 2023, Central European Summer Time.

YP DevDay home page is here: [https://www.yoctoproject.org/yocto-dev-day-june2023/ https://www.yoctoproject.org/yocto-dev-day-june2023/]

The Schedule page is here: [https://summit.yoctoproject.org/devday-at-eoss-2023/schedule/ https://summit.yoctoproject.org/devday-at-eoss-2023/schedule/]

== Slides ==

* Presenter Slides

[https://wiki.yoctoproject.org/wiki/images/b/b4/Customize_your_CROPS_containers_with_crops-generator.pdf Customize your CROPS containers with crops-generator.pdf]

* Class Movies, example code

[https://docs.google.com/file/d/1Kwb_zA1CntL0Dm3K4lNXis1HtLWH4X6b/preview crops-generator.mp4 (crops-generator)]

YP DevDay Prague 2023

2023-06-25T09:06:42Z

Tim Orling: /* Slides */

This page contains slides for the talks in the Yocto Project DevDay, EOSS/ELCE Prague 2023

== Slides ==

* Presenter Slides

[https://wiki.yoctoproject.org/wiki/images/b/b4/Customize_your_CROPS_containers_with_crops-generator.pdf Customize your CROPS containers with crops-generator.pdf]

* Class Movies, example code

[https://docs.google.com/file/d/1Kwb_zA1CntL0Dm3K4lNXis1HtLWH4X6b/preview crops-generator.mp4 (crops-generator)]

YP DevDay Prague 2023

2023-06-25T09:05:25Z

Tim Orling: /* Slides */

This page contains slides for the talks in the Yocto Project DevDay, EOSS/ELCE Prague 2023

== Slides ==

* Presenter Slides

[https://wiki.yoctoproject.org/wiki/File:Customize your CROPS containers with crops-generator.pdf Customize your CROPS containers with crops-generator.pdf]

* Class Movies, example code

[https://docs.google.com/file/d/1Kwb_zA1CntL0Dm3K4lNXis1HtLWH4X6b/preview crops-generator.mp4 (crops-generator)]

File:Customize your CROPS containers with crops-generator.pdf

2023-06-25T09:02:59Z

Tim Orling: Slides from Tim Orling and Eilís 'pidge' Ní Fhlannagáin presentation about crops-generator from Yocto Project DevDay Prague 2023

== Summary ==
Slides from Tim Orling and Eilís 'pidge' Ní Fhlannagáin presentation about crops-generator from Yocto Project DevDay Prague 2023

YP DevDay Prague 2023

2023-06-25T06:57:08Z

Tim Orling: Skeleton for YP DD 2023

This page contains slides for the talks in the Yocto Project DevDay, EOSS/ELCE Prague 2023

== Slides ==

* Presenter Slides

* Class Movies, example code

[https://wiki.yoctoproject.org/wiki/File:crops-generator.mp4 crops-generator.mp4 (crops-generator)]

Releases

2023-01-21T22:11:57Z

Tim Orling: /* Release Activity */

== Release Activity==

Releases can be downloaded at https://www.yoctoproject.org/software-overview/downloads/

{| class="wikitable" border="2"
!Codename
!Yocto Project Version
!Release Date
!Current Version
!Support Level
!Poky Version
!BitBake branch
! Maintainer
|-
|Nanbield
|4.3
| October 2023
|
|Future - Support for 7 months (until April 2024)
|N/A
|
|Richard Purdie <richard.purdie@linuxfoundation.org>
|-
|Mickledore
|4.2
| April 2023
|
|Future - Support for 7 months (until October 2023)
|N/A
|
|Richard Purdie <richard.purdie@linuxfoundation.org>
|-
|Langdale
|4.1
| October 2022
| 4.1.2 (January 2023)
| Support until May 2023
|N/A
|2.2
|Steve Sakoman <steve@sakoman.com>
|-
|Kirkstone
|4.0
|May 2022
|4.0.6 (December 2022)
|Long Term Support (minimum Apr. 2024)
|N/A
|2.0
|Steve Sakoman <steve@sakoman.com>
|-
|-style="color: slategray;"
|Honister
|3.4
|October 2021
|3.4.4 (May 2022)
|EOL
|N/A
|1.52
|Anuj Mittal <anuj.mittal@intel.com>
|-
|-style="color: slategray;"
|Hardknott
|3.3
|April 2021
|3.3.6 (April 2022)
|EOL
|N/A
|1.50
|Anuj Mittal <anuj.mittal@intel.com>
|-
|-style="color: slategray;"
|Gatesgarth
|3.2
|Oct 2020
|3.2.4 (May 2021)
|EOL
|N/A
|1.48
|Anuj Mittal <anuj.mittal@intel.com>
|-
|Dunfell
|3.1
|April 2020
|3.1.21 (November 2022)
|Long Term Support (until Apr. 2024)
|23.0
|1.46
|Steve Sakoman <steve@sakoman.com>
|-style="color: slategray;"
|Zeus
|3.0
|October 2019
|3.0.4 (August 2020)
|EOL
|22.0.3
|1.44
| Anuj/Armin
|-style="color: slategray;"
|Warrior
|2.7
|April 2019
|2.7.4 (June 2020)
|EOL
|21.0
|1.42
|Armin Kuster <akuster808@gmail.com>
|-style="color: slategray;"
|Thud
|2.6
|Nov 2018
|2.6.4 (October 2019)
|EOL
|20.0
|1.40
| Armin Kuster <akuster808@gmail.com>
|-style="color: slategray;"
|Sumo
|2.5
|April 2018
|2.5.3 (April 2019)
|EOL
|19.0
|1.38
| Armin Kuster <akuster808@gmail.com>
|-style="color: slategray;"
|Rocko
|2.4
|Oct 2017
|2.4.4 (November 2018)
|EOL
|18.0
|1.36
| Armin Kuster <akuster808@gmail.com>
|-style="color: slategray;"
|Pyro
|2.3
|May 2017
|2.3.4 (July 2018)
|EOL
|17.0
|1.34
| Armin Kuster <akuster808@gmail.com>
|-style="color: slategray;"
|Morty
|2.2
|Nov 2016
|2.2.4 (July 2018)
|EOL
|16.0
|1.32
| Armin Kuster <akuster808@gmail.com>
|-style="color: slategray;"
|Krogoth
|2.1
|Apr 2016
|2.1.3 (July 2017)
|EOL
|15.0
|1.30
| Armin Kuster <akuster808@gmail.com>
|-style="color: slategray;"
|Jethro
|2.0
|Nov 2015
|2.0.3 (January 2016)
|EOL
|14.0
|1.28
|Robert Yang <liezhi.yang@windriver.com>
|-style="color: slategray;"
|Fido
|1.8
|Apr 2015
|1.8.2
|EOL
|13.0
|1.26
|Joshua Lock <joshua.g.lock@intel.com>
|-style="color: slategray;"
|Dizzy
|1.7
|Oct 2014
|1.7.3
|EOL
|12.0
|1.24
| Armin Kuster <akuster808@gmail.com>
|-style="color: slategray;"
|Daisy
|1.6
|Apr 2014
|1.6.3
|EOL
|11.0
|1.22
| Saul Wold <sgw@linux.intel.com>
|-style="color: slategray;"
|Dora
|1.5
|Oct 2013
|1.5.4
|EOL
|10.0
|1.20
| Robert Yang <liezhi.yang@windriver.com>
|-style="color: slategray;"
|Dylan
|1.4
|Apr 2013
|1.4.3
|EOL
|9.0
|1.18
| Paul Eggleton <paul.eggleton@linux.intel.com>
|-style="color: slategray;"
|Danny
|1.3
|Oct 2012
|1.3.2
|EOL
|8.0
|1.16
|Ross Burton <ross.burton@intel.com>
|-style="color: slategray;"
|Denzil
|1.2
|Apr 2012
|1.2.2
|EOL
|7.0
|1.15
|-style="color: slategray;"
|Edison
|1.1
|Oct 2011
|1.1.2
|EOL
|6.0
|1.13
|-style="color: slategray;"
|Bernard
|1.0
|Apr 2011
|1.0.2
|EOL
|5.0
|1.11
|-style="color: slategray;"
|Laverne
|0.9
|Oct 2010
|
|
|4.0
|1.11
|-style="color: slategray;"
|Green
|N/A
|11 June 2010
|
|
|3.3
|
|-style="color: slategray;"
|Purple
|N/A
|15 Dec 2009
|
|
|3.2
|
|-style="color: slategray;"
|Pinky
|N/A
|12 Nov 2009
|
|
|3.1
|
|-style="color: slategray;"
|Blinky
|N/A
|1 Aug 2007
|
|
|3.0
|
|-style="color: slategray;"
|Clyde
|N/A
|19 Jan 2007
|
|
|2.0
|
|-style="color: slategray;"
|Inky
|N/A
|10 Feb 2006
|
|
|1.0
|
|}

'''Note:''' see also [[Stable Release and LTS]], [[Linux Yocto]], [[Planning]] and [[Release Feature Table]] pages. EOL means some community support on email lists but no commit updates in the repos. There is also OS Vendor support for some Yocto EOL releases.

== 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 3.4
| Honister
| 26.0
| Anuj Mittal
| [[Yocto_3.4_Features]]
| [[Yocto_3.4_Schedule]]
| [[Yocto_Project_v3.4_Status]]
| [[Yocto_Project_3.4_Release_Test_Plan | Yocto_3.4_Overall_Test_Plan]]
| [[Yocto_Project_3.4_Release_Test_Plan#Execution_History | 3.4 qa run history]]
| [https://lists.yoctoproject.org/g/yocto-announce/message/229 3.4 release notes]
|-
| Yocto Project 3.3
| Hardknott
| 25.0
| Anuj Mittal
| [[Yocto_3.3_Features]]
| [[Yocto_3.3_Schedule]]
| [[Yocto_Project_v3.3_Status]]
| [[Yocto_Project_3.3_Release_Test_Plan | Yocto_3.3_Overall_Test_Plan]]
| [[Yocto_Project_3.3_Release_Test_Plan#Execution_History | 3.3 qa run history]]
| [https://lists.yoctoproject.org/g/yocto-announce/message/215 3.3 release notes]
|-
| Yocto Project 3.2
| Gatesgarth
| 24.0
| Anuj Mittal
| [[Yocto_3.2_Features]]
| [[Yocto_3.2_Schedule]]
| [[Yocto_Project_v3.2_Status]]
| [[Yocto_Project_3.2_Release_Test_Plan | Yocto_3.2_Overall_Test_Plan]]
| [[Yocto_Project_3.2_Release_Test_Plan#Execution_History | 3.2 qa run history]]
| [https://lists.yoctoproject.org/g/yocto/message/51262 3.2 release notes]
|-
|-valign="top"
| Yocto Project 3.1
| Dunfell
| 23.0
| Steve Sakoman
| [[Yocto_3.1_Features]]
| [[Yocto_3.1_Schedule]]
| [[Yocto_Project_v3.1_Status]]
| [[Yocto_Project_3.1_Release_Test_Plan | Yocto_3.1_Overall_Test_Plan]]
| [[Yocto_Project_3.1_Release_Test_Plan#Execution_History | 3.1 qa run history]]
| [https://lists.yoctoproject.org/g/yocto/message/49201 3.1 release notes]
|-

|-valign="top"
| Yocto Project 3.0
| Zeus
| 22.0
| Armin Kuster/Anuj Mittal
| [[Yocto_2.8_Features]]
| [[Yocto_2.8_Schedule]]
| [[Yocto_Project_v2.8_Status]]
| [[Yocto_Project_2.8_Release_Test_Plan | Yocto_2.8_Overall_Test_Plan]]
| [[Yocto_Project_2.8_Release_Test_Plan#Execution_History | 2.8 qa run history]]
| [https://lists.yoctoproject.org/pipermail/yocto/2019-October/047111.html 3.0 release notes]
|-
|-valign="top"
| Yocto Project 2.7
| Warrior
| 21.0
| Community
| [[Yocto_2.7_Features]]
| [[Yocto_2.7_Schedule]]
| [[Yocto_Project_v2.7_Status]]
| [[Yocto_Project_2.7_Release_Test_Plan | Yocto_2.7_Overall_Test_Plan]]
| [[Yocto_Project_2.7_Release_Test_Plan#Execution_History | 2.7 qa run history]]
| [https://lists.yoctoproject.org/pipermail/yocto/2019-May/045028.html 2.7 release notes]
|-
|-valign="top"
| Yocto Project 2.6
| Thud
| 20.0
| Community
| [[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
| Community
| [[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
| Community
| [[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
| Community
| [[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
| Community
| [[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
| Community
| [[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
| Community
| [[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
| Community
| [[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]]
|
|
|}

Bug Triage

2022-05-05T15:02:09Z

Tim Orling: /* Bug Triage Order */

= Goal =
The output of the bug triage meeting should be that all bugs have an owner, a target milestone, and a priority.

Prior to the meeting, each Product Owner should review their Weekly New and High Bugs and be ready with any opens. An example open would be a bug that may need to change Products.

= Roles =
* Call facilitator: Stephen Jolley (sjolley.yp.pm@gmail.com)
** Ensure we keep to the agenda, don't rathole on bug resolution, and stay within our time block.
* Team Leads should pre-triage bugs for their areas of responsibility. Some guidelines on what they should/shouldn't do are:
** a) Pre-triage should happen in the presence of the appropriate team lead,
** b) The bugs being pre-triaged should be the responsibility of the team in question.
** c) The pre-triage team should be confident when dis-positioning the bugs, taking into account the individual's workload.
** d) If the bug raises any doubt or needs information prior, defer it to the main bug triage team.
** e) To insure a bug is triaged by the main bug triage team; set its priority to Undecided.

= Agenda =
* [https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09 Zoom Call Link]
* Review [https://bugzilla.yoctoproject.org/buglist.cgi?list_id=604307&resolution=---&query_format=advanced&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ACCEPTED&bug_status=IN%20PROGRESS%20DESIGN&bug_status=IN%20PROGRESS%20DESIGN%20COMPLETE&bug_status=IN%20PROGRESS%20IMPLEMENTATION&bug_status=IN%20PROGRESS%20REVIEW&bug_status=REOPENED&bug_status=NEEDINFO&product=Security&product=Security%20-%20Recipe%20Upgrade security issues]

* Review Queries
** State number, title, and owner
** Owner makes any modifications
** Assign owner, target milestone, and priority.
* Opens
** Collect opens
** Discuss opens

Note: for Minnowboard or MinnowBoard-MAX bugs go to: [[Minnow Bug Triage]]

= Bug Triage Order =
*[https://bugzilla.yoctoproject.org/buglist.cgi?list_id=604307&resolution=---&query_format=advanced&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ACCEPTED&bug_status=IN%20PROGRESS%20DESIGN&bug_status=IN%20PROGRESS%20DESIGN%20COMPLETE&bug_status=IN%20PROGRESS%20IMPLEMENTATION&bug_status=IN%20PROGRESS%20REVIEW&bug_status=REOPENED&bug_status=NEEDINFO&product=Security&product=Security%20-%20Recipe%20Upgrade Security Issues]
*[https://wiki.yoctoproject.org/wiki/Bug_Triage#Non-Prioritized_Bugs Non-Prioritized Bugs and Non Targeted Bugs]
*[https://bugzilla.yoctoproject.org/buglist.cgi?quicksearch=AB-INT&list_id=620110 Autobuilder issues]
*[https://wiki.yoctoproject.org/wiki/Bug_Triage#High_Enhancements.2FBugs High Enhancements/Bugs]
*[https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium.2B_4.1_Unassigned_Enhancements.2FBugs Medium+ 3.5 Unassigned Enhancement/Bugs]
*[https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium.2B_4.99_Unassigned_Enhancements.2FBugs Medium+ 3.99 Unassigned Enhancement/Bugs]
*[https://wiki.yoctoproject.org/wiki/Bug_Triage#NEEDINFO NEEDINFO]
*[https://wiki.yoctoproject.org/wiki/Bug_Triage#Re-Opened Reopened]
*[https://wiki.yoctoproject.org/wiki/Bug_Triage#Old_Milestone Old Milestone]
*[https://wiki.yoctoproject.org/wiki/Bug_Triage#Future_.26_4.99_Milestones Future & 4.99 Milestones]

* Note/Suggestion for the Weekly Triage Meeting: Open the first link in a new browser window and then each additional link in a new tab in that new window. Close the new window when the triage meeting is done.

= Bug Criteria =
* Priority-Severity
** High: Two Week - shouldn't slip to next milestone without review by Triage team.
** Medium+: Milestone Target Required
** Medium: Nice to have for milestone, should have for release
** Low: Nice to have, but no urgency

* Future bugs and enhancements are a good idea to do, but not able in the near term to get fixed or done.
** If you want to work on them, please talk first to the existing owner or change the ownership to yourself if unassigned or newcomer.
*** Note: we have a special owner - newcomer@yoctoproject.org - which we think would be great opportunities for a newcomer to open source to start learning on.

* Special Case: Medium+ and Future Enhancement or Bug - These are a good idea and important to do, but not currently scheduled at this time.
** If you want to work on them, please talk first to the existing owner or change the ownership to yourself if unassigned or newcomer.
*** Note: we have a special owner - newcomer@yoctoproject.org - which we think would be great opportunities for a newcomer to open source to start learning on.

* For more details see the wiki [[Bugzilla Configuration and Bug Tracking]]

= Bug Status Dashboards =

Weekly - https://wiki.yoctoproject.org/charts/combo.html

Daily - https://wiki.yoctoproject.org/charts/daily/combo.html

= Bug Product Searches =

* [[Bug Product Triage]]

= Yocto Bug Triage Searches =
== Newcomer Bugs ==
{{#bugzilla:
|status=!(RESOLVED,VERIFIED,CLOSED)
|to=newcomer@yoctoproject.org, unassigned@yoctoproject.org
|whiteboard=NEWCOMER
|product=!opkg
|severity=!janitors
|priority=!(Undecided)
|columns=id,summary,to,status,milestone,severity,priority,whiteboard
|sort=id
|noresultsmessage="No matching bugs found. Check for unassigned bugs."
|total=summary
}}

== Non-Prioritized Bugs ==
{{#bugzilla:
|status=!(RESOLVED,VERIFIED,CLOSED)
|priority=Undecided
|product=!(opkg, IoT Reference OS Kit, Toaster, Security Response Tool)
|severity=!janitors
|component=!(meta-cgl, meta-security, bsps-meta-ti)
|columns=id,summary,severity,priority,milestone,to,status,whiteboard,estimated
|sort=id
|noresultsmessage="No matching bugs found."
|total=summary
}}

== Non-Targeted Bugs ==
{{#bugzilla:
|status=!(RESOLVED,VERIFIED,CLOSED)
|severity=!janitors
|product=!(opkg, IoT Reference OS Kit, Toaster, Security Response Tool)
|milestone=---
|component=!(meta-cgl, meta-security, infrastructure-general, bsps-meta-ti)
|columns=id,summary,severity,priority,milestone,to,status,whiteboard,estimated
|sort=id
|noresultsmessage="No matching bugs found."
|total=summary
}}

== New This Week ==
{{#bugzilla:
|created=-1w
|columns=id,summary,severity,priority,milestone,to,status,whiteboard,estimated
|sort=status,id
|noresultsmessage="No matching bugs found."
|total=summary,estimated
}}
== Closed This week ==
{{#bugzilla:
|status=(RESOLVED,VERIFIED,CLOSED)
|modified=-1w
|product=!opkg
|severity=!janitors
|columns=id,modified,summary,severity,priority,milestone,to,status,resolution
|sort=id
|noresultsmessage="No matching bugs found."
|total=summary
}}

== High Enhancements/Bugs ==
{{#bugzilla:
|status=!(RESOLVED,VERIFIED,CLOSED)
|priority=high
|product=!opkg
|columns=id,summary,severity,priority,milestone,to,status,whiteboard,estimated
|sort=milestone,id
|noresultsmessage="No matching bugs found."
|total=summary
}}
== Medium+ 4.1 Unassigned Enhancements/Bugs ==
{{#bugzilla:
|status=!(RESOLVED,VERIFIED,CLOSED)
|priority=!(Undecided,Medium,Low,High)
|milestone=!(3.99, 4.99, 4.1, Q1, Q2, Q3, Q4, future)
|to=unassigned@yoctoproject.org
|product=!opkg
|columns=id,summary,severity,priority,milestone,to,status,whiteboard,estimated
|sort=milestone,id
|noresultsmessage="No matching bugs found."
|total=summary
}}

== Medium+ 4.99 Unassigned Enhancements/Bugs ==
{{#bugzilla:
|status=!(RESOLVED,VERIFIED,CLOSED)
|priority=!(Undecided,Medium,Low,High)
|milestone=4.99
|to=unassigned@yoctoproject.org
|product=!opkg
|columns=id,summary,severity,priority,milestone,to,status,whiteboard,estimated
|sort=milestone,id
|noresultsmessage="No matching bugs found."
|total=summary
}}

== Medium+ Future Unassigned Enhancements/Bugs ==
{{#bugzilla:
|status=!(RESOLVED,VERIFIED,CLOSED)
|priority=!(Undecided,Medium,Low,High)
|milestone=Future
|to=unassigned@yoctoproject.org
|product=!opkg
|columns=id,summary,severity,priority,milestone,to,status,whiteboard,estimated
|sort=milestone,id
|noresultsmessage="No matching bugs found."
|total=summary
}}

== NEEDINFO ==
{{#bugzilla:
|status=NEEDINFO
|columns=id,summary,to,status,severity,priority,milestone,modified,whiteboard
|sort=id
|noresultsmessage="No matching bugs found."
|total=summary
|modifiedformat=date
}}

== Re-Opened ==
{{#bugzilla:
|status=REOPENED
|columns=id,summary,to,status,severity,priority,milestone,whiteboard
|sort=milestone,priority,id
|product=!(opkg, IoT Reference OS Kit)
|severity=!janitors
|component=!(meta-cgl, meta-security)
|noresultsmessage="No matching bugs found."
|total=summary
}}

== Old Milestone ==
{{#bugzilla:
|status=!(RESOLVED,VERIFIED,CLOSED)
|milestone= !(3.1.16, 3.2.5, 3.3.6, 3.4.4, 3.99, 4.0.1, 4.1, 4.1 M1, 4.1 M2, 4.1 M3, 4.1 M4, 4.99, Q1, Q2, Q3, Q4, future)
|product=!(opkg, IoT Reference OS Kit)
|severity=!janitors
|component=!(meta-cgl, meta-security)
|priority= !Undecided
|columns=id,summary,to,status,severity,priority,milestone,whiteboard
|sort=milestone,priority,id
|noresultsmessage="No matching bugs found."
|total=summary
}}

== Future Dot Releases==
{{#bugzilla:
|status=!(RESOLVED,VERIFIED,CLOSED)
|product=!opkg
|milestone= 3.1.16, 3.2.5, 3.3.6, 3.4.3
|severity=!janitors
|priority= !Undecided
|columns=id,summary,to,status,severity,priority,milestone,whiteboard
|sort=milestone
|noresultsmessage="No matching bugs found."
|total=summary
}}

== YP Toaster Bugs==
Please refer to the [[Bug_Triage_Toaster]] Page

== YP Archived Queries==
Please refer to the [[Bug_Triage_Archive]] Page

== YP BSP Team Triage==
Please refer to the [[BSP Team Bug Triage]] Page

== YP Validation and Infrastructure Team Triage==
Please refer to the [[Validation and Infrastructure Team Bug Triage]] Page

== Future & 4.99 Milestones ==
{{#bugzilla:
|status=!(RESOLVED,VERIFIED,CLOSED)
|product=!opkg
|milestone=Future, 4.99
|severity=!janitors
|priority= !(Undecided)
|columns=id,modified,summary,to,status,milestone,severity,priority
|sort=modified,id
|noresultsmessage="No matching bugs found."
|total=summary
}}

== Future & 3.99 Milestones Check ==
{{#bugzilla:
|status=!(RESOLVED,VERIFIED,CLOSED)
|product=!opkg
|milestone=Future, 3.99
|whiteboard=REVIEW, QA, QA REVIEW, OB, OB REVIEW
|severity=!janitors
|priority= !(Undecided)
|columns=id,modified,summary,to,status,milestone,severity,priority,whiteboard
|sort=whiteboard,modified,id
|noresultsmessage="No matching bugs found."
|total=summary
}}

== Quarterly Milestones==
{{#bugzilla:
|status=!(RESOLVED,VERIFIED,CLOSED)
|milestone=Q1,Q2,Q3,Q4
|severity=!janitors
|priority= !Undecided
|columns=id,modified,summary,to,status,severity,priority,milestone,whiteboard
|sort=milestone
|noresultsmessage="No matching bugs found."
|total=summary
}}

File:YPS VIrtualization KVM EU20020.webm

2020-10-30T19:57:31Z

Tim Orling: Booting an unmodified Ubuntu cloud image on the KVM host image.

Booting an unmodified Ubuntu cloud image on the KVM host image.

YP DevDay Austin 2020

2020-10-30T19:55:31Z

Tim Orling: /* Slides */

This page contains slides for the talks in the Yocto Project DevDay Virtual, ELC Austin 2020

Starting at 9:00am, 02 July 2020, Mountain Time.

YP DevDay Virtual home page is here: [https://www.yoctoproject.org/yocto-project-dev-day-virtual-north-america-2020/ https://www.yoctoproject.org/yocto-project-dev-day-virtual-north-america-2020]

== Slides ==

* Presenter Slides

[https://wiki.yoctoproject.org/wiki/File:DD0_Introduction_NA20.pdf DD0_Introduction_NA20.pdf]
[https://wiki.yoctoproject.org/wiki/File:DD0_Introduction_NA20.pptx DD0_Introduction_NA20.pptx]
[https://wiki.yoctoproject.org/wiki/File:DD1_Highly_Scalable_Build_Automation_NA20.pdf DD1_Highly_Scalable_Build_Automation_NA20.pdf]
[https://wiki.yoctoproject.org/wiki/File:DD1_Highly_Scalable_Build_Automation_NA20.pptx DD1_Highly_Scalable_Build_Automation_NA20.pptx]
[https://wiki.yoctoproject.org/wiki/File:DD2_YoctoContainer-handout_NA20.pdf DD2_YoctoContainer-handout_NA20.pdf]
[https://wiki.yoctoproject.org/wiki/File:DD3_Kernel_Lab_NA20.pdf DD3_Kernel_Lab_NA20.pdf]
[https://wiki.yoctoproject.org/wiki/File:DD3_Kernel_Lab_NA20.pptx DD3_Kernel_Lab_NA20.pptx]
[https://wiki.yoctoproject.org/wiki/File:DD5_Security_Hardening_NA20.pdf DD5_Security_Hardening_NA20.pdf]
[https://wiki.yoctoproject.org/wiki/File:DD6_Size-Optimizations_NA20.pptx DD6_Size-Optimizations_NA20.pptx]
[https://wiki.yoctoproject.org/wiki/File:DD7_CI_CD_NA20.pptx DD7_CI_CD_NA20.pptx]
[https://wiki.yoctoproject.org/wiki/File:DD7_CI_CD_NA20.pdf DD7_CI_CD_NA20.pdf]
[https://wiki.yoctoproject.org/wiki/File:DD8_Userspace_Lab_NA20.pptx DD8_Userspace_Lab_NA20.pptx]
[https://wiki.yoctoproject.org/wiki/File:DD9_Devtool_NA20.odp DD9_Devtool_NA20.odp]
[https://wiki.yoctoproject.org/wiki/File:DD9_Devtool_NA20.pdf DD9_Devtool_NA20.pdf]
[https://wiki.yoctoproject.org/wiki/File:DD9_Devtool_NA20.pptx DD9_Devtool_NA20.pptx]
[https://wiki.yoctoproject.org/wiki/File:DD10_Xen_Hypervisor_NA20.pdf DD10_Xen_Hypervisor_NA20.pdf]
[https://wiki.yoctoproject.org/wiki/File:DD10_Virtualization_KVM_Hypervisor_NA20.pdf DD10_Virtualization_KVM_Hypervisor_NA20.pdf]

* Class Movies, example code

[https://wiki.yoctoproject.org/wiki/File:Xen-guest-on-Rpi4.mp4 Xen-guest-on-Rpi4.mp4 (Virtualization)]
[https://wiki.yoctoproject.org/wiki/File:Xen-on-Rpi4.mp4 Xen-on-Rpi4.mp4 (Virtualization)]
[https://wiki.yoctoproject.org/wiki/File:DD10_KVM_guest_on_NUC.mov DD10_KVM_guest_on_NUC.mov]
[https://wiki.yoctoproject.org/wiki/File:Ubuntu KVM guest on NUC (Virtualization)]
[https://wiki.yoctoproject.org/wiki/File:Elc-austin.zip User Space sample source files]

* ELC Austin 2020 presentations

[https://wiki.yoctoproject.org/wiki/File:Yocto_Project_LTS_ELC_NA_June_2020.pptx YP LTS Presentation]

* Slides template

[https://wiki.yoctoproject.org/wiki/File:Yocto_Project_DevDay_NA2020_Template.pptx Yocto_Project_DevDay_NA2020_Template.pptx]

AB layer application

2020-10-08T20:10:17Z

Tim Orling: fix mailng list URL

'''Yocto Project Autobuilder Layer Addition Application Form'''

Name of layer: [ text ]

Explain why this layer should be added to the autobuilder: [ text ]

Describe what will be built on the autobuilder: [ text ]

Is the layer Yocto Project Compatible? [yes / no]
If not, please explain why: [ text ]

Name and email addresses of maintainer(s): [ text ]

Are the maintainers committed to fixing build failures? [ yes / no ]

If build failures are not resolved in a timely manner the layer may be removed from the autobuilder.

Is this addition being made as a membership benefit?: [ yes / no ]

If so, which member and which membership level: [ member ] [ level ]

How many people have contributed to the layer: [ text ]

How long has the layer been in development: [ text ]

What dependencies does the layer have? [ text ]

Layers should ideally have minimal dependencies.

Does the layer include any automated QA tests to run on the autobuilder? If so, please give details: [ text ]

What is the approximate resource impact of this layer of the autobuilder (relative to other build targets, is there a comparable existing target)? [ text ]

Where can bug reports for the layer be filed (e.g. bugzilla): [ text ]

Where are changes to the layer reviewed (e.g. GitHub): [ text ]

Link to the related yocto-autobuilder-helper and yocto-autobuilder2 patches:

Send form to Yocto TSC <tsc@lists.yoctoproject.org>

TSC

2020-10-08T19:56:05Z

Tim Orling: rburton is not Intel anymore :(

=Yocto Project Technical Steering Committee=

The YP TSC consists of 5 people; 3 nominated from Yocto Project Member Organizations (including the chairperson) and 2 from OpenEmbedded.

The TSC has overall responsibility for all technical aspects of the Yocto Project. This includes repositories hosted on https://git.yoctoproject.org/, the associated mailing lists, bugzilla, the testing processes and infrastructure/QA and the releases of the project.

The TSC does not overlap with the OpenEmbedded TSC which is a similar entity with responsibility for the OpenEmbedded Architecture and the OpenEmbedded hosted repositories and infrastructure.

The YP TSC has a two year term limits. Term Started: May 2019

=Members=

* Richard Purdie (Linux Foundation) - TSC Chair
* Khem Raj (Comcast) - YP Membership Elected
* Ross Burton (Arm) - YP Membership Elected
* Armin Kuster - OE Elected
* Denys Dmytriyenko - OE Elected

=Operation=

The TSC is intended to be an entity of last resort, its expected the community will reach consensus decisions and/or individual maintainers will reach solutions in the best interests of the users and overall project. The TSC will therefore only act if these processes have failed and a decision is needed.

Anyone is free to approach any TSC member with any issue or concern who will refer it to the TSC members for discussion. The TSC members will usually try and continue public discussion as much as is practical, any final TSC discussion for a decision will however be by closed session with the aim of quickly reaching decisions which will then be made public.

The TSC will periodically (at least monthly) discuss the project health and direction, aiming to ensure its future success. The TSC is not an engineering organisation so can only pass on recommendations to the community or governing board in this matter although indvidual TSC members may make contributions to the project with these things in mind.

The TSC will make the final go/nogo decisions on releases, based on the release criteria, testing results and any other information available to them.

= Processes =
[https://wiki.yoctoproject.org/wiki/Stable_Release_and_LTS#New_Releases_process, LTS / Stable processes]

[https://wiki.yoctoproject.org/wiki/AB_layer_application#AB_app_form, AB layer application form]

Main Page

2020-08-18T15:54:55Z

Tim Orling: /* Project planning */ add Future_Directions link

== Welcome to the Yocto Project Wiki! ==
The [http://yoctoproject.org Yocto Project] is an open-source project that delivers a set of tools that create operating system images for embedded Linux systems. The Yocto Project tools are based on the [http://www.openembedded.org/wiki/Main_Page OpenEmbedded] (OE) project, which uses the BitBake build tool, to construct complete Linux images. BitBake and OE are combined to form a reference build host known as Poky which includes the following [[Core Components|core components]]. This [https://www.youtube.com/watch?v=utZpKM7i5Z4 video] will help explain what it's all about.

===Where to Start?===
If you're new to Yocto take a look at the '''[[Glossary]]''' so you're familiar with the terms used in this wiki and the project documentation. Then take a look at the [http://www.yoctoproject.org/docs/current/yocto-project-qs/yocto-project-qs.html '''Quick Start Guide''']. You can follow the steps in this document to clone the poky repository, quickly configure your build environment, and then try a build. Corporate firewalls can be problematic so network proxy configurations are detailed on the '''[[Working Behind a Network Proxy]]''' page. We advise you go straight for the [[Working_Behind_a_Network_Proxy#Option_2:_Chameleonsocks| Chameleonsocks option]].

===Where to Next?===
Thanks to the quick start guide, it's pretty easy to get your first Linux image and and running. Here are some places to look for help when improving your Yocto skills.
* The [https://linuxfoundation.org Linux Foundation] have some great [https://docs.google.com/presentation/d/1LmI3mHoD_Dzl8wplIYcUBrFF8BzDb_EadTvfbnpSK7Q/edit training slides]. There is also an [https://docs.google.com/presentation/d/1HoDtyN5SzlmuTN47ab4Y7w_i6c_VEW6EBUD944ntf38/edit#slide advanced slide deck] for more more experienced users.
* The first tool you'll need to get familiar with is '''bitbake''', so reading through the [https://www.yoctoproject.org/docs/current/bitbake-user-manual/bitbake-user-manual.html user manual] is recommended. You don't need to understand it all right now, but bookmark this page for reference. Implementation of bitake is covered in the [[Bitbake Internals Primer]]
* Once you start adding packages and configuring your image to create your own distribution, things can go wrong and it can hard to track down the root cause. There is no shortage of Yocto documentation resource, but if you're not exactly sure what you're looking for this '''[[Documentation Decoder]]''' will help you out. Also take a look at the [https://wiki.yoctoproject.org/wiki/Cookbook '''Cookbook'''] and [https://wiki.yoctoproject.org/wiki/Technical_FAQ troubleshooting guide]. Also [https://www.yoctoproject.org/blogs/jefro/2016/yocto-project-books these books] are helpful.
* Some new tools such as [http://www.yoctoproject.org/docs/current/toaster-manual/toaster-manual.html Toaster], [[Extensible SDK]] and [https://github.com/crops CROPS] are making it easier to get the best out of Yocto on Windows and Mac OS X. Take a look at the new workflow in [[Developer Workflow Improvements]].
* There is also a [https://wiki.yoctoproject.org/wiki/TipsAndTricks '''Tips and Tricks'''] section where more experienced developers contribute to articles that will help those new to Yocto Project.
* You can also read and participate on the [https://lists.yoctoproject.org mailing lists] - start with the [https://lists.yoctoproject.org/g/yocto main list] first - and the [https://www.yoctoproject.org/tools-resources/community/irc IRC channels].

== Project planning ==

=== Features ===
* [[Yocto Feature Summary]] (Current and Next)

=== Project Planning for current release ===

* [[Planning]]

=== Project Status and Schedule ===
* [[Weekly_Status]]
* [[Yocto Project v2.8 Status]]
* [[Yocto 2.8 Schedule]]
* Testresults - https://git.yoctoproject.org/cgit/cgit.cgi/yocto-testresults-contrib/log/?h=intel-yocto-testresults

=== Future Directions ===
* [[Future_Directions]]

== Release Engineering ==

* [[Yocto Release Engineering | Yocto Project Release Engineering]]
* [[Yocto Release Engineering | Release Activity (with status, version info, QA links, etc)]]

== QA & Automation ==

* [[The_Yocto_Autobuilder| The Yocto Project Autobuilder]]
* [[QA| Yocto Project QA Main Page]]
* [[QA/Archive| Yocto Project QA Test Report Archive ]]

== Quick guide for newcomers ==

If you are new to the project and are willing to contribute, please refer to our [[Newcomers|guide for newcomers]].

== TSC ==
* Yocto Project Technical Steering Committee [[TSC]]

== Wiki reference sitemap ==
* [[Glossary]]
* [[Documentation Decoder]]
* [[Working Behind a Network Proxy]]
* [[FAQ]] and [[Technical FAQ]]. These need to be unified.
* [[Cookbook]] and [[TipsAndTricks | Tips and Tricks]]. Need clear messaging on how these should be differentiated.
* [[Developer Workflow Improvements]], including [[Nodejs Workflow Improvements]]
* [[Planning and Governance]]
* [[Community Guidelines]]
* [[Yocto Release Engineering | Yocto Project Release Engineering]]
* [[License Infrastructure Interest Group | License Infrastructure]]
* [[Processes and Activities]]
* [[Technical Contributors]]
* [[Projects]]
* [[Security]] - find out what we do about CVEs and security
* [[Yocto Interest Groups]]
* [[Testopia]] - The Yocto Project's community-opened test case management platform
* [[Toaster]] - the web interface
* [[Archive]] - Graveyard for out of date articles.

== Other resources ==
* [http://yoctoproject.org Yocto Project Front Page]
* [http://git.yoctoproject.org/ Yocto Project Git Source Repos]
* [https://bugzilla.yoctoproject.org/ Yocto Project Bugzilla]
* [https://www.yoctoproject.org/tools-resources/community/mailing-lists Yocto Project Mailing Lists]
* [http://recipes.yoctoproject.org/rrs Yocto Project Recipe Reporting System]
* [https://autobuilder.yoctoproject.org/typhoon Yocto Project Autobuilder]
* [http://downloads.yoctoproject.org/releases/yocto/ Yocto Project Releases Downloads]
* [http://autobuilder.yoctoproject.org/pub/nightly/ Yocto Project Nightly Build Images]
* [http://downloads.yoctoproject.org/mirror/sources/ Upstream Sources Mirror]
* [http://www.openembedded.org/wiki/Main_Page OpenEmbedded Wiki]
* [http://cgit.openembedded.org/ OpenEmbedded Git Repos]
* [http://layers.openembedded.org/ OpenEmbedded Community Layers]
* [http://patchwork.openembedded.org/ OpenEmbedded Patch Tracking System]
* '''IRC''': irc.freenode.net
:* #yocto - Public discussions on the Yocto Project.
:* #oe - Public discussions on OpenEmbedded Core.

File:DD10 Virtualization KVM Hypervisor NA20.pdf

2020-07-02T20:20:29Z

Tim Orling: How to build a Yocto Based image that can host KVM guests.

How to build a Yocto Based image that can host KVM guests.

YP DevDay Austin 2020

2020-07-02T20:16:11Z

Tim Orling: Add Virtualization KVM content.

This page contains slides for the talks in the Yocto Project DevDay Virtual, ELC Austin 2020

Starting at 9:00am, 02 July 2020, Mountain Time.

YP DevDay Virtual home page is here: [https://www.yoctoproject.org/yocto-project-dev-day-virtual-north-america-2020/ https://www.yoctoproject.org/yocto-project-dev-day-virtual-north-america-2020]

== Slides ==

* Presenter Slides

[https://wiki.yoctoproject.org/wiki/File:DD0_Introduction_NA20.pdf DD0_Introduction_NA20.pdf]
[https://wiki.yoctoproject.org/wiki/File:DD0_Introduction_NA20.pptx DD0_Introduction_NA20.pptx]
[https://wiki.yoctoproject.org/wiki/File:DD1_Highly_Scalable_Build_Automation_NA20.pdf DD1_Highly_Scalable_Build_Automation_NA20.pdf]
[https://wiki.yoctoproject.org/wiki/File:DD1_Highly_Scalable_Build_Automation_NA20.pptx DD1_Highly_Scalable_Build_Automation_NA20.pptx]
[https://wiki.yoctoproject.org/wiki/File:DD2_YoctoContainer-handout_NA20.pdf DD2_YoctoContainer-handout_NA20.pdf]
[https://wiki.yoctoproject.org/wiki/File:DD3_Kernel_Lab_NA20.pdf DD3_Kernel_Lab_NA20.pdf]
[https://wiki.yoctoproject.org/wiki/File:DD3_Kernel_Lab_NA20.pptx DD3_Kernel_Lab_NA20.pptx]
[https://wiki.yoctoproject.org/wiki/File:DD5_Security_Hardening_NA20.pdf DD5_Security_Hardening_NA20.pdf]
[https://wiki.yoctoproject.org/wiki/File:DD6_Size-Optimizations_NA20.pptx DD6_Size-Optimizations_NA20.pptx]
[https://wiki.yoctoproject.org/wiki/File:DD7_CI_CD_NA20.pptx DD7_CI_CD_NA20.pptx]
[https://wiki.yoctoproject.org/wiki/File:DD8_Userspace_Lab_NA20.pptx DD8_Userspace_Lab_NA20.pptx]
[https://wiki.yoctoproject.org/wiki/File:DD9_Devtool_NA20.odp DD9_Devtool_NA20.odp]
[https://wiki.yoctoproject.org/wiki/File:DD9_Devtool_NA20.pdf DD9_Devtool_NA20.pdf]
[https://wiki.yoctoproject.org/wiki/File:DD9_Devtool_NA20.pptx DD9_Devtool_NA20.pptx]
[https://wiki.yoctoproject.org/wiki/File:DD10_Xen_Hypervisor_NA20.pdf DD10_Xen_Hypervisor_NA20.pdf]
[https://wiki.yoctoproject.org/wiki/File:DD10_Virtualization_KVM_Hypervisor_NA20.pdf DD10_Virtualization_KVM_Hypervisor_NA20.pdf]

* Class Movies and hands-on text Cheat sheets

[https://wiki.yoctoproject.org/wiki/File:Xen-guest-on-Rpi4.mp4 Xen-guest-on-Rpi4.mp4]
[https://wiki.yoctoproject.org/wiki/File:DD10_KVM_guest_on_NUC.mov DD10_KVM_guest_on_NUC.mov]

* ELC Austin 2020 presentations

[https://wiki.yoctoproject.org/wiki/File:Yocto_Project_LTS_ELC_NA_June_2020.pptx YP LTS Presentation]

* Slides template

[https://wiki.yoctoproject.org/wiki/File:Yocto_Project_DevDay_NA2020_Template.pptx Yocto_Project_DevDay_NA2020_Template.pptx]

File:DD10 Virtualization KVM Hypervsior NA20.pdf

2020-07-02T20:13:29Z

Tim Orling: How to build Yocto Project based image that can host KVM guests.

How to build Yocto Project based image that can host KVM guests.

File:DD10 Virtualization KVM.pdf

2020-07-02T20:04:59Z

Tim Orling: How to create a Yocto Project built image that can act as host for KVM guests.

How to create a Yocto Project built image that can act as host for KVM guests.

File:DD10 KVM guest on NUC.mov

2020-07-02T19:54:51Z

Tim Orling: Ubuntu 20.04 kvm cloud image (completely unmodified in any way) launching.

Ubuntu 20.04 kvm cloud image (completely unmodified in any way) launching.

User:Tim Orling

2018-03-23T04:31:42Z

Tim Orling:

* Co-founder and co-maintainer of meta-python layer.
* Co-founder and co-maintainer of meta-maker layer.
* Co-maintainer of meta-perl layer.
* I also watch for quality of meta-oe and meta-multimedia layers.

I am not really a testing guy. However, I despise tedious repetitive tasks, so I automate everything.

* If you aren't run-time testing, you are fooling yourself.

User:Tim Orling

2018-03-23T04:29:53Z

Tim Orling:

Co-founder and co-maintainer of meta-python layer.
Co-founder and co-maintainer of meta-maker layer.
Co-maintainer of meta-perl layer.
I also watch for quality of meta-oe and meta-multimedia layers.
I am not really a testing guy. However, I despise tedious repetitive tasks, so I automate everything.
If you aren't run-time testing, you are fooling yourself.

File:Crops-poky-mac.txt

2017-10-26T11:44:29Z

Tim Orling: Notes for using the CROPS poky Docker container. Note that this will work with oe-core based workflows as well.

Notes for using the CROPS poky Docker container. Note that this will work with oe-core based workflows as well.

File:Crops-toaster-mac.txt

2017-10-26T11:12:20Z

Tim Orling: Notes for running the CROPS Toaster Docker container (tested on Mac OS X)

Notes for running the CROPS Toaster Docker container (tested on Mac OS X)

File:Hello c.txt

2017-10-26T11:10:42Z

Tim Orling: Simple Hello World program. Rename to "hello.c"

Simple Hello World program.
Rename to "hello.c"

DevDay Prague 2017

2017-10-26T11:06:41Z

Tim Orling: /* Advanced Class */ More CROPS notes

Page for DevDay Prague 2017

Starting at 9:00am, 26 October [https://www.yoctoproject.org/yocto-project-developer-day-europe-2017 More info and tentative schedule]

== Begining Class ==

* Class Slides

[]Beginning Class Slides

* Sample Code

== Advanced Class ==

* Class Slides

[https://wiki.yoctoproject.org/wiki/File:Yocto_DevDay_Advanced_Class_Prague.pdf] Advanced Class Slides (PDF)
[https://wiki.yoctoproject.org/wiki/File:Yocto_DevDay_Advanced_Class_Prague.pptx] Advanced Class Slides (PowerPoint)

* Sample Code

[https://wiki.yoctoproject.org/wiki/File:Event_overlap_py.txt]Sample script 'event_overlap.py'

* Class image set up

[https://wiki.yoctoproject.org/wiki/File:Devdey_class_image_setup.sh.txt]Sample script to prepare up the class image

* Devtool transcript

[https://wiki.yoctoproject.org/wiki/File:devtool.txt] devtool.txt

* CROPS eSDK notes (for Mac OS X)

[https://wiki.yoctoproject.org/wiki/File:crops-extsdk-mac.txt] crops-extsdk-mac.txt

* eSDK sample code

[https://wiki.yoctoproject.org/wiki/File:hello.c] hello.c

* CROPS Toaster notes (for Mac OS X)

[https://wiki.yoctoproject.org/wiki/File:crops-toaster-mac.txt] crops-toaster-mac.txt

* CROPS poky container notes (for Mac OS X)

[https://wiki.yoctoproject.org/wiki/File:crops-poky-mac.txt] crops-poky-mac.txt

File:Crops-extsdk-mac.txt

2017-10-26T10:06:55Z

Tim Orling: Transcript and working notes for CROPS eSDK workflow (on Mac OS X)

Transcript and working notes for CROPS eSDK workflow (on Mac OS X)

DevDay Prague 2017

2017-10-26T10:05:21Z

Tim Orling: /* Advanced Class */ CROPS eSDK notes

File:Devtool.txt

2017-10-25T09:41:20Z

Tim Orling: Tim Orling uploaded a new version of "File:Devtool.txt": typo

Annotated transcript of the activities for the devtool session of Yocto Project Dev Day -- Advanced Class 2017, Prague

File:Devtool.txt

2017-10-25T09:39:54Z

Tim Orling: Annotated transcript of the activities for the devtool session of Yocto Project Dev Day -- Advanced Class 2017, Prague

Annotated transcript of the activities for the devtool session of Yocto Project Dev Day -- Advanced Class 2017, Prague

DevDay Prague 2017

2017-10-25T09:38:30Z

Tim Orling: /* Advanced Class */ add devtool transcript link

Page for DevDay Prague 2017

== Begining Class ==

* Class Slides

[]Beginning Class Slides

* Sample Code

== Advanced Class ==

* Class Slides

[https://wiki.yoctoproject.org/wiki/File:Yocto_DevDay_Advanced_Class_Prague.pdf] Advanced Class Slides (PDF)
[https://wiki.yoctoproject.org/wiki/File:Yocto_DevDay_Advanced_Class_Prague.pptx] Advanced Class Slides (PowerPoint)

* Sample Code

[https://wiki.yoctoproject.org/wiki/File:Event_overlap_py.txt]Sample script 'event_overlap.py'

* Class image set up

[https://wiki.yoctoproject.org/wiki/File:Devdey_class_image_setup.sh.txt]Sample script to prepare up the class image

* Devtool transcript
[https://wiki.yoctoproject.org/wiki/File:devtool.txt] devtool.txt

TipsAndTricks

2017-08-10T03:39:48Z

Tim Orling: /* Ideas for Articles */

== Background ==
This wiki page captures ideas for "Tips and tricks" articles that are aimed Yocto Project users that have a basic understanding of the core tools and want to extend their knowledge. Articles will written and published using the following process
* Articles must refer to the current (or earlier) release. They must not cover features in development in the master branch.
* Anyone can add entries to the '''Ideas for Articles''' section based on challenges they have encountered when using the Yocto Project
* More experienced developers can start to flesh out articles in the ''Ideas'' section move then to '''Articles in Development''' or contribute directly to this section.
* Approximately once a month an article ready for publishing will be chosen for publication by [mailto:jeffrey.osier-mixon@intel.com Jefro] and moved to the '''Finished Articles ''' section.

Please contact [mailto:henry.bruce@intel.com?Subject=Yocto%20Project%20Tips%20and%20Tricks Henry Bruce] with any questions.

== Ideas for Articles ==
* [[TipsAndTricks/GeneratingASDK]] (Ross, Paul help please...)
* [[TipsAndTricks/AddingALicense]] (Ross)
* [[TipsAndTricks/UsingBuildstatsDiff]] (Ross)
* [[TipsAndTricks/DevPyShell]] (Richard Purdie)
* [[TipsAndTricks/CreatingABSP]]. And what not to put in it.
* [[TipsAndTricks/Patchwork]]
* [[TipsAndTricks/Patchtest]] (Leo)
* [[TipsAndTricks/CreateNewLayer]] (Brendan)
* [[TipsAndTricks/LAVAHardwareTesting]] (Tim Orling)
* [[TipsAndTricks/JenkinsPipelinesForContinuousIntegration]] (Tim Orling)

== Articles in development ==
* [[TipsAndTricks/DockerOnImage]] (bavery)
* [[TipsAndTricks/OnTargetWorkFlowLeveragingRPMPackagefeeds]] (bavery)
* [[TipsAndTricks/BuildingAndRunningClearContainersonTarget]] (bavery)
* [[TipsAndTricks/KernelDevelopmentWithEsdk]] (Todor Minchev, Henry Bruce)
* [[TipsAndTricks/DebugNativeRecipeWithGdb]] (Joshua Lock)
* [[TipsAndTricks/Netconsole]] (Ross Burton)
* [[TipsAndTricks/ParsingProfiling]] (Richard Purdie)
* [[TipsAndTricks/DemystifyingTheLinuxYoctoKernel]] (Tom Zanussi)
* [[TipsAndTricks/Patching the source for a recipe]] (Paul Eggleton)
* [[TipsAndTricks/Incorporating closed source components]] (Paul Eggleton)
* [[TipsAndTricks/DebuggingAvoidingRebuilds]] (Richard Purdie)
* [[TipsAndTricks/GitBisectABitbake]] (Ross)
* [[TipsAndTricks/RunningEclipseAgainstBuiltImage]] (bavery)
* [[TipsAndTricks/PrelinkSomePointersAndWorkarounds]] (bavery)
* [[TipsAndTricks/RunningQemuOnMacOSX]] (Stephano)
* [[TipsAndTricks/Understanding what changed (diffsigs etc)]] (Joshua)
* [[TipsAndTricks/CropsCLIContainers]] (bavery)
* [[TipsAndTricks/QuickAndDirtyKernelConfig]] (bavery)
* [[TipsAndTricks/TestingToasterWithContainers]] (bavery)
* [[TipsAndTricks/InvestigatingBuildTime]] (Leo Sandoval)
* [[TipsAndTricks/ResolvingLocaleIssues]] (bavery)
* [[TipsAndTricks/DebuggingBitbakeInPudb]] (bavery)
* [[TipsAndTricks/DebuggingBitbakeInWingIDE]] (bavery)
* [[TipsAndTricks/CliBuildsInToasterBuilddir]] (bavery)
* [[TipsAndTricks/BuildingZephyrImages]] (Henry)
* [[TipsAndTricks/Cmake,Eclipse, and SDKS]] (bavery)
* [[TipsAndTricks/LinuxKernelAndSDKs]] (bavery)
* [[TipsAndTricks/Running YP binaries on Ubuntu and Vice Versa]] (bavery)
* [[TipsAndTricks/LockSharedState]] (Stephano)
* [[TipsAndTricks/Building and booting for Joule or MinnowBoard]] (Cal)
* [[TipsAndTricks/EnablingAPackageFeed]] (Henry)
* [[TipsAndTricks/Creating Recipes for ROS modules]] (Henry)
* [[TipsAndTricks/TeamWorkflows]] (Joshua)

== Finished Articles ==
* [[TipsAndTricks/Packaging Prebuilt Libraries | Packaging Prebuilt Libraries]] (Ross and Henry)
* [[TipsAndTricks/NPM | Packaging Node.js Projects]] (Brendan and Henry)

TipsAndTricks/DebuggingBitbakeInWingIDE

2017-07-26T20:29:51Z

Tim Orling: /* Debug Core Bitbake or a Bitbake Tool */ Fix image link for Remote Debug

= Why =
If you find the pudb environment too bare bones and old fashioned (I do) and wanted a more modern debug experience, you may want to try using the WindIDE debugger: https://wingware.com/. I am pretty sure the same could be done with PyCharm: https://www.jetbrains.com/pycharm/ but I have only done Wing so far. The below assumes you have installed the WingIDE Personal. I used the deb on an ubuntu box.
== Goal ==
I wanted to be able to step through some of the more complex code and see stacks, variables, etc.as well as setting breakpoints. I wanted to be able to do this in bitbake proper aka bitbake/lib/bb/cooker.py for instance, as well as in the metadata e.g. poky/meta/classes/native.bbclass.
 
---
I managed to be able to do both of the above, but not, unfortunately simultaneously. This may be because I have something misconfigured or for some limitation of the debuggers remote connection ability. This is how I set up the 2 scenarios.
=== Debug Core Bitbake or a Bitbake Tool ===
This details how to configure the WingIDE Personal debugger to debug core bitbake (e.g. bitbake/lib/bb/main.py) or a particular tool (e.g. poky/scripts/oe-check-sstate). This is useful if you are trying to understand the program flow or look at some variables w/out adding a bunch of logger.warn(;;;) statements.
* Turn on the Debuggers ability to accept incoming connections . Edit->Preferences->External/Remote. All I did was accept the defaults and hit the checkbox to turn it on. [[File:WingRemoteDebugOn.png|x200px]]
* make a new project
* set the interpreter to be python3 -> 
[[File:WingProjectPython.png|x200px]]
* add the bitbake/bin bitbake/lib and scripts/lib to the project. Right click in the are to the right where the tab says project and select Add Directory.... [[File:WingAddBB.png|x200px]]
* Now you need to help the Source Parser know about the bb libs. Add bitbake/libs and poky/script/libs into the Python Path the IDE knows about. Select Project Properties and add those to the PYTHONPATH. [[File:WingAddBBLibs.png|x200px]]
* You also need to tell the debugger to start in the build directory. By default, it will start in the directory the file you are debugging is in. e.g. bitbake/bin. [[File:WingSetBuilddir.png|x200px]]
* Then you can pull up files and add a breakpoint. In this example I put a bp in oe-check-sstate itself.
* Bring up oe-check-sstate from the poky/scripts and right click to say "Debug this file". This will bring up a dialog box and you can type in the target. For example autoconf-native.
** If Wing doesn't recognize a file as python, you can right click on the file and set the type via File Properties.
* Then you will hit the bp in oe-check-sstate. 
[[File:WingSetBP-check-sstate.png |200xpx]]
* and you can step into tinfoil.py which is in bitbake/lib/bb! 
[[File:WingSetBP-step-tinfoil.png |x200px]]
* You can put bp in any other non meta-data file. You can also start bitbake/bin/bitbake this way and hit the breakpoints...

=== Debug Bitbake Metadata ===
Because the metadata is interpreted as part of bitbake parsing/execution, we need to approach this differently. The below steps worked for me. There may be a better way if someone has more knowledge of the Wing Remote Debug interface. Sometimes, I just want to be able to break in a metadata file and see what is happening and what the state is.
* Make a new project
* First, set up everything as before with respect to the remote debugger, python interpreter, and project properties.
* add the poky/meta directory
* We will bring up the meta/classes/native.bbclass and the poky/meta/recipes-devtools/quilt/quilt-native.inc
** Like we did in the pudb example, we will add some python to the quilt-native.inc file as an example. Add :
<code>
python () {
import sys
import wingdbstub
i=5
for j in range(i):
print("\nCOWZ IN QUILT_NATIVE.INC\n")
print("\n VERSION=",sys.version,"\n")
}
</code>
After the line <code> EXTRA_OECONF = "--disable-nls" </code>
* Note the line <code> import wingdbstub </code>
** this file should be copied from where the Wing IDE install put it (on ubuntu /usr/lib/wingide-personal6) to bitbake/lib. This is so that all the bitbake meta files can easily find it.
** this file tells how to talk to the Wing IDE debugger.
* Now you can pull up files like native.bbclass and quilt-native.inc and put breakpoints in them.
* Here's an example of breaking in native.bbclass: 
[[File:WingBreakNativeMetadata.png|x200px]]
** Caveats:
*** You MUST start bitbake from the command line as normal, with your WingIDE up and running.
*** You will MISS breakoints that are happening in other threads while you are stopped in a particular bp. For instance, if we had breakpoints in quilt-native.inc and in cmake_3.7.2.bb you will probably miss one of them while broke on the other one. For this reason, if you are debugging more than one metadata file at a time, you may need to set the following in your local.conf:
<code>
# FOR Happier WING debugger
# single threaded parsing and building.
# parallel makes are fine...
BB_NUMBER_THREADS="1"
BB_NUMBER_PARSE_THREADS="1"
</code>
* If you go back to debugging bitbake and it is really slow, check to see if you have commented out the above limitations since bb parses VERY slowly with only one thread.

Development Manual Rework

2017-07-14T04:31:34Z

Tim Orling:

= Intro =
This page will propose an outline for [http://www.yoctoproject.org/docs/current/dev-manual/dev-manual.html Development Manual] refactoring work. See also [https://bugzilla.yoctoproject.org/show_bug.cgi?id=11630 bug #11630]

= Henry's Input =
I believe the manual lost its way as it became the dumping ground for useful (and often advanced) info that had nowhere else to land. As a result the size of the manual and top level topics became overwhelming to the new developer who had just graduated from the quick state guide. Currently this user is not served by the Yocto documentation, thus the creation of the wiki [[cookbook]]. Simple tasks such as adding an existing recipe to image and creating a recipe source should be the bread and butter of the development manual. If this approach makes the development master server too many master, we should dicuss re-structing all the docs the addition of a new one.

== Basic "How To" Topics ==
I plan to structure these, but just a plain list for the time being. Many of these topics are already documented, but this feels like a better flow that we have just now.
=== Basic Skills for Systems Developers ===
* Deal with corporate proxies.
* Add a package to an image
* Understand the difference between a recipe and package
* Build a package by itself and why that's useful
* Find out what packages are created by a recipe
* Find out what files are in a package
* Find out what files are in an image
* Add an ssh server to an image (enable transferring of files to target)
* Anatomy of a recipe
* How to find recipes (layers.openembedded,org)
* Understand difference between machine and distro settings
* How to find and use the right BSP (machine) for your hardware
* Examples of distro features and where to set them.
* Understanding the task pipeline and executing individual tasks
* Understand devtool and how it simplifies your workflow
* Improve build speeds with shared downloads and shared state cache
* Generate and understand dependency graph
* Generate and understand bitbake environment
* Building an Extensible SDK
=== Basic Skills for Application Developers ===
* Understand intent and content of extensible SDK (eSDK) and why traditional SDK is no longer necessary
* Understand CROPS eSDK container solution
** Source code is edited outside of container using tools of your choice on host
**
* Install and run CROPS/eSDK
* Intro to devtool
* Make sure you're up to date
* Build the image (may not be the same as on your target) and typical options for flashing it
* Modify an existing recipe
** Understand how git is managing source code
** Build and deploy modified recipe
** Using devtool finish to create updated recipe and patches.
** Understand how this is done without updating upstream source code
* Add a new recipe
** Create recipe from source code
** Review recipe to see what's missing
** Repeat steps as for 'modify'

= Tracey's Input =
The way Henry described this yesterday, customers use the "getting started" guide to learn how to bring up a vanilla image, but then don't know how to approach their own custom situation. This should be a TRANSITION DOCUMENT - how to use YP once you have gotten your feet wet in a controlled situation. Feel free to delete this, I don't know how you folks work in the WIKI and I'm assuming this may not be it.

I would suggest organizing this in a couple of ways - and this might be better in a google doc, frankly.
1) by what people need to do to get started
a) where to start to support a platform
1. find a BSP and test it
b) how to add support for platform components
c) how to slim down an image size
1. Remove code automatically included
2. design your own BSP fine tuned to exclude extra code, unneeded support code
d) How to approach setting up a development environment
e) How use layers to create a flexible long term design, and recipes
d) How do you start a new project vs build off an existing one
e) How do you set up a team sharable development environment (sstate)
f) Here are some of the most common commands
g) How to deal with CVEs and code branches

2) By helping them collect the information they need in order to make set up decisions
Brent had a great idea to make this a SW Wizard that would step a new user through a series of questions and give them at least one solution on how to proceed.
a) what platform are you using
b) will you include an application as part of the image or will it run on the image
c) what is the configuration of the team (system developers, app developers, etc)
c) How to help them choose the right kernel
d) etc.

= Scott's Input =

Scott Rifenbark - This is a good idea. I was thinking of a similar way to deal with this with sort of a decision tree at the end of the YP Quick Start (flowchart for old-schoolers) that would lead the reader down a path based on information they have about what they want to get accomplished. Then, based on how they traverse the tree, we point them to areas they need to use in the manual.

== Notes for Chapter 1 of the dev-manual: ==

I re-wrote this introductory section to work more tightly with the introductory material of the ref-manual. Also, created a better "Other Information" section to lead the reader to various places of interest. In particular, I am leveraging off the Yocto Project Backgrounders that exist on the YP Website. These backgrounders are probably the best place for an overall introduction to what the YP is supposed to be and do for you.

== Notes for Chapter 2 of the dev-manual: ==

This chapter has been renamed "Getting Started With the Yocto Project". It is going to be a collection of beginning type procedures. It now has "Setting Up the Development Host to Use the Yocto Project", "Working With Yocto Project Source Files", "Performing a Simple Build", and "Using Pre-Built Binaries and QEMU". This last section likely will be moved. I do not know what the importance is we are placing on using pre-built binaries. We pulled the section from the Quick Start a long time ago and this section was the boiled up version that mirrored it in the dev-manual.

There are two sections that need flushed out that are impacted by the use of CROPS. One, is to set up the system for CROPS, which seems to be the preferred method now. The other is for setting up a native Linux machine, which will cover the distribution compatibilities and the host package stuff.

== Notes for Chapter 3 of the dev-manual: ==

This chapter was mostly reference material. The entire chapter has been converted now to procedures by pulling out the reference stuff and placing it into the ref-manual. What is left in Chapter 3 are procedures related to setting up a shared YP development environment, submitting a defect, and submitting a change.

=== Section 3.1 - "Open Source Philosophy" ===

I moved this section to the ref-manual. It now is in a chapter called "The Yocto Project Development Environment". That new chapter in the ref-manual is really the old "Closer Look" chapter now with some YP development environment concepts placed on top in their own subsections.

=== Section 3.2 - "Using the Yocto Project in a Team Environment" ===

I have converted this section to a procedure. I need more information on this section from the team. Emails are out soliciting input.

=== Section 3.3 - "Source Repositories" ===

This section has been moved to the ref-manual under "The Yocto Project Development Environment" section. No procedures here except perhaps "Locating the Yocto Project Source Repositories".

=== Section 3.4 - "Terms" ===

This section has been moved to the ref-manual into the "Introduction" chapter. All links throughout the YP Documentation Manual set have been adjusted to work for the new location.

=== Section 3.5 - "Licensing" ===

I moved this section to the ref-manual under "The Yocto Project Development Environment". There are no possibilities of procedures in this section. It is pure reference material.

=== Section 3.6 - "Git" ===

The concepts and overview of how Git works is best suited for the ref-manual. I moved the concepts of Git to the ref-manual. In doing so, I decided to keep the two small examples in that section there just for completeness. However, I created a new section in the dev-manual called "Working With Git Repositories" that has pointed procedures that show the reader how to clone poky, check out a branch based on a poky branch name, and check out a branch based on a poky tag. Right now in the "Getting Set Up" section but will likely be moved as the new dev-manual gains more procedures.

=== Section 3.7 - "Workflows" ===

I have moved this section to "The Yocto Project Development Environment" section in the ref-manual. The section is concepts only.

=== Section 3.8 - "Submitting a Defect Against the Yocto Project" ===

I have reworked this section and it is done. It will live in the dev-manual.

=== Section 3.9 - "How to Submit a Change" ===

I have re-worked this section into a couple of procedures.

== Notes for Chapter 4 of the dev-manual: ==

This whole section is about various workflows. The information is a mix of concepts, high-level workflow steps, and various details associated with the flows. The chapter is now gone from the dev-manual. I took all conceptual information out and it has landed in the ref-manual. I took out all stand-alone sections and set them up as individual sections in the "Common Tasks" chapter. I took the workflows and dropped them into the appropriate other development manuals. Devtool, in particular, now lives in the sdk-manual. The sections on devtool between the dev-manual and the sdk-manual were 99.9% identical. This will fix that Henry bug.

= Tim's input =

== First Steps for a Real Project (Intermediate) ==

The two biggest ideas I find missing in teams new to Yocto Project are:
* Step 1: create a distro layer
** Add your own branding to it
** Add your own image recipe and starting adding packages your team needs/wants
*** When in doubt, '''require''' another base image recipe and then add to it.
*** Stop adding '''IMAGE_INSTALL_append''' to your '''local.conf''', put it in your new image recipe.
* Step 2: create one or more application/functional layers
** '''devtool finish''' all your custom recipes to these layers (unless they are upstream intent)

I honestly recommend this (usually as a course correction) to every single team with which I engage. It is clearly not intuitive.

== Layers are like LEGOs(TM)(R) ==
=== Keep your "git" working directories clean ===
* Do not create your new layers as children of '''poky'''.
** Create them as siblings, this way they can work with '''oe-core''' only and also anyone else's layers.
** Ship your layers as git repos, not a zipped '''poky''' fork.
* Create your build directories as siblings of '''poky''', not children.
* Do not force users of your init script (e.g. '''oe-init-build-env''') to conform to your concept of the location for their build directory! '''HUGE PET PEEVE'''. This makes we want to abandon your layer ''immediately''.
* Do not force users of your distro layer to conform to your concept of what their '''bblayers.conf''' should be. Let them put their layers where they want them to be!
* Any layer ''should'' be able to be picked up and dropped in line with any other layer and not interfere.
* Do not assume everyone is using '''poky'''.

''(TM) and (R) indicate trademarks of the LEGO Group''

TipsAndTricks/RunningEclipseAgainstBuiltImage

2017-01-13T22:34:13Z

Tim Orling: /* Other Useful Info */

= Cookbook guide to Making an Eclipse Debug Capable Image =
Suppose you are building images and would like to be able to use Eclipse and the Yocto Eclipse plugin to develop/debug a C/C++ application on either a remote hardware target or on qemu. This cookbook will explain the small number of steps needed to accomplish this.
 
So that the commands are specific and can be cut and pasted to try, we will assume the following:
* Target Image-> core-image-sato-sdk
** see section[[#Why SDK Image]] for why you have to build the sdk image and how to work around it if you really don't want to.
* Target Machine -> qemux86
 
=== Making a Suitable Qemux86 Image===
* We need to build a core-image-sato-sdk that has the pieces needed by Eclipse, so we add/change the following in our conf/local.conf:
** We add the following to EXTRA_IMAGE_FEATURES in conf/local.conf
*** <code>EXTRA_IMAGE_FEATURES += " eclipse-debug "</code>
**** This adds gdbserver,tcf-agent (for Target Communication Framework), and openssh-sftp-server)
*** <code>EXTRA_IMAGE_FEATURES += " tools-sdk "</code>
**** This adds the build requirements on the target rootfs. This is needed since the Yocto Eclipse plugin is assuming that the qemu rootfs and the sysroot are synonymous.
*** <code>EXTRA_IMAGE_FEATURES += " ssh-server-openssh "</code>
**** This defaults to the openssl ssh server rather than dropbear. You can use either so this line can be omitted since the sftp server works with either.
** Execute: <code> $bitbake core-image-sato</code>
*** This makes a rootfs in tmp/deploy/images/qemux86/core-image-sato-qemux86.tar.bz2
* We need to build the toolchain eclipse will use
** Execute <code> $bitbake core-image-sato -c populate_sdk </code>
*** This makes sdk stuff such as the toolchains eclipse will use to build,
* We need to build a version of qemu that can run natively on our workstation as well as a userspace nfs daemon.
** Execute <code> $bitbake meta-ide-support </code>
* We need an extracted rootfs that can be used by the userspace nfs daemon to boot qemu.
** Execute <code> $mkdir MY_QEMU_ROOTFS </code>
*** Execute <code> $runqemu-extract-sdk tmp/deploy/images/qemux86/core-image-sato-qemux86.tar.bz2 MY_QEMU_ROOTFS</code>
**** This will result in a fully extracted rootfs in MY_QEMU_ROOTFS and a set of permissions maintained by pseudo (a yocto tool similar to but more functional than fakeroot) for the rootfs in MY_QEMU_ROOTFS.pseudo_state

=== Running Eclipse Against the Built Qemux86 Image ===
This Cookbook assumes you have already installed the Eclipse Poky plugin following the directions in http://www.yoctoproject.org/docs/latest/sdk-manual/sdk-manual.html. Assuming that is true, you can
==== Set up the Configuration For the Built Image ====
* Goto Windows->Preferences->Yocto Project SDK
** Select Build System Derived Toolchain
** enter Toolchain Root Location: <build dir>
*** this is where you have been running bitbake core-image-sato, bitbake etc.
** enter Sysroot Location: <path>/MY_QEMU_ROOTFS
*** this is where you extracted the core-image-sato-qemux86.tar.bz2 to by running runqemu-extract-sdk
** enter Qemu/Kernel: <path>/tmp/deploy/images/qemux86/bzImage-qemux86.bin
*** this is the kernel we built
** You should now see i586-poky-linux in the Target Architecture dropdown list.
** hit apply and ok

=== Alternatively, Downloading what we need for Qemux86===
Sometimes, you may not want to build everything yourself but just want to download what you need. These instructions will target the Yocto 2.1 release, but you should be able to translate it into other releases pretty easily.
* Download the image http://downloads.yoctoproject.org/releases/yocto/yocto-2.1/machines/qemu/qemux86/core-image-sato-sdk-qemux86.tar.bz2 Note, the image MUST be an SDK image. Images without sdk in the name will NOT work.
* Download the toolchain: http://downloads.yoctoproject.org/releases/yocto/yocto-2.1/toolchain/x86_64/poky-glibc-x86_64-core-image-sato-i586-toolchain-2.1.sh Note, the toolchain must NOT be one with -ext in the name. The ext toolchains are for the extensible SDK which is useful for CLI and recipe development but which is not currently compatible with Eclipse.
* unpack the toolchain to a dir by running the shell script file you downloaded:
<code>$chmod a+x poky-glibc-x86_64-core-image-sato-i586-toolchain-2.1.sh </code>
<code>$sh poky-glibc-x86_64-core-image-sato-i586-toolchain-2.1.sh </code>
 
This will put the toolchain in /opt/poky/2.1 by default.
* source the toolchain environment file
<code> $source environment-setup-i586-poky-linux </code>
* extract the image you downloaded so that Qemu can use it
<code> $runqemu-extract-sdk core-image-sato-sdk-qemux86.tar.bz2 MY_QEMU_ROOTFS </code>
* Downloads a kernel Qemu can use to boot: http://downloads.yoctoproject.org/releases/yocto/yocto-2.1/machines/qemu/qemux86/bzImage-qemux86.bin

=== Running Eclipse Against the Downloaded Image ===
This Cookbook assumes you have already installed the Eclipse Poky plugin following the directions in http://www.yoctoproject.org/docs/latest/sdk-manual/sdk-manual.html. Assuming that is true, you can
==== Set up the Configuration For the Downloaded Image====
* Goto Windows->Preferences->Yocto Project SDK
** Select Standalone pre built toolchain
** enter Toolchain Root Location: /opt/poky/2.1
** enter Sysroot Location: <path>/MY_QEMU_ROOTFS
*** this is where you extracted the core-image-sato-qemux86.tar.bz2 to by running runqemu-extract-sdk
** enter Qemu/Kernel: bzImage-qemux86.bin
*** this is the kernel you downloaded
** You should now see i586-poky-linux in the Target Architecture dropdown list.
** hit apply and ok

=== Run Qemu ===
* goto <code> Run->External Tools-> External Tools Configurations... </code> and select qemu_i586-poky-linux (in our example; in general it will be architecture-distro-os)
** click Run - this will bring up a Qemu instance.
==== Put the binary on the Qemu instance and debug it ====
* goto <code>Run->Debug Configurations...</code> and select your project (looks like hello_gdb_i586-poky-linux in our case if you named the project hello)
* make a new connection - I prefer SSH so I'll show that here. TCF should also work.
** Click New... on Connection line
** put 192.168.7.2 (probably, look at the end of the qemu xterm that launched and find ip=192.168.7.XX::192.168.7.XX-1 ) in the Host name
** name it
** click finish
* Browse to where the prog will go. I tend to use /home/root.
** Remote Absolute File Path for C/C++ Application -> click Browse...
** Goto Root->/->home->root remember the user is root and the password is empty by default.
** double click root
** click ok
* click Apply
* click Debug and open the Debug Perspective.

== Other Useful Info ==
=== Why SDK Image ===
The current poky-eclipse plugin mashes together 2 concepts that should have been disjoint: namely, the target sysroot and the rootfs image qemu will boot. Under <code> Window->Preferences->Yocto Project SDK </code>, you choose a sysroot location. Up above I told you to point this to the MY_QEMU_ROOTFS you extracted with runqemu-extract-sdk. This will work, but only if you have built the sdk image. If you built the core-image-sato instead, then the MY_QEMU_ROOTFS will be missing a lot of important development files like stdio.h...
==== How to Work around this ====
Let's say you build core-image-sato (this is a standin for your particular image that can't have the sdk parts tossed in for some reason). You can still use eclipse and qemu. You need to do the same things as above with the following changes:
* <code>Sysroot in Window->Preferences->Yocto Project SDK </code> points to <builddir>/tmp/sysroots/qemux86-64. This will give the build system access to the development files it needs.
* In the dialog for <code> Run->External Tools-> External Tools Configurations... </code> you will need to read the long Argument string in the big box. It will have something like <code> -e "source env-setup-<sdkarch>; runqemu <kernel path> <rootfs path> </code> Because the current plugin munges the sysroot and qemu image concepts, the <rootfs path> will incorrectly be pointing to your sysroot. Just delete the <rootfs path> and put in the ABSOLUTE path to the MY_QEMU_ROOTFS you extracted with the runqemu-extract-sdk tool. This way, you can build & debug the image even if it's not an sdk image.

=== Adding static tap devices ===
It is often easier to preconfigure several tap devices so that qemu can run and use them without needing to be root or use sudo. To do this, run <code> runqemu-gen-tapdevs `id -u <username>` `id -g <username>` 4 `find ./tmp/sysroots -iname tunctl`</code> as root. This will make the inet devices tap0,tap1,tap2,tap3. You can see them with <code> ifconfig -a | grep tap </code>. Typically, tap0 is 192.168.7.1 and so when the first qemu is run it's address will be 192.168.7.2 and 192.168.7.1 will be that qemu instance's gateway. The runqemu-gen-tapdevs is located in bitbake/scripts.

scripts/runqemu-gen-tapdevs

=== Switching autotools C/C++ project from one toolchain/sysroot to another and build failing===
Sometimes you will have an existing project and want to switch to a different toolchain or sysroot or machine (x86->x86-64 for instance). If you find that you are getting errors like <code>install-sh not found</code> it may mean that your autotools files have gotten out of sync. Here's how you can force them back. All of these are found by Right clicking on the project and going to Invoke Autotools->:
<code> Invoke Libtoolize option = "--force"</code>
<code> Invoke Aclocal</code>
<code> Invoke Autoheader</code>
<code> Invoke Automake option = "--force-missing --add-missing"</code>
<code> Invoke Autoconf</code>
Then Right click on the project and select <code> Reconfigure Project </code>. You should now be able to build the project again.

=== Dealing with java.lang.NullPointerException ===
Eclipse upstream has some issues with *some* of the GTK3 libraries shipped with some of the distributions(https://bugs.eclipse.org/bugs/show_bug.cgi?id=430736). If you are seeing a NullPointer Exception try adding the following to your eclipse.ini file:
<code>
--launcher.GTK_version
2
</code>

Here's an in place snippet of a happy ini file:
<code>
-showsplash
org.eclipse.platform
--launcher.XXMaxPermSize
256m
--launcher.defaultAction
openFile
--launcher.GTK_version
2
--launcher.appendVmargs
-vmargs
</code>
Alternatively, you can set
<code>
$export SWT_GTK3=0
</code>
But this might affect other programs as well.

=== XWayland workaround with <code>gtk3</code> (Fedora-25) ===

If you see bizarre screen layout of controls in Eclipse Neon, it is probably because the Neon (4.6.x) release of Eclipse is not fully compatible with straight Wayland.

Fedora-25 now has Wayland by default. To enable the XWayland backend:

<code>export GDK_BACKEND=x11</code>

This will still use gtk3, but will use the XWayland bridge rather than straight Wayland. This is expected to be fixed in the Oxygen (4.7) release of Eclipse to support straight Wayland.(https://bugs.eclipse.org/bugs/show_bug.cgi?id=496923)

Thanks to Roland Grunber (Red Hat Linux Tools team) for pointing me in the right direction on #fedora-linux (freenode IRC).

[Source] https://coffeeorientedprogramming.com/2016/10/06/make-applications-eclipse-use-x11-backend-on-wayland-fedora-25/#more-502

==== How to know what version of <code>gtk</code> is being used in your session? ====
<code>Help -> About -> Installation Details -> Configuration Tab</code>

Look for something like:

<code>org.eclipse.swt.internal.gtk.version=3.22.6</code>

[Source] https://coffeeorientedprogramming.com/2014/10/27/how-to-tell-if-you-are-running-eclipse-on-gtk2-or-on-gtk3/

==== How do you know you are running Wayland? ====
<code>loginctl</code> which should show you a list of sessions, one of which will be <code>gdm</code>, remember that session number.

<code>loginctl show-session <session number from above> -p Type</code>

Result should be:

<code>Type=wayland</code>

[Source] http://unix.stackexchange.com/questions/202891/how-to-know-whether-wayland-or-x11-is-being-used

TipsAndTricks/RunningEclipseAgainstBuiltImage

2016-08-18T00:38:05Z

Tim Orling: /* Making a Suitable Qemux86 Image */