https://www.openembedded.org/api.php?action=feedcontributions&user=XorA&feedformat=atomOpenembedded.org - User contributions [en]2024-03-28T10:37:08ZUser contributionsMediaWiki 1.29.0https://www.openembedded.org/index.php?title=FOSDEM_2014&diff=6765FOSDEM 20142014-01-24T19:13:42Z<p>XorA: /* General attendance */</p>
<hr />
<div>[[Category:Conferences]]<br />
<br />
= OpenEmbedded booth =<br />
== Manning ==<br />
You are going to FOSDEM 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.<br />
<br />
* Paul Eggleton (Saturday, Sunday)<br />
* Henning Heinold (both days partly)<br />
<br />
== Tasks ==<br />
A bunch of tasks need to be carried out to make our attendance a pleasant experience. Each task needs a volunteer who is willing to help.<br />
<br />
=== Event box ===<br />
<br />
TBA<br />
<br />
=== Device Tags ===<br />
<br />
People standing in front of our booth often want to know what kind of device it is that blinks so funnily. ;) We could make things easier by being able to print small tags providing some information about board manufacturer, CPU, RAM and what its relation to OpenEmbedded is.<br />
<br />
Volunteer: ?<br />
<br />
== Devices ==<br />
<br />
* Paul Eggleton - MinnowBoard, Galileo<br />
<br />
== Flyers and posters ==<br />
You can bring and/or print OpenEmbedded flyers and posters? Add your name and what you'll bring.<br />
<br />
== Power extensions, adapters and other stand material ==<br />
Bringing devices is cool but we need a way to bring power to them too. Additionally people might need power sockets for different systems than the european one. List your name and what stuff you can bring.<br />
* Presentation file for use on the display - Paul<br />
* Machine to connect for displaying the presentation (hopefully with the ability to show off Toaster) - Paul <br />
<br />
= General attendance =<br />
<br />
Attending FOSDEM 2014? Add your name to this page so that other developers can look out for you!<br />
<br />
* Paul Eggleton (bluelightning)<br />
* Philip Balister (Crofton)<br />
* Henning Heinold (woglinde)<br />
* Phil Blundell (pb_)<br />
* Koen Kooi (koen)<br />
* Marcin Juszkiewicz (hrw)<br />
* Jack Mitchell (jackmitchell)<br />
* Graeme Gregory (XorA)<br />
<br />
== Hotels ==<br />
<br />
Although FOSDEM itself takes place at the ULB campus, most folks prefer to stay nearer the city centre.<br />
<br />
The Astrid has traditionally been the default choice for OE developers, though there are many other hotels in the area. If you are staying in a hotel other than the Astrid, feel free to add it to this section for the benefit of others. Recently, most of us stay at the Saint Nicolas due to the free breakfast and wifi.<br />
<br />
Scandic Grand Place.<br />
Rue d'Arenberg 18<br />
Close to beer event (300 m) and Central Station.<br />
Tram to Fosdem around the corner.<br />
Bus to FOSDEM<br />
Train + Bus to FOSDEM<br />
Free WiFi<br />
<br />
Saint Nicolas<br />
Hôtel Saint Nicolas *** <br />
Rue Marché aux Poulets 32 <br />
1000 Bruxelles Tél. +32/2-219.04.40 <br />
Fax +32/2-219.17.21 <br />
http://www.st-nicolas.be<br />
close to beer event, bus to Fosdem few minutes by walk from hotel.<br />
<br />
IBIS Brussels off Grand' Place<br />
Grasmarkt 100<br />
Rue du Marché aux Herbes 100<br />
1000 BRUSSELS</div>XorAhttps://www.openembedded.org/index.php?title=FOSDEM_2013&diff=5517FOSDEM 20132013-01-27T04:24:26Z<p>XorA: /* General attendance */</p>
<hr />
<div>[[Category:Conferences]]<br />
<br />
= OpenEmbedded booth =<br />
== Manning ==<br />
You are going to FOSDEM 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.<br />
<br />
* Paul Eggleton (Saturday, Sunday)<br />
* Philip Balister (Saturday, Sunday)<br />
<br />
== Tasks ==<br />
A bunch of tasks need to be carried out to make our attendance a pleasant experience. Each task needs a volunteer who is willing to help.<br />
<br />
=== Event box ===<br />
<br />
The [[OE event box]] is being graciously brought to the event by Florian.<br />
<br />
Florian would like someone to take this back with them if at all possible. <br />
Volunteer - ?<br />
<br />
=== Device Tags ===<br />
People standing in front of our booth often want to know what kind of device it is that blinks so funnily. ;) We could make things easier by being able to print small tags providing some information about board manufacturer, CPU, RAM and what its relation to OpenEmbedded is.<br />
<br />
Volunteer: ?<br />
<br />
== Devices ==<br />
<br />
* Paul Eggleton - either FRI2 or Intel NUC<br />
<br />
== Flyers and posters ==<br />
You can bring and/or print OpenEmbedded flyers and posters? Add your name and what you'll bring.<br />
* Stickers! - Philip<br />
<br />
== Power extensions, adapters and other stand material ==<br />
Bringing devices is cool but we need a way to bring power to them too. Additionally people might need power sockets for different systems than the european one. List your name and what stuff you can bring.<br />
* Presentation file for use on the display - ?<br />
* Machine to connect for displaying the presentation - Paul<br />
<br />
= General attendance =<br />
<br />
Attending FOSDEM 2013? Add your name to this page so that other developers can look out for you!<br />
<br />
* Paul Eggleton (bluelightning)<br />
* Marcin Juszkiewicz (hrw)<br />
* Philip Balister (Crofton)<br />
* Denis Carikli (GNUtoo)<br />
* Graeme Gregory (XorA)<br />
<br />
== Hotels ==<br />
<br />
Although FOSDEM itself takes place at the ULB campus, most folks prefer to stay nearer the city centre.<br />
<br />
The Astrid has traditionally been the default choice for OE developers, though there are many other hotels in the area. If you are staying in a hotel other than the Astrid, feel free to add it to this section for the benefit of others. Recently, most of us stay at the Saint Nicolas due to the free breakfast and wifi.<br />
<br />
Scandic Grand Place.<br />
Rue d'Arenberg 18<br />
Close to beer event (300 m) and Central Station.<br />
Tram to Fosdem around the corner.<br />
<br />
Saint Nicolas<br />
Hôtel Saint Nicolas *** <br />
Rue Marché aux Poulets 32 <br />
1000 Bruxelles Tél. +32/2-219.04.40 <br />
Fax +32/2-219.17.21 <br />
http://www.st-nicolas.be/contentENG/home.asp<br />
close to beer event, bus to Fosdem few minutes by walk from hotel.<br />
<br />
IBIS Brussels off Grand' Place<br />
Grasmarkt 100<br />
Rue du Marché aux Herbes 100<br />
1000 BRUSSELS</div>XorAhttps://www.openembedded.org/index.php?title=User:XorA&diff=4061User:XorA2011-02-17T08:46:13Z<p>XorA: Created page with 'Is the XorA'</p>
<hr />
<div>Is the XorA</div>XorAhttps://www.openembedded.org/index.php?title=TSCCharter&diff=3981TSCCharter2011-02-10T11:03:33Z<p>XorA: </p>
<hr />
<div>The Technical Steering Council (TSC) is a committee within OpenEmbedded<br />
(OE) appointed by the board with its members voted by election of the eV<br />
members.<br />
<br />
The TSC is ultimately answerable to the members of the OE eV through the<br />
OE board!<br />
<br />
The TSC has 5 positions which will be filled by 5 people elected by the<br />
OE eV members using the eV voting processes.<br />
<br />
The serving term of a TSC member is 1 year, they may be re-elected to<br />
serve more than one term. Each position on the TSC is elected seperately.<br />
<br />
No member is required to serve out his full term, the board would prefer<br />
that if a member of the TSC feels that he is not in a position to best<br />
serve the TSC that he can step down and trigger an election for his<br />
position.<br />
<br />
Decisions by the TSC are made where necessary by majority vote. Once a<br />
decision is made by the technical steering committee, the decision<br />
should be respected as a democratic decision.<br />
<br />
The board will leave the internal running of TSC<br />
meetings/roles/communication/task allocation to the current committee to<br />
decide, but we would wish that the TSCs actions were transparent to the<br />
members.<br />
<br />
The rights and responsibilities of the TSC within the project.<br />
<br />
1) To lead the technical development of OpenEmbedded forward.<br />
2) To generally promote good development practice in OpenEmbedded.<br />
3) To assist the board anticipating future developments in world outside<br />
OpenEmbedded, that could affect the project technically, and bring these<br />
to the members notice.<br />
4) To govern access to all technical aspects of OpenEmbedded, this<br />
includes official git trees, openembedded-devel mailing list, bug<br />
trackers, QA systems, and others as the TSC sees fit.<br />
5) To make decisions in the technical implementation of OpenEmbedded<br />
where the membership is unable to obtain a consensus within itself.<br />
6) To guide the technical aspects of cooporation with outside entities,<br />
whether upstreaming or collaborating.<br />
7) To inform the OpenEmbedded board if there is an area not covered in<br />
the charter the TSC feel should be and the board can make a decision on<br />
updating the charter.</div>XorAhttps://www.openembedded.org/index.php?title=TSCCharter&diff=3979TSCCharter2011-02-10T10:56:55Z<p>XorA: Created page with 'Place Holder'</p>
<hr />
<div>Place Holder</div>XorAhttps://www.openembedded.org/index.php?title=Project_devices&diff=3949Project devices2011-02-05T18:19:32Z<p>XorA: /* 1x CE-RH2 zaurus remote */</p>
<hr />
<div>This site provides a list of devices the OpenEmbedded Projects owns, where they were located, where they will be located, what people intended to do with it.<br />
<br />
The OpenEmbedded Project will lend the devices for a limiting time to people interested and willing to do useful projects with them. The guidelines still need to be set up as it is a matter of trust.<br />
<!--break--><br />
= Sharp Zaurus devices =<br />
<br />
== 3x Sharp SL-6000L (tosa) ==<br />
<br />
First device was won at [http://tuxmobil.org/linux_award.html TuxMobil GNU/Linux Award 2005] which was kindly sponsored by [http://xtops.de Xtops.DE].<br />
* '''2005.09.13''' Holger Hans Peter Freyther (zecke) picked it up. His interest is in assisting Dirk Opfer to finish the SL-6000er Linux port. The initial plan is to keep the device for three month and pass it on. He is willing to pass the device on earlier if others are interested to work on it.<br />
* '''2006.01.10''' device was sent to Liam Girdwood (lrg) to work on drivers for Touchscreen and audio. His plan is to keep the device for a few weeks until the touch and audio are working well.<br />
* '''2006.07.14''' device was given to Mike Arthur (mikearthur) by Liam Girdwood (lrg) to work on drivers for touchscreen and battery.<br />
* '''2006.09.27''' device returned by Mike Arthur to Liam Girdwood (lrg) and Graeme Gregory (XorA)<br />
* '''2009.03.25''' Graeme 'XorA' Gregory working on Ångström improvements.<br />
* '''2010'06'01''' Transferred to Jay7<br />
<br />
Second was donated by anonymous donor.<br />
* '''2006.06.08''' Aman Gupta (TheMasterMind1) got it.<br />
* '''2006.06.27''' Marcin Juszkiewicz (Hrw) got it - machine will be used to resolve current OpenZaurus problems and testing 2.6 kernel.<br />
* '''2008.06.14''' Samuel Ortiz (from OpenedHand, now Intel) got it to test MFD support for Tosa. We discussed that when he will end testing this device will go to Dmitry Baryshkov (current Tosa maintainer in 2.6 kernel).<br />
<br />
Third was donated by Matthew Melendy<br />
* '''2009.03.25''' Mark 'broonie' Brown working on ASoC improvements<br />
<br />
== 1x Sharp SL-C750 (shepherd) ==<br />
This device was won at [http://tuxmobil.org/linux_award.html TuxMobil GNU/Linux Award 2005] which was kindly sponsored by [http://xtops.de Xtops.DE] .<br />
* '''2005.09.10''' Christian Fertig (_FuF_) picked it up. His interest is in improving multimedia packages for Opie and GPE but also videolan etc.<br />
* '''2006.05.01''' Mickeyl got it back. Plan is to hand it over to Zecke at OEDEM in October.<br />
* '''2006.10.06''' Holger Freyther (zecke) received it<br />
<br />
== 2x Sharp SL-5600 (poodle) ==<br />
<br />
First device was donated by anonymous donor.<br />
* '''2006.06.08''' Aman Gupta (TheMasterMind1) got it.<br />
* '''2006.06.27''' Marcin Juszkiewicz (Hrw) got it - machine will move to Mickeyl soon.<br />
* '''2006.10.07''' Micheal Lauer (Mickeyl) got it<br />
<br />
Second was donated by Daniel Stutzbach.<br />
* '''2006.09.11''' Graeme Gregory (XorA) now has it for audio work.<br />
* '''2009.03.25''' Was transferred to Henry von Tresckow(hvontes) via Crofton last year<br />
<br />
== 1x Sharp SL-C1000 (akita) ==<br />
<br />
Gaining dust in Lukas' drawer. If anybody likes it for OE needs contact him at lukas <at> htc-linux.org<br />
<br />
== 1x Sharp SL-C3000 (spitz) ==<br />
This device was sponsored by SIEMENS R&D.<br />
<br />
* '''2005''' Mickeyl got it to improve OpenZaurus experience on Zaurus models w/ HD.<br />
* '''2006''' Marcin Juszkiewicz will get it at OEDEM in October.<br />
* '''2006.10.07''' Marcin Juszkiewicz (Hrw) got it<br />
* '''2007.02.25''' Rolf 'Laibsch' Leggewie got it on FOSDEM. He works on Japanese support.<br />
<br />
== 1x Sharp SL-5500 (collie) ==<br />
Donated by Matthew Melendy<br />
<br />
* '''2009.03.25''' Graeme 'XorA' Gregory is holding it currently.<br />
* '''2010'06'01''' Transferred to Jay7<br />
<br />
= 1x USB-VGA adaptor =<br />
This device will be used for presentations on OE powered devices. It requires a usb 2.0 host controller, so it won't work with the ratoc CFU1U card.<br />
<br />
* '''2006.11.03''' Koen got it to do some initial testing<br />
<br />
Lukas: I would love to test this device with htcleo machine which has usb 2.0 host. Is it still in OE possession ?<br />
<br />
= 1x Greenphone =<br />
This devices was given us by Knut Irvin (Qt Community Manager). It will be used as a reference platform for hopefully future work on Qtopia Integration<br />
<br />
* '''2007.02.24''' Holger Freyther got it at FOSDEM<br />
<br />
= 1x Various hardware =<br />
Given by an unknown person, 1xOrinoco wifi card, 1x4gb flashcard, 1x Canon flash card , 2x usb cable.<br />
<br />
* '''2007.02.26''' Gerwin van der Kruis got it at FOSDEM<br />
<br />
Donated by Matthew Melendy Socket WiFi CF, Socket Bluetooth CF, Pretec GPS CF and various cables/adapters, SL-6000 sled<br />
<br />
* '''2009.03.25''' Graeme 'XorA' Gregory received at FOSDEM and currently holding<br />
* '''2010'06'01''' Transferred to Jay7<br />
<br />
Donated by Marcin Juszkiewicz 'hrw' D-Link Wifi, Unbranded libertas wifi<br />
<br />
* '''2009.03.25''' Graeme 'XorA' Gregory received and FOSDEM and currently holding<br />
* '''2010'06'01''' Transferred to Jay7<br />
<br />
= 1x Unknown Mini-itx epia box =<br />
Given by an unknown company, got it by mail.<br />
<br />
* '''2007.02.26''' Gerwin van der Kruis got it at home<br />
<br />
= 1x CE-RH2 zaurus remote =<br />
Lost who it was given by.<br />
<br />
* Currently in posession of Richard Purdie<br />
<br />
<br />
[[Category:Dev]]</div>XorAhttps://www.openembedded.org/index.php?title=Fosdem_2011&diff=3934Fosdem 20112011-01-31T16:36:13Z<p>XorA: /* General attendance */</p>
<hr />
<div>= OpenEmbedded booth =<br />
== Manning ==<br />
You are going to FOSDEM 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.<br />
<br />
* Robert Schuster (Saturday)<br />
* Ulf Samuelsson (Saturday and Sunday occasionally)<br />
* Philip Balister (As needed)<br />
<br />
== Devices ==<br />
Add your name and what devices you'll bring for the stand.<br />
<br />
Ulf Samuelsson - AT91SAM9M10EKES booting Openembedded/Android from SD-Card<br />
(No flash on board enabled)<br />
<br />
Robert Schuster - Pandaboard - Hopefully booting Angstrom with some desktop and Java foo. Try to get hold of a small TFT display<br />
<br />
== Flyers and posters ==<br />
You can bring and/or print OpenEmbedded flyers and posters? Add your name and what you'll bring.<br />
<br />
== Power extensions, adapters and other stand material ==<br />
Bringing devices is cool but we need a way to bring power to them too. Additionally people might need power sockets for different systems than the european one. List your name<br />
and what stuff you can bring.<br />
<br />
* Robert Schuster:<br />
**3-socket power extension (EU)<br />
**tape<br />
<br />
= General attendance =<br />
<br />
Attending FOSDEM 2011? Add your name to this page so that other developers can look out for you!<br />
<br />
* Esben Haabendal<br />
* Frans Meulenbroeks (eFfeM)<br />
* Philip Balister (Crofton)<br />
* Robert Schuster (rschus/thebohemian)<br />
* Ulf Samuelsson<br />
* Graeme Gregory (XorA)<br />
<br />
== Hotels ==<br />
<br />
Although FOSDEM itself takes place at the ULB campus, most folks prefer to stay nearer the city centre.<br />
<br />
The Astrid has traditionally been the default choice for OE developers, though there are many other hotels in the area. If you are staying in a hotel other than the Astrid, feel free to add it to this section for the benefit of others.<br />
<br />
Scandic Grand Place.<br />
Rue d'Arenberg 18<br />
Close to beer event (300 m) and Central Station.<br />
Tram to Fosdem around the corner.</div>XorAhttps://www.openembedded.org/index.php?title=GA2010&diff=2861GA20102010-10-13T07:36:57Z<p>XorA: /* Agenda */</p>
<hr />
<div>=General Assembly 2010 Agenda=<br />
<br />
Currently this is in draft state, the order and exact agenda is not finalised yet!<br />
<br />
==Agenda==<br />
<br />
* Open of GA by Chairperson<br />
* Apologies<br />
* Review of last GA Minutes<br />
* Vote for new members<br />
* Online Voting System discussion/redraft/vote.<br />
* Report from TSC<br />
* Report from Treasurer<br />
* Any Other Business<br />
* Close by Chairperson</div>XorAhttps://www.openembedded.org/index.php?title=Getting_started_with_OE-Classic&diff=1957Getting started with OE-Classic2009-12-10T22:24:34Z<p>XorA: /* Obtaining BitBake */</p>
<hr />
<div>= Setting up the toolchain and doing a build =<br />
<br />
== Directory Structure ==<br />
The base directory of your Openembedded environment (<nowiki>/stuff/</nowiki>) is the location where sources will be checked out (or unpacked).<br />
<br />
* You must choose a location with '''no symlinks above it'''<br />
<br />
* If you work in a chrooted environment and have ccache installed it is highly recommended to 'su - <username>' after you have chrooted. Compilation may fail because ccache needs a valid <nowiki>$HOME</nowiki>, which is usually set when using a user account. It is recommended that ccache is not installed on systems used to build OpenEmbedded as it has been known to introduce other subtle build failures.<br />
<br />
To create the directory structure:<br />
<br />
<pre><nowiki><br />
$ mkdir -p /stuff/build/conf<br />
$ cd /stuff/<br />
</nowiki></pre><br />
<br />
== Obtaining BitBake ==<br />
To start using OE, you must first obtain the build tool it needs: <nowiki>bitbake</nowiki><br />
<br />
It is recommended to run bitbake without installing it, as a sibling directory of <nowiki>openembedded/</nowiki> and <nowiki>build/</nowiki> directories. Indeed, as bitbake is written in python it does not need to be compiled. You'll just have to set the PATH variable so that the [[BitBake]] tools are accessible (see [[#Setup the environment|Setup the environment]] section).<br />
<br />
===Getting a working bitbake===<br />
<br />
Bitbake switched from a svn repository to a git one, and the former is stuck at version 1.8.13, so when you try to build you may face to an error: "Bitbake version 1.8.16 is required and version 1.8.13 was found". In that case please fetch released version or use git repository.<br />
<br />
Which version is safe to use? Last release one is always working. When OE changes require newer version of BitBake metadata is changed and you will get message like above.<br />
<br />
One note for those who wants to play with development versions of BitBake - Python 2.6 may be required by newer versions. This can be a problem for some Linux distributions.<br />
<br />
Basically the easier and faster solution (at the moment I'm writing) is to get release one.<br />
<br />
wget http://download.berlios.de/bitbake/bitbake-1.8.18.tar.gz<br />
<br />
===Using releases===<br />
<br />
Visit [http://developer.berlios.de/projects/bitbake/ BitBake homepage] and download tarball with latest release. For normal usage we suggest using 1.8.x (stable branch) versions. Unpack it to '''/stuff/bitbake/'''.<br />
<br />
== Obtaining OpenEmbedded using GIT ==<br />
<br />
''Note: ''Once upon a time OpenEmbedded was using Monotone for version control. If you have an OE Monotone repository on your computer, you should replace it with the Git repository.<br />
<br />
''Note: ''These are only brief instructions. For a longer description about using Git with OpenEmbedded refer to [[Git]] and [[GitPhraseBook]].<br />
<br />
The OpenEmbedded project resides in a Git repository. You can find it at ''git://git.openembedded.org/openembedded''. <br />
<br />
Web interface is: http://cgit.openembedded.org/<br />
<br />
To obtain Openembedded:<br />
# Install git<br />
# Go to the base directory of your OpenEmbedded environment<br />
$ cd /stuff/<br />
# Checkout the repository<br />
$ git clone git://git.openembedded.org/openembedded<br />
<br />
or for the firewall challenged try<br />
$ git clone http://repo.or.cz/r/openembedded.git<br />
<br />
This is the data you'll be using for all the work.<br />
<br />
=== Updating OpenEmbedded ===<br />
The .dev branch of OE is updated very frequently (as much as several times an hour). The distro branches are not updated as much but still fairly often. It seems good practice to update your OE tree at least daily. To do this, run<br />
$ git pull<br />
(note: this must be done in the directory created by the checkout of openembedded. On this page, this directory is <tt>/stuff/openembedded</tt>, but my checkout generated a directory <tt>/stuff/openembedded</tt>. Check the name of your subdir, and use the name on your machine in the following examples)<br />
<br />
== Create local configuration ==<br />
It's now time to create your local configuration.<br />
While you could copy the default local.conf.sample like that:<br />
<br />
<pre><nowiki><br />
$ cd /stuff/<br />
$ cp openembedded/conf/local.conf.sample build/conf/local.conf<br />
$ vi build/conf/local.conf<br />
</nowiki></pre><br />
<br />
It is actually recommended to start smaller and keep local.conf.sample in the background and add entries from there step-by-step as you understand and need them. Please, do not just edit build/conf/local.conf.sample but actually READ it (read it and then edit).<br />
<br />
For building a .dev branch, in your <nowiki>local.conf</nowiki> file, you should have at least the following three entries. Example for the Angstrom distribution and the Openmoko gta01 machine:<br />
<pre><nowiki><br />
BBFILES = "/stuff/openembedded/recipes/*/*.bb"<br />
DISTRO = "angstrom-2008.1"<br />
MACHINE = "om-gta01"<br />
</nowiki></pre><br />
<br />
If you choose to install OE in your home directory, modify local.conf to refer to the OE paths as /home/<username>/ rather than ~/. It does not find the *.bb packages otherwise.<br />
<br />
== Setup the environment ==<br />
One of the four command sets below will need to be run every time you open a terminal for development. (You can automate this in ~/.profile, /etc/profile, or perhaps use a script to set the necessary variables for using [[BitBake]].)<br />
<br />
If you followed the recommendation above to use [[BitBake]] from svn:<br />
<pre><nowiki><br />
$ export BBPATH=/stuff/build:/stuff/openembedded<br />
$ export PATH=/stuff/bitbake/bin:$PATH<br />
</nowiki></pre><br />
<br />
If you installed [[BitBake]]:<br />
<pre><nowiki><br />
$ export BBPATH=/stuff/build:/stuff/openembedded<br />
</nowiki></pre><br />
<br />
Alternative syntax for those using the tcsh shell (e.g FreeBSD):<br />
<pre><nowiki><br />
$ setenv PATH "/stuff/bitbake/bin:"$PATH<br />
$ setenv BBPATH "/stuff/build:/stuff/openembedded:"$BBPATH<br />
</nowiki></pre><br />
<br />
== Start building ==<br />
The primary interface to the build system is the <nowiki>bitbake</nowiki> command (see the bitbake users manual). <nowiki>bitbake</nowiki> will download and patch stuff from the network, so it helps if you are on a well connected machine.<br />
<br />
Note that you should issue all bitbake commands from inside of the <nowiki>build/</nowiki> directory, or you should override TMPDIR to point elsewhere (by default it goes to <nowiki>tmp/</nowiki> relative to the directory you run the tools in).<br />
<br />
Here are some example invocations:<br />
<br />
Building a single package (e.g. nano):<br />
<br />
<pre><nowiki><br />
$ bitbake nano<br />
</nowiki></pre><br />
<br />
Building package sets (e.g. task-base):<br />
<br />
<pre><nowiki><br />
$ bitbake task-base<br />
</nowiki></pre><br />
<br />
''Special note for'' <nowiki>task-base</nowiki>: you may need additional setup for building this very one task. More details in [[ZaurusKernels]]<br />
<br />
Building a group of packages and deploying them into a rootfs image:<br />
<br />
GPE:<br />
<br />
<pre><nowiki><br />
$ bitbake x11-gpe-image<br />
</nowiki></pre><br />
<br />
X11:<br />
<br />
<pre><nowiki><br />
$ bitbake x11-image<br />
</nowiki></pre><br />
<br />
OPIE:<br />
<br />
<pre><nowiki><br />
$ bitbake opie-image<br />
</nowiki></pre><br />
<br />
('''NOTE:''' kergoth says it will take around 10GB of disk space to build an opie or gpe image for one architecture.<br><br />
sledge says: You can reduce it to ~4GB by [[Advanced_configuration|INHERIT += "rm_work"]])<br />
<br />
('''NOTE:''' if you are using your custom kernel - set "Use the ARM EABI to compile the kernel (AEABI)" option in "Kernel Features")<br />
<br />
See the /stuff/openembedded/recipes/meta/ directory if you're curious about what meta/task and image targets exist.<br />
<br />
Building a single package, bypassing the long parse step (and therefore its dependencies--use with care):<br />
<br />
<pre><nowiki><br />
$ bitbake -b /stuff/openembedded/recipes/blah/blah.bb<br />
</nowiki></pre><br />
<br />
See [[Useful targets]] for a description of some of the more useful meta-packages. You will typically need at least one of the base images (<nowiki>bootstrap-image</nowiki>, <nowiki>opie-image</nowiki> or <nowiki>gpe-image</nowiki>), and if and only if you're building for an [http://wiki.openzaurus.org/Main_Page OpenZaurus] target requiring an installer image (such as C3000), an additional <nowiki>pivotboot-image</nowiki>.<br />
<br />
Output of the build process (temporary files, log files and the binaries) all ends up in the <nowiki>tmp</nowiki> directory. Most interesting is probably the <nowiki>tmp/work/</nowiki> directory. Just have a look around the [[DirectoryStructure]]. <br />
<br />
Images generated by building package groups like <nowiki>opie-image</nowiki> or <nowiki>pivotboot-image</nowiki> are placed in the <nowiki>tmp/deploy/images/</nowiki> directory. Individual ipkg packages are put in <nowiki>tmp/deploy/ipk</nowiki>.<br />
<br />
== Adding Packages ==<br />
# Create [[bbfile]].<br />
# Try building it locally.<br />
# Fix eventual problems.<br />
# Send .[[bbfile]] or an [[OePatch]] to the [http://wiki.openembedded.net/index.php/Mailing_Lists openembedded-devel mailing list]. Please note that changes should comply with the [[Commit_Policy | commit policy]].<br />
<br />
= Problems =<br />
Try to solve problems first by checking that you have done everything right, that nothing has changed from this description and that you have the latest code (see [[GitPhraseBook]]). Look also in the log file (referenced in any error message you will receive). If you still have problems, try checking [[PossibleFailures]] and [http://www.openembedded.org/wiki/OeFaq#builderrors common build errors]. <br />
Above links are dead, you can try the [[:Category:FAQ]]. If problems persist, ask on [[IRC]] or in the [[Mailing lists|openembedded mailing list]].<br />
<br />
The Openembedded metadata is changing constantly. This implies several things:<br />
<br />
# Once you have a "known good" version that works well on your system, keep it! To update, clone a new copy; don't overwrite that working version until it's known to be safe.<br />
# To resolve build problems, "git pull" is your good friend. Many times, the issues will already be fixed in the current tree.<br />
# Not all metadata updates cause the local caches to update correctly. Sometimes you'll need to remove the ".../tmp" work directory and rebuild from scratch.<br />
# Similar issues apply to the package sources you download.<br />
<br />
= Portability issues =<br />
Make sure to set <nowiki>TARGET_OS</nowiki> to something other than linux in local.conf if your host isn't linux.<br />
<br />
GNU extensions to tools are often required. Symlink GNU patch, make, and cp (from fileutils), chmod, sed, find, tar, awk into your OE development path.<br />
<br />
FreeBSD 4 users: Perl 5.0 is too old. A more recent perl must be available as <nowiki>/usr/bin/perl</nowiki>. Unfortunately just having more recent perl in the path isn't good enough. Some scripts are hard-coded for <nowiki>/usr/bin/perl</nowiki>. You can test for which perl you're using by typing perl -v. see /usr/ports/UPDATING for instructions on updating perl. Don't forget to do a use.perl port as instructed in /usr/ports/UPDATING<br />
<br />
FreeBSD users: Set <nowiki>BUILD_OS</nowiki> in local.conf to freebsdN where N is your major version number. At least the cross gcc wants this.<br />
<br />
FreeBSD users: The build process of glibc uses a very long command line at some places. Increase ARG_MAX to at least 131072, by editing /usr/sys/sys/syslimits.h and recompile your kernel (and reboot).<br />
<br />
= Productivity notes =<br />
Use the interactive bitbake mode ("bitbake -i") to speed up work when debugging or developing .bb files. Remember to run "parse" at the prompt first. Go!<br />
<br />
If you want to save some compile time or are interested in additional tweaks to local.conf take a look at the [[Advanced configuration]] page.<br />
<br />
[[Category:User]]</div>XorAhttps://www.openembedded.org/index.php?title=Online_Voting_Policy&diff=1936Online Voting Policy2009-11-30T10:01:49Z<p>XorA: New page: Rules of Procedures for Online Voting The articles of association of the OpenEmbedded e.V. provide that certain decisions can be taken by online voting. This includes voting about new mem...</p>
<hr />
<div>Rules of Procedures for Online Voting<br />
<br />
The articles of association of the OpenEmbedded e.V. provide that certain decisions can be taken by online voting. This includes voting about new members and deciding about certain rules of procedures. In addition the OpenEmbedded e.V. allows to use online voting for decisions which aren't covered in the articles of association. There are several different types of votes which slightly differ in procedure and method to calculate results. These rules regulate the procedure of online votes and how results are calculated. The intention of these rules is to provide a fair and pragmatic way to let the OpenEmbedded e.V. take decisions by online voting.<br />
<br />
=Voting Administrators=<br />
<br />
The board of the OpenEmbedded e.V. assigns one or more voting administrators which are responsible for technically performing the voting. This includes sending out the ballots, receiving the votes, calculating and publishing the results.<br />
<br />
The voting administrators must not disclose any information about the identity of the voters or any other information which isn't contained in the published voting results.<br />
<br />
=General procedure for online voting=<br />
<br />
An online voting is initiated by a voting proposal followed by a discussion period. After the discussion period the voting period is started. The voting is finished by calculating and publishing the voting results.<br />
<br />
Results of online votes are effective immediately following publication of the results unless otherwise stated in the voting proposal.<br />
<br />
==Voting Proposal==<br />
<br />
An online voting is initiated by a proposal for voting which states the subject of the voting. The proposal is sent by email to the membership mailing list and has to include exact and complete information what is voted upon. Only the information which is directly included in the mail sent as voting proposal is subject of the voting.<br />
<br />
The voting proposal email has to explicitly be marked as voting proposal by starting the email subject line with the string "Voting Proposal:".<br />
<br />
Any active member can initiate a voting by sending a voting proposal.<br />
<br />
The member who has initiated a vote can retract the voting proposal by sending an email to the membership list stating the intention to retract the proposal.<br />
<br />
A proposal can only be retracted within the discussion period.<br />
<br />
==Discussion Period==<br />
<br />
The discussion period begins on the date the membership mailing list receives the voting proposal. Unless specified otherwise in the procedures for the specific type of vote (see: Types of Votes), the discussion period lasts for two weeks. The discussion period should be used to discuss the voting and form opinions about the options which are available for voting.<br />
<br />
==Start of Voting==<br />
<br />
When the discussion period has finished the voting is started by sending ballots to all active members. The ballots should include the text of the proposal which is voted about.<br />
<br />
==Voting Period==<br />
<br />
The voting period is started by sending out the ballots. Unless specified otherwise in the procedures for the specific type of vote (see: Types of Votes), the voting period lasts for two weeks. During the voting period the active members cast their votes. Only votes cast within the voting period are considered for the results of the voting.<br />
<br />
==End of Voting==<br />
<br />
After the voting period all cast votes are counted and the results of the voting are published.<br />
<br />
The results of a vote are published to the OpenEmbedded e.V. membership by sending them to the membership mailing list. They have to include the number of persons permitted to vote, the total number of votes, and the number of votes for each available voting option. The results should also include a statement, if the voting was valid according to section 5.<br />
<br />
=Types of Votes=<br />
<br />
There are three types of votes: Votes about new members (3.1), elections of groups of people (3.2), votes for decision (3.3).<br />
<br />
==Voting about new members==<br />
<br />
The discussion period is started by sending a new member proposal to the membership mailing list. Within the discussion period at least two other members have to declare their support for the vote, otherwise the proposal is considered to be rejected. If two members declare their support the voting is started after the discussion period.<br />
<br />
The discussion period has a duration of one week and is extended to two weeks, if requested by a member.<br />
<br />
The voting period has a duration of one week.<br />
<br />
For new member votes there are three options: "Yes", "No", "Abstention". The new member is accepted, if there are more "Yes" than "No" votes and the vote isn't invalid according to section 5.<br />
<br />
==Electing groups of persons==<br />
<br />
For elections of groups of people there is an additional candidacy period before the voting proposal is sent. The person responsible for the execution of the voting sends a call for candidates to the membership mailing list which starts the candidacy period. If there is no explicit rule about who is responsible for execution of the voting, the board of the e.V. is responsible.<br />
<br />
The candidacy period lasts two weeks. All members who declare their candidacy in a statement sent to the membership list become candidates for the election.<br />
<br />
After the candidacy period the list of candidates is sent as voting proposal. This starts the two-weeks discussion period.<br />
<br />
The candidates are voted on as options according to section 3.4.<br />
<br />
==Voting about decisions==<br />
<br />
The OpenEmbedded e.V. can officially take decisions or decide about official statements on request of at least three active member. One member has to send the voting proposal to the membership mailing list. This starts the discussion period. Within the discussion period at least two other members have to declare their support for the vote, otherwise the proposal is considered to be rejected. If two members declare their support the voting is started after the discussion period.<br />
<br />
The responsible party for execution of the voting sends the voting proposal which includes all options. This starts the discussion period.<br />
<br />
After the discussion period the voting is started. The options are voted on according to section 3.4.<br />
<br />
==Voting System==<br />
===Multiple options===<br />
<br />
If there are more than two options (excluding abstention), the following voting system shall be used:<br />
<br />
The members are asked to rank the options in terms of their preference into a ballot. A ballot may contain two options of the same rank. All options must be ranked. Each member may make up to one ballot.<br />
<br />
The winners are found by:<br />
<br />
1. Given two options A and B, V(A,B) is the number of voters who prefer option A over option B.<br />
2. From the list of options, we generate a list of pairwise defeats.<br />
* An option A defeats an option B, if V(A,B) is strictly greater than V(B,A).<br />
3. From the list of pairwise defeats, we generate a set of transitive defeats.<br />
* An option A transitively defeats an option C if A defeats C or if there is some other option B where A defeats B AND B transitively defeats C.<br />
4. We construct the Schwartz set from the set of transitive defeats.<br />
* An option A is in the Schwartz set if for all options B, either A transitively defeats B, or B does not transitively defeat A.<br />
5. If there are defeats between options in the Schwartz set, we drop the weakest such defeats from the list of pairwise defeats, and return to step (iii).<br />
* A defeat (A,X) is weaker than a defeat (B,Y) if V(A,X) is less than V(B,Y). Also, (A,X) is weaker than (B,Y) if V(A,X) is equal to V(B,Y) and V(X,A) is greater than V(Y,B).<br />
* A weakest defeat is a defeat that has no other defeat weaker than it. There may be more than one such defeat.<br />
6. If the number of options in the Schwartz set does not exceed the number of required winners, then the winners are the Schwartz set. If the number of members of the Schwartz set exceeds the number of required winners, the board chooses which of the members of the Schwartz set wins.<br />
7. If this results in an insufficient number of winners, then the candidates which have already won according to step (vi) should be removed from the list of options, and then this procedure is repeated from step (i).<br />
<br />
Parts of this section are copied from the Constitution for the Debian Project (v1.4), http://www.debian.org/devel/constitution<br />
<br />
===Two options===<br />
<br />
If the number of options is exactly two (excluding abstension), then:<br />
<br />
* Each active member can vote with "Yes", "No" or "Abstain".<br />
* If there are more "Yes" than "No" votes and the vote isn't invalid according to section 5, the decision is accepted.<br />
<br />
=Right to vote=<br />
<br />
All members of the OpenEmbedded e.V. which are active members at the time the voting period is started have the right to cast a vote. The prerequisite for taking part in online votes is a valid email address in the member database. The member is solely responsible for initially setting and updating his email address in the member database.<br />
<br />
=Quorum=<br />
<br />
The result of a voting only becomes effective when the number of votes which have chosen an option different from "Abstention" is greater than 20 percent of the number of active members. If this quorum isn't reached the voting is considered invalid. An invalid voting can be repeated, but not before a period of four weeks has passed between publishing the results of the invalid vote and the proposal for the repeated voting.<br />
<br />
=Anonymity=<br />
<br />
Online votes are anonymous. The information which members participated in the vote and for which option they voted aren't disclosed. The voting administrators are allowed to track this information for technically executing the vote. The information mustn't be used for other purposes and mustn't be made available to any other people.<br />
<br />
=Publication of voting results=<br />
<br />
All voting results except for rejected votes about new members are published on the OpenEmbedded e.V. web site, excluding the exact numbers of votes.<br />
<br />
=Modification of voting procedure=<br />
<br />
The board may modify the voting procedures for individual votes upon request of the e.V. membership if good reason for the change, as determined by the good judgment of the board, is provided.</div>XorAhttps://www.openembedded.org/index.php?title=Organization&diff=1935Organization2009-11-30T09:49:31Z<p>XorA: </p>
<hr />
<div>The current organization for OE is a German eV legal entity (similar to KDE: http://ev.kde.org/) and is for the purpose of managing finances, voting, and membership.<br />
<br />
An 'eV' for 'eingetragener Verein', in the German law, translates to a voluntary organization; a group of individuals who voluntarily enter into an agreement to form a body (or organization) to accomplish a purpose. The organization has members.<br />
<br />
The OpenEmbedded eV statues are located here: http://docs.openembedded.org/organization/2008-11-22_statutes-de.pdf<br />
<br />
A bablefish translation is here -- could German speaking folks please clean this up: [[OpenEmbedded eV Statutes]]<br />
<br />
During FOSDEM 2008 in Brussels, Belgium, a group of founding members physically gathered to get the paperwork going.<br />
<br />
= The current board of directors =<br />
<br />
* President ''Dr. Michael Lauer''<br />
* Vice President ''Philip Balister''<br />
* Vice President and Treasurer ''Florian Boor''<br />
* Board Member ''Graeme Gregory''<br />
<br />
= Current Members =<br />
(please keep in alphabetical order)<br />
# Alessandro Gardich<br />
# Chris Larson<br />
# Cliff Brake<br />
# Daniel Willmann<br />
# Denys Dmytriyenko<br />
# Dirk Opfer<br />
# Dmitry EreminSolenikov<br />
# Florian Boor<br />
# Graeme Gregory<br />
# Henning Heinold<br />
# Holger Freyther<br />
# Jan Lübbe<br />
# Ken Gilmer<br />
# Khem Raj<br />
# Koen Kooi<br />
# Leon Woestenberg<br />
# Liam Girdwood<br />
# Marcin Juszkiewicz<br />
# Marco Cavallini<br />
# Mark Brown<br />
# Michael Lauer<br />
# Philip Balister<br />
# Philip Blundell<br />
# Phillip Zabel<br />
# Richard Purdie<br />
# Robert Schuster<br />
# Stefan Schmidt<br />
<br />
= OE Developers =<br />
Openembedded Developers are people who have write access to the git repository. Due to the nature of OE, there are many developers, and each one tends to maintain a section of OE. A list of maintainers can be found [http://cgit.openembedded.net/cgit.cgi?url=openembedded/tree/MAINTAINERS here]. See [[OpenEmbedded Developers]] for a list of current developers.<br />
<br />
= Todo =<br />
* process for adding new members<br />
* process for voting<br />
* responsibility of the board<br />
* conflict resolution<br />
<br />
= Pointers for Board Members =<br />
* [[Checklist for the General Assembly]]<br />
<br />
= Online Voting Policy =<br />
* [[Online Voting Policy]]<br />
<br />
= Faq =<br />
; Are contributions tax deductible?<br /><br />
: Yes they are. <br />
; Should I become member of the OE e.V.?<br />
: If you are contributing to OE frequently and/or you are interested in getting involved in administrative or organisational tasks it might be a good idea to join OE e.V.<br />
; How do I become member of the OE e.V.?<br />
: Let an existing member introduce you by sending a short introduction to the 'ev' [http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-members mailinglist]. If you don't know one get in touch with us on the development mailinglist or IRC first. The e.V. is open for anyone to join and its not meant to be an exclusive club of a few developers. <br />
; Is there a membership fee?<br />
: Yes, and no, since you are allowed to defined the amount on your own.<br />
<br />
[[Category:Dev]]</div>XorA