nyuuzyou/wikis huggingface dataset:
Legacy staging

The term "legacy staging" refers to recipes or classes which have a do_stage function for populating the sysroot directories that we use for building, rather than having a do_install that works, along with post install functions to mangle the contents as needed.
In OpenEmbedded-Classic, legacy staging was deprecated but still supported; but with OE-Core, BitBake will error out during parse if it finds a do_stage function defined in any recipe, so when migrating a recipe you will need to translate this if present.
Steps for moving script code in the do_stage function to the do_install function:
# Move the lines in do_stage to do_install, deleting anything that is already handled in the existing do_install
# Replace STAGING_BINDIR with ${D}${bindir}
# Replace STAGING_INCDIR with ${D}${includedir}
# Replace STAGING_LIBDIR with ${D}${libdir}
# Replace STAGING_DATADIR with ${D}${datadir}
LinuxTag

== LinuxTag 2011 ==
* takes place in Berlin, Germany
* May 11th to 14th 2011
* LinuxTag is Germany's biggest F/OSS event
* Berlin is supercool and quite cheap
== Manning ==
You are going to LinuxTag and can spend some time at the OpenEmbedded stand to explain interested individuals the virtues of OpenEmbedded? Add your name and on which day you'll be available.
* Florian Boor
* Robert Schuster (will definitely be there)
* Henning Heinold (occassionally, can jump in so that other people can take a break)
* Bernhard Guillon
* <your name here>
== Yocto/oe-core ==
* be informed of what will come
* oe-core/layers bsp's
== Booth support material ==
* power extensions and converters
* TFT screen
* transport box
* SD cards and reader
* WIFI AP in managed mode (provide wired network to embedded devices)
== Marketing material ==
* Flyer availability?
* Poster availability?
 - Poster needs to be updated
 - where are poster sources?
* embedded devices to show (+ what is running on them)
 -
 -
 -
* booth presentation slideshow
 - Robert Schuster made one for CeBIT, will update it and bring it to the event
* OE booth demo image
List of Executable tasks

Bitbake executable tasks
Usage: bitbake -c <task> <module>
For an updated list for a specific recipe, run:
bitbake -c listtasks <recipe>
* fetchall Fetch all source
* build
* devshell
* package_write_ipk
* cleansstate Clean the build/sstate-cache directory
* configure
* clean clean $WORKDIR
* cleanall clean $WORKDIR and sstate-cache
* populate_lic
* package_write
* populate_sysroot
* buildall
* populate_lic_setscene
* patch
* listtasks list all tasks that can be run for a target
* compile
* package_setscene
* fetch
* checkuri
* package_write_ipk_setscene
* package
* unpack
* install
* populate_sysroot_setscene
* checkuriall
Logo

The SVG version of the logo can be found in the OpenEmbedded Core git repo: https://git.openembedded.org/openembedded-core/plain/contrib/artwork/oe.svg
The OpenEmbedded Logo uses the following colors:
 OpenEmbedded Logo Colors
Color	HTML 	RGB 	HSV
Grey 	#5C6F7B	92,111,123	203°,25.2%,48.2%
Blue 	#00BCE4	0,188,288 	191°,100%,89.4%
The font used is currently unknown
Mailing lists

Email address of list 	Purpose 	Subscribe and view archives
openembedded-core@lists.openembedded.org 	General discussion & patch submission for OE-Core 	join+archives
openembedded-devel@lists.openembedded.org 	General discussion & patch submission for other meta layers 	join+archives
openembedded-architecture@lists.openembedded.org	Discussions about overall OpenEmbedded Architecture and Status	join+archives
openembedded-commits@lists.openembedded.org 	Git commits 	join+archives
bitbake-devel@lists.openembedded.org 	Bitbake developers mailing list 	join+archives
openembedded-users@lists.openembedded.org 	User discussion (defunct - use openembedded-devel) 	archives
openembedded-issues@lists.openembedded.org 	Bug tracker status updates (defunct) 	archives
openembedded-stablebranch@lists.openembedded.org	Discussion about the stable branch (defunct) 	
* denotes a searchable archive including an interactive tree view for threads (might not work with all types of browsers)
Category:Community
Membership

Development in OpenEmbedded or any of it's sub-projects does not require membership in OpenEmbedded. However, membership does provide some benefits:
* Voting in elections for the OpenEmbedded board
* Voting in elections for the OpenEmbedded Technical Steering Committee
* Voting in elections for the 2 OpenEmbedded seats in the Yocto Project Technical Steering Committee
* Can join the OpenEmbedded mailing list for members
Membership is free
New members are voted on by the existing membership. This is mostly a formality, but members do want relevant information about yourself (to make sure you are a real person, have relevant interest in OE, and would be a good member). To that end, email [board@openembedded.org] with a request to join and why members should want to vote you in. Feel free to use this template:
* A link to [linkedin] or brief CV 
* Embedded work you've done or plan to do
* Anything else members might wish to know
Membership process:
# email the board with the above
# board will communicate with members to vote on you joining
# board will communicate results to you (2-4 weeks turn around time)
Mirrors

Category:Dev
OpenEmbedded git repositories have following mirrors:
bitbake:
# 	Clone URL 	Supported proto	Web interface 	Comment
1.	git://git.openembedded.org/bitbake 	git, ssh 	http://cgit.openembedded.org/cgit.cgi/bitbake/	master git repo (used by developers to push changes only)
2.	https://github.com/openembedded/bitbake.git	https 	https://github.com/openembedded/bitbake 	git mirror for users to pull from
openembedded-core:
# 	Clone URL 	Supported proto	Web interface 	Comment
1.	git://git.openembedded.org/openembedded-core 	git, ssh 	http://cgit.openembedded.org/cgit.cgi/openembedded-core/	master git repo (used by developers to push changes only)
2.	https://github.com/openembedded/openembedded-core.git	https 	https://github.com/openembedded/openembedded-core 	git mirror for users to pull from
meta-openembedded:
# 	Clone URL 	Supported proto	Web interface 	Comment
1.	git://git.openembedded.org/meta-openembedded 	git, ssh 	http://cgit.openembedded.org/cgit.cgi/meta-openembedded/	master git repo (used by developers to push changes only)
2.	https://github.com/openembedded/meta-openembedded.git	https 	https://github.com/openembedded/meta-openembedded 	git mirror for users to pull from
openembedded (OpenEmbedded-Classic)
# 	Clone URL 	Supported proto	Web interface 	Comment
1.	git://git.openembedded.org/openembedded 	git, ssh 	http://cgit.openembedded.org/cgit.cgi/openembedded/	master git repo (used by developers to push changes only)
2.	https://github.com/openembedded/openembedded.git	https 	https://github.com/openembedded/openembedded 	git mirror for users to pull from
MotorolaEzx

The Motorola EZX devices are a family of PXA2xx-based smartphones shipping with a Linux 2.4 kernel. The OpenEZX project is delivering a modern Linux 2.6 kernel for these devices. Targets in OE are:
* E680
* A780
* A910
* A1200
* ROKRE2
* ROKRE2
Motorola EZX support in OE is maintained by Michael 'Mickey' Lauer and others from the OpenEZX team.
Category:machine
NTP

NOTE: This page is a work in progress.'''
When building ntp for use within an image produced from OpenEmbedded there is an important concern with regard to setting the default server(s) used for time synchronisation.
From http://www.pool.ntp.org/en/vendors.html:
 You must absolutely not use the default pool.ntp.org zone names as the default configuration in your application or appliance.
Once you have gone through the process of setting up / obtaining appropriate server address(es) - refer to the pool.ntp.org vendor info page - you can use these in your OE configuration. To do this, use a bbappend for the ntp recipe in your own layer providing ntp.conf and/or ntpdate.default with the appropriate servers set within.
New Bitbake Syntax Brainstorm

NOTE: This page is only intended for brainstorming bitbake syntax changes and is not an official description of anything will be done
Example 	Expands To 	Description
FOO += "bar" 	FOO_defvar_append = " bar" 	Append " bar" to the default value
FOO ??= "bar" 	FOO_weakval = "bar" 	Set the weakest override value to "bar"
FOO_append = "bar" 	FOO_append = "bar" 	Append "bar" to any value of FOO
FOO_o_append = "bar"	FOO_o_append = "bar" 	Append "bar" to FOO_o
FOO_append_o = "bar"	FOO_append_o = "bar" 	Append "bar" to any value of FOO if o is in OVERRIDES
FOO_o += "bar" 	FOO_o_defvar_append = " bar"	Append " bar" to the default value of FOO_o
OE-Core Standalone Setup

OpenEmbedded-Core is a base layer of recipes, classes and associated files that is meant to be common among many different OpenEmbedded-derived systems and forms the basis of the new structure for OpenEmbedded. See the OpenEmbedded-Core page for more information.
== Getting started ==
1) Clone the repositories for OE-Core (the core metadata) and BitBake (the build tool), checking out the latest stable branches of each one in turn:
git clone git://git.openembedded.org/openembedded-core oe-core
cd oe-core
git clone git://git.openembedded.org/bitbake bitbake
2) Check out the latest stable branches of both OE-Core and BitBake:
git checkout hardknott
cd bitbake
git checkout 1.50
cd ..
3) Set up the environment and build directory:
source ./oe-init-build-env [<build directory>]
The optional build directory may be specified, otherwise it is assumed you want to use the directory named "build".
4) First time configuration
The first time you run oe-init-build-env, it will setup the directory for you and create the configuration files conf/bblayers.conf and conf/local.conf. You should at least review the settings within the conf/local.conf file.
5) Build something:
bitbake <target>
A good simple place to start is bitbake core-image-minimal. This will do basic system sanity checks and build a small but practical image. If your system needs additional software installed, or other environment settings it will tell you what is needed.
OEDAM 2016

== Location and Time ==
Friday April 8 2016 
Catamaran Resort & Hotel
3999 Mission Boulevard
San Diego, CA 92109
858-539-8727
transportation will be provided, TBA
(after ELC [Apr 4-6] and Yocto Project Developer Day [Apr 7])
NOTE: this event is NOT going to be at the Marriott Marquis as previously announced
== Attendees ==
Armin Kuster (Armpit)
Behan Webster (behanw)
Denys Dmytriyenko (denix)
Jan-Simon Möller (dl9pf)
Philip Balister (Crofton|work)
Sean Hudson (darknighte)
Tim Orling (Moto-timo)
Trevor Woerner
Tom King (ka6sox)
Mark Hatle (fray)
Jeff Osier-Mixon (jefro)
Frederick Ollinger (Follinge)
Rudolf Streif (rstreif)
Gratian Crisan
Alejandro Hernandez (aehs29)
Belén Barros Pena (belen)
Scott Murray (smurray)
Koen Kooi (koen)
George McCollister (georgem)
Michael Halstead (halstead) morning only
== Agenda Items ==
* Is there a better name for this meeting that would make it easier for people to get funding to attend?
* Review items from last meeting in Dublin (Please add remarks)
===BSPs & Layer Index===
* oe driving toward machine readable files, can also drive from layer
test (yp compat) side - KK
* publicize defs of each list? discuss on members list - where to
overall architecture discussions belong
* TSC to add new mailing list specifically about project
architecture, no patches, and determine list name [Done]
* KK bring discussion to new mailing list
===BSP standards - standards exist,coming soon are methods for comparing===
a given layer with the standard
* need wiki documentation for TSC to ratify
* document distro vs. machine policies, other best practices
===BSP layer availability===
* encourage board vendors to provide a BSP, make it easier to do so
* ask yp ab to talk to linux.com [PB] - community issue
* look at digi manual (i.e. "just add bsp changes in local.conf"):
===meta-yocto to meta-poky===
* RP to take action on the YP side, possibly not for 2.0 [Done, rename happened]
* formalize lowercase as mandatory requirement for overrides, look for other options in the future [Done]
===Layer Index feature requests discussed with layer index build feedback>>===
* ask for cycles from employers to work on these issues
* make people aware, help with triage, provide resources
===Security===
* need a method for tracking CVs
===Systemd===
complaints: more package config, comments; look at packaging to have
minimal systemd even with options available
* need someone with time available to work on it
* need to get systemd feedback, people using systemd talk to package maintainer
* file systemctl wrapper bug
===Advocacy===
* board to discuss advocacy/community, invite jefro to meetings
Potential OE Day at ELCE next year
* board: do a proper cfp
== Minutes ==
Category:OEDEM
OEDEM 2018

== Location and Time ==
Sunday, 21 October 2018 (before ELCE [October 22-24])
Doors open at: 0830 , Meeting starts at 0900
Expectation is to finish by 1800
Hilton Edinburgh Grosvenor
5-21 Grosvenor Street
EH12 5EF Edinburgh
SAT-NAV: EH12 5EF
5 minute walk to Haymarket Train Station
No onsite car park. Ask Crofton if you need local parking information.
I hope you all like Vertically challenged bread.
Lunch is included.
== Logistics ==
Yes, we know it is Sunday. Best we could do this year.
Attendance is capped at 50. Armin is the bouncer.
== Remote conference link ==
== Planning to Attend ==
# Khem Raj (khem)
# Armpit (Akuster)
# Philip Balister (Crofton)
# Denys Dmytriyenko (denix)
# Marco Cavallini (mckoan)
# Jan Lübbe (shoragan)
# Peter Kjellerstedt (Saur)
# Jeff Osier-Mixon (Jefro)
# Scott Murray (smurray)
# Ruslan Bilovol
# Phil Blundell
# Richard Purdie (RP)
# Richard Leitner
# Jan-Simon Möller (dl9pf)
# Koen Kooi
# Robert Berger (will join in afternoon approx. 14:00?)
# Ulrich Ölmann (OnkelUlla)
# Trevor Woerner (tlwoerner)
# Matt Porter (mdp)
# Nicolas Dechesne (ndec)
# Grygorii Tertychnyi
# Behan Webster (behanw)
# Phil Wise (cajun-rat)
# Martin Hundebøll (hundeboll)
# Tim Orling (moto-timo)
# Bill Mills
# Kate Stewart
# Jeff Morrison
# Alan Wang
# Andrea Galbusera (gizero)
# Ricardo Salveti (rsalveti)
# Christopher Clark (xtopher)
# Rich Persaud
# Michael Halstead (halstead)
# Changhyeok Bae (chbae)
# Kyungjik Min
# Earnest Son
# Mark Hatle (fray)
# Robert Yang
# Bruce Ashfield (zeddii)
# David Reyna
# Alexander Kanavin (kanavin)
# George McCollister (georgem)
# Beth Flanagan (pidge)
# Josef Holzmayr (letothe2nd)
# Stephano Cetola
# Ricardo Ribalda (ribalda)
# Tom King (ka6sox)
# Jon Mason (jonmason)
# Lieu Ta
== Agenda Items ==
=== OE Developers Meeting ===
* Board Member ballot
* OE Infrastructure
* 2.7 Features
* Package Maintainers (reminder)
* Next meeting? Normally in US at ELC in spring. But in 2019 event is in August in San Diego. Skip? Arrange event in Spring? Where? (Maybe at SCaLE?)
* Format of future meetings. We will barely fit in this room, and the size of the group is getting awkward. How do we get people together to communicate, without the situation becoming difficult to handle?
* Tagged releases (Ruslan)
* Automated CVE reporting tools (+ kernel) (Grygorii)
* Long-term OpenEmbedde support (Ruslan, Grygorii)
* Reproducible builds
* 'Patch accepted' notifications to contributors (Ruslan)
=== Meeting minutes for OEDeM ===
https://docs.google.com/document/d/1YDAHjIOXCIgvSZVOKCYLxa8h26dkruX8zspoge7zCpk/edit?usp=sharing
== Minutes ==
SHARED MINUTES AT
ACTIONS identified in meeting:
=== Prior minutes ===
Minutes from Portland, Mar 2018:
https://docs.google.com/document/d/1h_otwcH-6ej4URB5vER-7FpaPthrji3TpJWf5jAKRIk/edit?usp=sharing
Minutes from Prague, Oct 2017:
https://docs.google.com/document/d/1R_pV_PumhZ9a8_aRDTuW7wBjqNwIDuau7FGr6sYYRu0/edit?usp=sharing
Minutes from Portland, Feb 2017:
https://docs.google.com/document/d/1ECCfBwdLUaW3I23RATWCU3kGnSh04Kv0DkH1_KfiLVA/edit?usp=sharing
Category:OEDEM
OEDVM 2022 05

==Location and Time==
Held after the Yocto Project Summit , The OE Developers Meeting is scheduled for Friday, 20 May 2022 between 12:00 and 20:00 UTC. Exact times for each individual topic are found below in the schedule.
The meeting is held on Zoom https://zoom.us/j/99151508871 (Meeting ID: 991 5150 8871). We thank Automotive Grade Linux for providing!
==Format==
As always, we will collect topics on the wiki at
https://wiki.openembedded.org/OEDVM_2022_05.
For the actual developer meeting, there will be pre-assigned timeslots for each topic. The moderator(s) will open with a short introduction/presentation to introduce the topic.
==Topic Ideas==
These are topics that were suggested for previous OE developer meetings and have not been covered yet. They should be seen as starting ideas on things that can be discussed.
Actual schedule
::
Topic 	Moderator(s) 	Time in UTC (Start is 1200 UTC/0800 EDT)	Notes
Introduction 	OE Board 	1200 	
Future of eSDK (inc. bblock/bbunlock commands)	Richard Purdie 	1215 	https://lists.openembedded.org/g/openembedded-architecture/topic/thoughts_on_the_esdk/90990557
Copyright in OE-Core files 	Richard Purdie 	1300 	https://lists.openembedded.org/g/openembedded-architecture/topic/oe_core_copyright_notices/91159593
layer.conf changes 	Richard Purdie 	1330 	
Kernel config RFC 	Trevor Woerner 	1400 	https://docs.google.com/presentation/d/1EC6W_MH6OJ3uMxH2uWA1OWsxYlEVZAoT3z91g6SULqk/edit?usp=sharing
Layer Setup Configuration 	Joshua Watt 	1430 	
Bitbake & OE "Core improvements" 	Joshua Watt 	1500 	
Multiple SBOM formats, both in and out 	Peter Kjellerstedt 	1530 	https://docs.google.com/presentation/d/1f6WvLNrkIVESdI1tSoq99QOTcsAkS08adGnSycWub2w/edit?usp=sharing
Layerindex: quality, tooling, enhancements 	Jan-Simon Möller, Tim Orling	1550 	
Airing of Grievances 	OpenEmbedded Board 	1610 (After all other topics covered) 	
List of grievances
 * How do we increase people working on underlying system?
Unassigned ideas for next time
::
Topic 	Moderator(s) 	Estimate of time	Notes
Data store operation changes 	? 	? 	
Syntax removal 	? 	? 	
Data store internal rewrite 	? 	? 	
f-string in Python code (and more modern python in general)	Ross Burton, Tim Orling	? 	
Merging optional functionality to make it mandatory 	? 	? 	
Dropping core features 	? 	? 	
Security (PSiRT) 	? 	? 	
QA Automation 	? 	? 	
Code submission process 	? 	? 	
Software updates 	Bruce Ashfield 	? 	
AI/ML 	? 	? 	
Here are some new topic ideas:
::
Topic	Moderator(s)	Estimate of time
==Notes==
===Social===
Meet up @ ELC?
==Minutes==
https://docs.google.com/document/d/12rtiKrLgtZl617I5aew0g-N3ZoIyJts3r-FKP2AGRgQ/edit?usp=sharing
OEDVM Nov 2021

==Location and Time==
Held after the Yocto Project Summit , The OE Developers Meeting is scheduled for Friday, 03 December 2021 between 12:00 and 20:00 UTC.
The exact times for each individual topic are found below in the schedule.
We will be using Automotive Grade Linux's Zoom (and many thanks to AGL for this!)
https://zoom.us/j/99151508871
==Format==
As always, we will collect topics on the wiki at
https://www.openembedded.org/OEDVM_Nov_2021.
For the actual developer meeting, there will be pre-assigned timeslots for each topic. The moderator(s) will open with a short introduction/presentation to introduce the topic.
==Topic Ideas==
(In no particular order)
Topic 	Moderator(s) 	Estimate of time
Future direction for SBOM 	Ross Burton, Saul Wold, Joshua Watt	?
Replacing Sato with Phosh 	Joshua Watt, Tim Orling 	?
Future of eSDK 	? 	?
bblock/bbunlock 	? 	?
Binary distributions 	Bruce Ashfield 	?
Modern languages (e.g. go) 	Paul Barker 	?
Inclusive language 	Jon Mason, Tim Orling 	15mins
layer.conf changes 	? 	?
Data store operation changes 	? 	?
Syntax removal 	? 	?
Data store internal rewrite 	? 	?
f-string in Python code (and more modern python in general)	? 	?
Bitbake internal changes 	? 	?
Merging optional functionality to make it mandatory 	? 	?
Dropping core features 	? 	?
Migration to SPDX license 	Ross Burton, Joshua Watt 	?
Security (PSiRT) 	? 	?
Layer setup configuration 	? 	?
Yocto Project compatibility 	ndec 	?
QA Automation 	? 	?
Code submission process 	? 	?
Software updates 	? 	?
AI/ML 	? 	?
Increasing OE membership and voter turnout 	OE Board member 	?
==Minutes==
https://docs.google.com/document/d/1T7pqHvNZuwDGOPXIgRR1_1-ECgDcw0xNin2IgahHpRk/edit#
OEDvM 2022.11

==Location and Time==
Held after the Yocto Project Summit , the OE Developers Meeting is scheduled for Friday, December 2nd 2022 between 12:00 and 20:00 UTC. Exact times for each individual topic are found below in the schedule.
The meeting is held on Zoom https://zoom.us/j/99151508871 (Meeting ID: 991 5150 8871). We thank Automotive Grade Linux for providing!
==Format==
As always, we will collect topics on the wiki at
https://wiki.openembedded.org/OEDVM_2022_11.
For the actual developer meeting, there will be pre-assigned timeslots for each topic. The moderator(s) will open with a short introduction/presentation to introduce the topic.
The meeting notes: https://docs.google.com/document/d/1_kcJJJ_nup9ZfizlBlQF2qUiyrxI_nz3-2V9mn7NwDk/edit?usp=sharing
==Topic Ideas==
From RP's post about bitbake changes for the next release on the architecture list.
https://lists.openembedded.org/g/openembedded-architecture/topic/bitbake_changes_for_the_next/95298341
These are topics that were suggested for previous OE developer meetings and have not been covered yet. They should be seen as starting ideas on things that can be discussed.
Philip Balister will host a discussion of how people use the various layer setup approaches. The goal is list tasks, such as development, testing, production etc and how you interact with the various layer setup solutions. This is not a session to talk about layer setup, the goal here is work out which ones support specific day to day tasks.
Texas Instruments will talk about their experience introducing new users to OpenEmbedded. We are scheduling this for 1400 UTC (0800 CST). Experienced people should take notes, this is a great chance to be reminded your struggles learning how to use OpenEmbedded.
::
Topic 	Moderator(s)	Estimate of time	Notes
Data store operation changes 	? 	? 	
Syntax removal 	? 	? 	
Data store internal rewrite 	? 	? 	
f-string in Python code (and more modern python in general)	? 	? 	
Merging optional functionality to make it mandatory 	Covered 	? 	
Dropping core features 	? 	? 	
Security (PSiRT) 	? 	? 	
QA Automation 	? 	? 	
Code submission process 	? 	? 	
Software updates 	? 	? 	
AI/ML 	? 	? 	
Here are some new topic ideas:
::
Topic 	Moderator(s) 	Estimate of time
OE in-person meet up adjacent to FOSDEM 2023, Brussels	Josef Holzmayr	30 Minutes
? 	? 	?