http://www.openembedded.org/api.php?action=feedcontributions&user=MarcinHrwJuszkiewicz&feedformat=atomOpenembedded.org - User contributions [en]2024-03-19T03:19:59ZUser contributionsMediaWiki 1.29.0http://www.openembedded.org/index.php?title=User:MarcinHrwJuszkiewicz&diff=10841User:MarcinHrwJuszkiewicz2021-05-20T09:12:51Z<p>MarcinHrwJuszkiewicz: </p>
<hr />
<div>* OpenEmbedded developer 2004-2010, 2012-2013<br />
* Poky developer 2007-2009<br />
* OpenZaurus maintainer from 2005 to the end (2007)<br />
* BUG Labs developer 2008-2010<br />
* Linaro developer 2010-2013, 2016-present (2021)<br />
* Fedora developer 2013-2016<br />
* RHEL developer 2013-2016<br />
<br />
= Contact =<br />
<br />
E-mail: hrw@openembedded.org<br />
<br />
Website: http://marcin.juszkiewicz.com.pl/</div>MarcinHrwJuszkiewiczhttp://www.openembedded.org/index.php?title=OE-Core_Standalone_Setup&diff=10702OE-Core Standalone Setup2020-04-14T15:55:08Z<p>MarcinHrwJuszkiewicz: updated to newest versions</p>
<hr />
<div>[[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.<br />
<br />
== Getting started ==<br />
<br />
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:<br />
<pre><br />
git clone git://git.openembedded.org/openembedded-core oe-core<br />
cd oe-core<br />
git clone git://git.openembedded.org/bitbake bitbake<br />
</pre><br />
<br />
2) Check out the latest stable branches of both OE-Core and BitBake:<br />
<pre><br />
git checkout zeus<br />
cd bitbake<br />
git checkout 1.46<br />
cd ..<br />
</pre><br />
<br />
3) Set up the environment and build directory:<br />
<pre><br />
source ./oe-init-build-env [<build directory>]<br />
</pre><br />
<br />
The optional build directory may be specified, otherwise it is assumed you want to use the directory named "build".<br />
<br />
4) First time configuration<br />
<br />
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.<br />
<br />
5) Build something:<br />
<pre><br />
bitbake <target><br />
</pre><br />
<br />
A good simple place to start is <tt>bitbake core-image-minimal</tt>. 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.</div>MarcinHrwJuszkiewiczhttp://www.openembedded.org/index.php?title=FOSDEM_2019&diff=10484FOSDEM 20192019-01-29T16:35:09Z<p>MarcinHrwJuszkiewicz: /* Attendance */</p>
<hr />
<div>[[Category:Conferences]]<br />
<br />
= OpenEmbedded 2019 booth =<br />
<br />
== Volunteers ==<br />
<br />
Are you 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 />
* Scott Murray - should be available for a big chunk of both Saturday and Sunday<br />
* Chris Simmonds - would be happy to take a slot of booth duty either Saturday or Sunday<br />
* Philip Balister - I'll stop by Saturday and see what you need. I can make a beer, drink and food run.<br />
<br />
== Devices & Project Demos ==<br />
<br />
Can you bring some interesting hardware running Linux built with OE? We're especially interested if it shows off the features of OE such as building the same software for multiple boards, ease of OS customisation, etc.<br />
<br />
* Scott Murray - AGL running on up^2 board plus 11" touchscreen<br />
<br />
== Anything else? ==<br />
<br />
If you can bring anything else useful - OE stickers/flyers, power adaptors & cables, etc - let us know here...<br />
<br />
= Attendance =<br />
<br />
If you're attending FOSDEM and want to meet up with other OE & Yocto folk then put your name down here so we can look out for you.<br />
<br />
* Chris Simmonds<br />
* Philip Balister<br />
* Marcin Juszkiewicz<br />
<br />
= Non-Attendance =<br />
<br />
If you're not attending FOSDEM put your name down here so nobody goes looking for you. :)<br />
<br />
* Josef Holzmayr<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 />
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<br />
http://www.ibis.com/gb/hotel-1046-ibis-brussels-off-grand-place/index.shtml</div>MarcinHrwJuszkiewiczhttp://www.openembedded.org/index.php?title=OEDEM_2016&diff=8993OEDEM 20162016-09-28T13:12:10Z<p>MarcinHrwJuszkiewicz: /* Attendees */</p>
<hr />
<div>NOTE: for the OpenEmbedded General Assembly 2016, held the same day at the same location, see the page [[Berlin, 2016]]<br />
<br />
== Location and Time ==<br />
<br />
Friday, October 14 2016<br><br />
(after ELC-E [Oct 11-13])<br />
<br />
Specific location in Berlin will be announced later<br />
<br />
== Attendees ==<br />
<br />
* Andrei Gherzan<br />
* Khem Raj "khem"<br />
* Armin Kuster "Armpit"<br />
* Marco Cavallini "mckoan"<br />
* Pierre-Jean Texier "pjtexier"<br />
* Koen Kooi "koen"<br />
* Anders Darander<br />
* Sean Hudson "darknighte"<br />
* Changhyeok Bae "chbae"<br />
* Peter Kjellerstedt "Saur"<br />
* Josef Holzmayr "LetoThe2nd"<br />
* Vicentiu Neagoe<br />
* Nicolas Dechesne "ndec"<br />
* Denys Dmytriyenko "denix"<br />
* Philip Balister "Crofton"<br />
* Jan Lübbe "shoragan"<br />
* Enrico Jörns<br />
* Jeff Osier-Mixon "Jefro"<br />
* Andrea Galbusera "gizero"<br />
* Richard Purdie "RP"<br />
* Changhyeok bae "chbae"<br />
* Scott Murray "smurray"<br />
* Behan Webster "behanw"<br />
* Jan-Simon Moeller "dl9pf"<br />
* Bruce Ashfield "zediii"<br />
* Marcin Juszkiewicz "hrw"<br />
<br />
== Agenda Items ==<br />
<br />
OpenEmbedded eV General Assembly [[Berlin,_2016]]<br />
<br />
# LTS<br />
# BSPs and layer name recommendations<br />
# Make perl and python distro features? [Saur]<br />
# Support for meson build system? [Saur]<br />
# Can devtool be made standalone, or how to use latest devtool with older version of OE? [Saur]<br />
<br />
== Minutes ==</div>MarcinHrwJuszkiewiczhttp://www.openembedded.org/index.php?title=FOSDEM_2014&diff=6755FOSDEM 20142014-01-21T11:30:20Z<p>MarcinHrwJuszkiewicz: /* 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 - 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 />
<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>MarcinHrwJuszkiewiczhttp://www.openembedded.org/index.php?title=FOSDEM_2013&diff=5481FOSDEM 20132013-01-22T10:07:40Z<p>MarcinHrwJuszkiewicz: I will be there as well</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 />
<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 />
=== Table cloth ===<br />
Can Philip bring table cloths from last year - ?<br />
<br />
=== Bringing an TFT LCD ===<br />
Displaying a presentation during the time of the conference makes our stand visually more attractive. We have a simple OpenDocument presentation in our SCM that can be used for this. However we need a display as well. If you come by car and can transport a display that'd be great.<br />
<br />
Volunteer: ?<br />
<br />
=== Poster ===<br />
A nice poster with updated sponsor was used for 2011's LinuxTag in Berlin. This poster needs to be brought to FOSDEM. Where is it right now and can it be taken to Brussels?<br />
<br />
Volunteer: ?<br />
<br />
=== Flyers ===<br />
Years ago we printed a bunch (2500) of flyers. We still have a bunch of them left (exact number unknown; will update this as soon as I know). As the text is already a few years old it makes sense to update the actual document (it is in openembedded/contrib/marketing/oe-flyer.pdf) and print new ones.<br />
<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 />
<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 />
<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 />
<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.<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>MarcinHrwJuszkiewiczhttp://www.openembedded.org/index.php?title=LayerIndex&diff=4759LayerIndex2012-07-12T15:40:12Z<p>MarcinHrwJuszkiewicz: Added category so it is easier to find it</p>
<hr />
<div>List of metadata layers compatible with [[OpenEmbedded-Core]]:<br />
<br />
{| class="wikitable" border="2"<br />
|| '''Layer name''' || '''Description''' || '''Repo subdir''' || '''Repository''' || '''Repo web''' || '''Setup/Info'''<br />
|-<br />
!colspan="6"|''Base layers''<br />
|-<br />
||openembedded-core||Core metadata||meta||git://git.openembedded.org/openembedded-core||[http://cgit.openembedded.org/cgit.cgi/openembedded-core/ link]||<br />
|-<br />
||meta-oe||Additional shared OE metadata||meta-oe||git://git.openembedded.org/meta-openembedded||[http://cgit.openembedded.org/cgit.cgi/meta-openembedded/ link]||<br />
|-<br />
!colspan="6"|''Board / device support layers <sup>[[#unofficial|1]]</sup>''<br />
|-<br />
||meta-bug||BugLabs bug20 machine support||||git://github.com/buglabs/meta-bug.git||[http://github.com/buglabs/meta-bug link]||<br />
|-<br />
||meta-efikamx||Genesi Efika MX machine support||||git://github.com/kraj/meta-efikamx.git||[http://github.com/kraj/meta-efikamx link]||<br />
|-<br />
||meta-ettus||Ettus machine support||||<nowiki>http://github.com/balister/meta-ettus.git</nowiki>||[http://github.com/balister/meta-ettus link]||<br />
|-<br />
||meta-fsl-arm||Freescale ARM hardware support||||git://github.com/Freescale/meta-fsl-arm.git||[http://github.com/Freescale/meta-fsl-arm link]||<br />
|-<br />
||meta-fsl-ppc||Freescale PowerPC hardware support||||git://git.yoctoproject.org/meta-fsl-ppc||[http://git.yoctoproject.org/cgit/cgit.cgi/meta-fsl-ppc link]||<br />
|-<br />
||meta-gumstix||Gumstix board support||||git://gitorious.org/schnitzeltony-oe-meta/meta-gumstix.git||[http://gitorious.org/schnitzeltony-oe-meta/meta-gumstix link]||<br />
|-<br />
||meta-handheld||Older handheld device support (Zaurus, iPAQ, etc.)||||<nowiki>git://git.openembedded.org/meta-handheld</nowiki>||[http://cgit.openembedded.org/cgit.cgi/meta-handheld link]||[http://www.linuxtogo.org/gowiki/meta-handheld link]<br />
|-<br />
|| meta-hidav || DResearch HidaV (dm8148 based) BSP, SDK, and (Angstrom based) distro. (official) |||| git://github.com/DFE/HidaV.git || [http://github.com/DFE/HidaV link] || [http://github.com/DFE/HidaV/wiki link]<br />
|-<br />
||meta-htc||HTC smartphone support||meta-htc||<nowiki>http://git.shr-project.org/repo/meta-smartphone.git</nowiki>||[http://git.shr-project.org/git/?p=meta-smartphone.git;a=summary link]||<br />
|-<br />
||meta-igep||IGEP board support||||<nowiki>http://github.com/ebutera/meta-igep.git</nowiki>||[http://github.com/ebutera/meta-igep link]||<br />
|-<br />
||meta-intel||Intel board support (official)||||git://git.yoctoproject.org/meta-intel||[http://git.yoctoproject.org/cgit/cgit.cgi/meta-intel/ link]||<br />
|-<br />
||meta-kirkwood||Marvell Kirkwood-based device support||||git://github.com/kelvinlawson/meta-kirkwood.git||[http://github.com/kelvinlawson/meta-kirkwood link]||[http://www.kelvinsthunderstorm.com/open-embedded-for-marvell-kirkwood/ link]<br />
|-<br />
||meta-netbookpro||Psion NetBook Pro device support||||git://github.com/tworaz/meta-netbookpro||[http://github.com/tworaz/meta-netbookpro link]||<br />
|-<br />
||meta-nokia||Nokia N900 support||meta-nokia||<nowiki>http://git.shr-project.org/repo/meta-smartphone.git</nowiki>||[http://git.shr-project.org/git/?p=meta-smartphone.git;a=summary link]||<br />
|-<br />
||meta-nslu2||Linksys NSLU2 device support||||git://github.com/kraj/meta-nslu2||[http://github.com/kraj/meta-nslu2 link]||<br />
|-<br />
||meta-openmoko||OpenMoko device support||meta-openmoko||<nowiki>http://git.shr-project.org/repo/meta-smartphone.git</nowiki>||[http://git.shr-project.org/git/?p=meta-smartphone.git;a=summary link]||<br />
|-<br />
||meta-openpandora||OpenPandora machine support||||git://github.com/openpandora/meta-openpandora.git||[http://github.com/openpandora/meta-openpandora link]||<br />
|-<br />
||meta-palm||Palm Pre machine support||meta-palm||<nowiki>http://git.shr-project.org/repo/meta-smartphone.git</nowiki>||[http://git.shr-project.org/git/?p=meta-smartphone.git;a=summary link]||<br />
|-<br />
||meta-picosam9||Picosam9 board support||||git://gitorious.org/picopc-tools/meta-picosam9.git||[http://gitorious.org/picopc-tools/meta-picosam9 link]||<br />
|-<br />
||meta-raspberrypi||Raspberry Pi board support||||git://github.com/djwillis/meta-raspberrypi.git||[http://github.com/djwillis/meta-raspberrypi link]||[http://blogs.distant-earth.com/wp/?p=377 link]<br />
|-<br />
||meta-samsung||Samsung smartphone support||meta-samsung||<nowiki>http://git.shr-project.org/repo/meta-smartphone.git</nowiki>||[http://git.shr-project.org/git/?p=meta-smartphone.git;a=summary link]||<br />
|-<br />
||meta-ti (was meta-texasinstruments)||Texas Instruments board support (official)||||git://git.yoctoproject.org/meta-ti||[http://git.yoctoproject.org/cgit/cgit.cgi/meta-ti/ link]||<br />
[http://git.yoctoproject.org/cgit/cgit.cgi/meta-ti/tree/README link]<br />
|-<br />
||meta-xilinx||Xilinx hardware support||||git://git.yoctoproject.org/meta-xilinx||[http://git.yoctoproject.org/cgit/cgit.cgi/meta-xilinx link]||<br />
|-<br />
||meta-zynq||Xilinx Zynq hardware support||||git://github.com/balister/meta-zynq.git||[https://github.com/balister/meta-zynq link]||[https://github.com/balister/meta-zynq/wiki/Getting-started link]||<br />
|-<br />
!colspan="6"|''Software support layers''<br />
|-<br />
||meta-arago-extras||Arago/TI extra apps||meta-arago-extras||git://arago-project.org/git/meta-arago.git||[http://arago-project.org/git/?p=meta-arago.git;a=summary link]||[http://arago-project.org/git/?p=meta-arago.git;a=blob;f=meta-arago-extras/README;hb=HEAD link]<br />
|-<br />
||meta-browser||Web browsers (Chromium, Firefox, etc.)||||git://github.com/OSSystems/meta-browser.git||[http://github.com/OSSystems/meta-browser link]||<br />
|-<br />
||meta-chicken||Chicken toolchain support||||git://github.com/OSSystems/meta-chicken||[http://github.com/OSSystems/meta-chicken link]||<br />
|-<br />
||meta-efl||Enlightenment UI support||meta-efl||git://git.openembedded.org/meta-openembedded||[http://cgit.openembedded.org/cgit.cgi/meta-openembedded/ link]||<br />
|-<br />
||meta-fso||freesmartphone.org framework support||meta-fso||<nowiki>http://git.shr-project.org/repo/meta-smartphone.git</nowiki>||[http://git.shr-project.org/git/?p=meta-smartphone.git;a=summary link]||<br />
|-<br />
||meta-games||Open-source games||||git://github.com/cazfi/meta-games.git||[http://github.com/cazfi/meta-games link]||<br />
|-<br />
||meta-gnome||GNOME UI support||meta-gnome||git://git.openembedded.org/meta-openembedded||[http://cgit.openembedded.org/cgit.cgi/meta-openembedded/ link]||<br />
|-<br />
||meta-gpe||GPE UI support (very minimal currently)||meta-gpe||git://git.openembedded.org/meta-openembedded||[http://cgit.openembedded.org/cgit.cgi/meta-openembedded/ link]||<br />
|-<br />
||meta-initramfs||initramfs tools||meta-initramfs||git://git.openembedded.org/meta-openembedded||[http://cgit.openembedded.org/cgit.cgi/meta-openembedded/ link]||<br />
|-<br />
||meta-java||Java support||||git://github.com/woglinde/meta-java||[http://github.com/woglinde/meta-java link]||<br />
|-<br />
||meta-kde||KDE 4 / Plasma Active||||git://gitorious.org/openembedded-core-layers/meta-kde.git||[http://gitorious.org/openembedded-core-layers/meta-kde link]||<br />
|-<br />
||meta-mono||Mono||||git://git.yoctoproject.org/meta-mono.git||[http://git.yoctoproject.org/cgit/cgit.cgi/meta-mono/ link]||[http://git.yoctoproject.org/cgit/cgit.cgi/meta-mono/tree/README link]<br />
|-<br />
||meta-opie||Opie UI support||||git://git.openembedded.org/meta-opie||[http://cgit.openembedded.org/cgit.cgi/meta-opie link]||[http://www.linuxtogo.org/gowiki/meta-opie link]<br />
|-<br />
||meta-osmocombb||OsmocomBB support||meta-osmocombb||<nowiki>http://git.shr-project.org/repo/meta-smartphone.git</nowiki>||[http://git.shr-project.org/git/?p=meta-smartphone.git;a=summary link]<br />
|-<br />
||meta-qt3||Qt 3.x support||||git://git.yoctoproject.org/meta-qt3||[http://git.yoctoproject.org/cgit/cgit.cgi/meta-qt3 link]||<br />
|-<br />
||meta-telephony||Telephony-related software||||git://gitorious.org/sysmocom-openembedded/meta-telephony.git||[http://gitorious.org/sysmocom-openembedded/meta-telephony link]||<br />
|-<br />
||meta-xen||Xen related software||||git://git.se-eng.com/meta-xen.git||[http://git.se-eng.com/gitweb/?p=meta-xen.git;a=summary link]||<br />
|-<br />
||meta-xfce||XFCE UI support||meta-xfce||git://git.openembedded.org/meta-openembedded||[http://cgit.openembedded.org/cgit.cgi/meta-openembedded/ link]||<br />
|-<br />
||toolchain-layer||Older/newer toolchains||toolchain-layer||git://git.openembedded.org/meta-openembedded||[http://cgit.openembedded.org/cgit.cgi/meta-openembedded/ link]||<br />
|-<br />
!colspan="6"|''Distribution layers''<br />
|-<br />
||meta-angstrom||Ångström distribution||||<nowiki>http://github.com/Angstrom-distribution/meta-angstrom.git</nowiki>||[https://github.com/Angstrom-distribution/meta-angstrom.git link]||[https://github.com/Angstrom-distribution/meta-angstrom/blob/master/README link]<br />
|-<br />
||meta-arago-distro||Arago/TI-SDK distribution||meta-arago-distro||git://arago-project.org/git/meta-arago.git||[http://arago-project.org/git/?p=meta-arago.git;a=summary link]||[http://arago-project.org/git/?p=meta-arago.git;a=blob;f=meta-arago-distro/README;hb=HEAD link]<br />
|-<br />
||meta-aurora||aurora distribution||meta-aurora||<nowiki>http://git.shr-project.org/repo/meta-smartphone.git</nowiki>||[http://git.shr-project.org/git/?p=meta-smartphone.git;a=summary link]||<br />
|-<br />
||meta-eldk||Denx ELDK distribution||||git://git.denx.de/eldk.git||[http://git.denx.de/eldk.git/ link]||[http://www.denx.de/wiki/view/ELDK-5/GitRepositorySetup link]<br />
|-<br />
||meta-micro||micro distribution||||git://git.openembedded.org/meta-micro||[http://cgit.openembedded.org/cgit.cgi/meta-micro/ link]||<br />
|-<br />
||meta-shr||SHR distribution||meta-shr||<nowiki>http://git.shr-project.org/repo/meta-smartphone.git</nowiki>||[http://git.shr-project.org/git/?p=meta-smartphone.git;a=summary link]||[http://shr-project.org/trac/wiki/Building%20SHR link]<br />
|-<br />
||meta-slugos||SlugOS distribution||||git://github.com/kraj/meta-slugos||[http://github.com/kraj/meta-slugos link]||[https://github.com/kraj/slugos-setup link]<br />
|-<br />
||meta-woce||WebOS community Edition distribution||||git://github.com/kraj/meta-woce||[http://github.com/kraj/meta-woce link]||[https://github.com/kraj/woce-setup link]<br />
|-<br />
<br />
!colspan="6"|''Miscellaneous''<br />
|-<br />
||meta-yocto||Integration layer for the Yocto Project||meta-yocto||git://git.yoctoproject.org/poky||[http://git.yoctoproject.org/cgit/cgit.cgi/poky/ link]||[http://www.yoctoproject.org/docs/yocto-quick-start/yocto-project-qs.html link]<br />
|-<br />
|}<br />
<br />
<span id="unofficial"><sup>1</sup> Note: machine support layers are unofficial and not manufacturer-supported unless noted otherwise.</span><br />
<br />
[[Category:Dev]]</div>MarcinHrwJuszkiewiczhttp://www.openembedded.org/index.php?title=User:MarcinHrwJuszkiewicz&diff=4545User:MarcinHrwJuszkiewicz2012-01-16T07:34:25Z<p>MarcinHrwJuszkiewicz: </p>
<hr />
<div>* OpenEmbedded developer since 2003<br />
* Poky developer 2007-2009<br />
* OpenZaurus maintainer from 2005 to the end (2007)<br />
* BUG Labs developer 2008-2010<br />
<br />
= Contact =<br />
<br />
Jabber: hrw@jabber.org<br />
<br />
E-mail: marcin@juszkiewicz.com.pl<br />
<br />
Website: http://marcin.juszkiewicz.com.pl/</div>MarcinHrwJuszkiewiczhttp://www.openembedded.org/index.php?title=Fosdem_2012&diff=4543Fosdem 20122012-01-16T07:33:02Z<p>MarcinHrwJuszkiewicz: added info about flyers + hotel which some of us used in 2011</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 />
* Robert Schuster (Saturday, Sunday)<br />
* Alex Lennon (Saturday, Sunday)<br />
* Henning Heinold (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 />
=== Table cloth ===<br />
We only have a single table cloth (it washed but has a negligible stain from a quick soldering action that happened last year). We definitely need a 2nd one to also cover our second table. The FOSDEM tables are pretty huge (2.5m length), so chose a reasonably sized cloth. Additionally it would be super cool to have the OpenEmbedded logo printed on it. The idea would be to show the logo on the front side of our tables. For that the 'OE' sign should not be taller than say 50cm (The tables are approximately 70cm high.).<br />
<br />
Volunteer:<br />
<br />
=== Bringing an TFT LCD ===<br />
Displaying a presentation during the time of the conference makes our stand visually more attractive. We have a simple OpenDocument presentation in our SCM that can be used for this. However we need a display as well. If you come by car and can transport a display that'd be great. Getting a screen is not so complicated. Robert Schuster could send one to you by mail.<br />
<br />
Volunteer:<br />
<br />
=== Poster ===<br />
A nice poster with updated sponsor was used for 2011's LinuxTag in Berlin. This poster needs to be brought to FOSDEM. Where is it right now and can it be taken to Brussels?<br />
<br />
Volunteer:<br />
<br />
=== Flyers ===<br />
Years ago we printed a bunch (2500) of flyers. We still have a bunch of them left (exact number unknown; will update this as soon as I know). As the text is already a few years old it makes sense to update the actual document (it is in openembedded/contrib/marketing/oe-flyer.pdf) and print new ones.<br />
<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 />
Robert Schuster - Pandaboard - Hopefully booting Angstrom with some desktop and Java foo.<br />
<br />
Alex Lennon - Gem (i.MX28 based telematics board) - Booting OpenEmbedded with an end-user demo running (hopefully)<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 />
<br />
* Robert Schuster:<br />
**3-socket power extension (EU)<br />
**tape<br />
**WiFi-Router in client mode to provide Internet access for Ethernet-based devices<br />
**2 1m-Ethernet cables<br />
<br />
= General attendance =<br />
<br />
Attending FOSDEM 2012? Add your name to this page so that other developers can look out for you!<br />
<br />
* Robert Schuster (rschus/thebohemian)<br />
* Henning Heinold (woglinde)<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.<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.</div>MarcinHrwJuszkiewiczhttp://www.openembedded.org/index.php?title=Getting_started_with_OE-Classic&diff=3570Getting started with OE-Classic2010-11-25T15:06:57Z<p>MarcinHrwJuszkiewicz: Reverted edits by JamesCowan (Talk) to last revision by Eric</p>
<hr />
<div>= Setting up the toolchain and doing a build =<br />
<br />
Before starting to configure your OE installation by following the instructions on this page make sure you have read [[OEandYourDistro|how OE fits in with your host distribution]] and the [[RequiredSoftware|required software for compilation]].<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 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 want 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 />
Laibsch also provides a [http://oss.leggewie.org/oe/deb/bitbake_1.8.18-1_all.deb deb-package for bitbake 1.8.18] that should work in all current Ubuntu and Debian releases.<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 this:<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 Git:<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>MarcinHrwJuszkiewiczhttp://www.openembedded.org/index.php?title=Category:Community&diff=3551Category:Community2010-11-24T09:41:31Z<p>MarcinHrwJuszkiewicz: Reverted edits by Ejumuvo (Talk) to last revision by Laibsch</p>
<hr />
<div>Various Community resources</div>MarcinHrwJuszkiewiczhttp://www.openembedded.org/index.php?title=Common_mistakes_in_a_recipe&diff=3550Common mistakes in a recipe2010-11-24T09:41:19Z<p>MarcinHrwJuszkiewicz: Reverted edits by Ejumuvo (Talk) to last revision by 75.172.121.11</p>
<hr />
<div>This page should list common (!) mistakes when defining a recipe. a link or one sentence explaining what the problem is are a bonus. But keep it short!<br />
<br />
= (R)DEPENDS, etc. =<br />
<br />
libiconv in (R)DEPENDS<br />
: Use "virtual/libiconv" instead as glibc based systems already have libiconv functionality from glibc. Uclibc based systems will get it from "libiconv". By building libiconv in glibc build You risk a corrupted TMPDIR which will need to be restarted from scratch.<br />
<br />
kernel modules in RDEPENDS<br />
: Never use RDEPENDS to drag kernel modules into an image, use RRECOMMENDS instead. The reason is that some devices can have those modules built-in into kernel.<br />
<br />
[[Category:Dev]]<br />
[[Category:FAQ]]</div>MarcinHrwJuszkiewiczhttp://www.openembedded.org/index.php?title=How_to_help_out&diff=3549How to help out2010-11-24T09:41:18Z<p>MarcinHrwJuszkiewicz: Reverted edits by Ejumuvo (Talk) to last revision by Laibsch</p>
<hr />
<div>'''OE is great and I want to contribute something back. How?'''<br />
<br />
That of course depends on your skills. But you don't need to be an Überhacker to be welcome in the OE community. This is an absolutely non-complete list of things you might want to consider<br />
<br />
* tell others about your positive experience with OE<br />
* donate some money (tax-deductible!) to the [[Organization|e.V.]]<br />
* try to verify, refute or fix some [http://tinderbox.openembedded.net/packages/?status=Failed compile failures] or [http://bugzilla.openembedded.org other bugs]<br />
* Help out with the [http://docs.openembedded.org/usermanual/usermanual.html documentation]. The source is controlled in our [http://cgit.openembedded.net/cgit.cgi?url=openembedded/tree/docs/usermanual git repo]<br />
* Help us [[push patches upstream]] or participate in our [[bug days]]<br />
* add another entry to this list of how to help, yes, that would help us, too ;-)<br />
<br />
[[Category:FAQ]]<br />
[[Category:User]]</div>MarcinHrwJuszkiewiczhttp://www.openembedded.org/index.php?title=Tinderbox&diff=3548Tinderbox2010-11-24T09:41:16Z<p>MarcinHrwJuszkiewicz: Reverted edits by Ejumuvo (Talk) to last revision by Sledz</p>
<hr />
<div>Using [http://opensource.bolloretelecom.eu/projects/oestats/wiki/oestats oestats] for your builds.<br />
<br />
For your builder to send reports to our [http://tinderbox.openembedded.org QA server], you need to edit your build/conf/local.conf to make use of the oestats-client.bbclass class.<br />
<br />
INHERIT += "oestats-client" <br />
OESTATS_SERVER = "tinderbox.openembedded.org" <br />
OESTATS_BUILDER = "your_nickname"<br />
<br />
[[Category:FAQ]]<br />
[[Category:Quality Assurance]]</div>MarcinHrwJuszkiewiczhttp://www.openembedded.org/index.php?title=%C5ngstr%F6m&diff=35472010-11-24T09:41:14Z<p>MarcinHrwJuszkiewicz: Reverted edits by Ejumuvo (Talk) to last revision by Cbrake</p>
<hr />
<div>[http://www.angstrom-distribution.org Angstrom]<br />
<br />
[[Category:Distro]]</div>MarcinHrwJuszkiewiczhttp://www.openembedded.org/index.php?title=Documentation&diff=3546Documentation2010-11-24T09:41:13Z<p>MarcinHrwJuszkiewicz: Reverted edits by Ejumuvo (Talk) to last revision by Slyon</p>
<hr />
<div>Documentation that relates to Openembedded.<br />
<br />
* [http://docs.openembedded.org/usermanual/html OE User manual] [http://docs.openembedded.org/usermanual/usermanual.pdf (pdf)] [http://docs.openembedded.org/usermanual/usermanual.html (html single-page)]<br />
* [http://docs.openembedded.org/bitbake/html/ Bitbake Manual]<br />
* [http://www.pokylinux.org/doc/poky-handbook.html Poky Handbook]<br />
<br />
Articles about Openembedded:<br />
* [http://bec-systems.com/site/tag/openembedded articles at BEC Systems]<br />
** [http://bec-systems.com/site/456/capture-oe-source-changes How to Capture OE Source Code Changes to a Package]<br />
<br />
Guides and HowTos:<br />
* [[How to create a bitbake recipe for dummies]]<br />
* [[How to submit a patch for dummies]]<br />
* [http://www.kernel-labs.org/files/openembedded-guide/openembedded-guide.html OpenEmbedded Guide by Example]<br />
* [http://www.uv-ac.de/openembedded/ OpenEmbedded HowTo]<br />
* [http://free-electrons.com/docs/openembedded/ Using OpenEmbedded to build embedded Linux distributions]<br />
<br />
[[Category:User]]<br />
[[Category:Dev]]</div>MarcinHrwJuszkiewiczhttp://www.openembedded.org/index.php?title=Fetch_from_secure_CVS_and_SVN&diff=3543Fetch from secure CVS and SVN2010-11-24T09:40:30Z<p>MarcinHrwJuszkiewicz: Reverted edits by Ejumuvo (Talk) to last revision by Laibsch</p>
<hr />
<div>'''Q: bitbake fetch breaks on a secure connections for svn or cvs, what shall I do?'''<br />
<br />
A: bitbake/OE has [http://bugs.openembedded.net/show_bug.cgi?id=2501 a bit of a problem with https for cvs and svn] checkouts. You need to run "svn info $svnhost" once and permanently accept the certificate before you can fetch sources for OE.<br />
<br />
[[Category:FAQ]]</div>MarcinHrwJuszkiewiczhttp://www.openembedded.org/index.php?title=Oedem/2009&diff=3542Oedem/20092010-11-24T09:40:29Z<p>MarcinHrwJuszkiewicz: Reverted edits by Ejumuvo (Talk) to last revision by Sledz</p>
<hr />
<div>OpenEmbedded developers' meeting 2009 will be in Cambridge, UK on the weekend of November 7/8.<br />
<br />
All developers and other interested parties are welcome.<br />
<br />
==Location==<br />
<br />
Reciva Ltd have generously offered to host the meeting at their offices: 509 Coldhams Lane, Cambridge, CB1 3JS.<br />
<br />
The Reciva offices are on the east side of the city, about 2km from the centre of town. See below for detailed travel information.<br />
<br />
Call Phil on +44 7973 869202 if you get hopelessly lost and cannot find the venue.<br />
<br />
==Agenda==<br />
<br />
===Friday 2009-11-06===<br />
<br />
20:00 (approx) Pre-meeting beer session at the Red Lion, Histon, CB24 9BD<br />
<br />
http://maps.google.co.uk/maps?f=q&source=s_q&hl=en&geocode=&q=cb24+9jd&sll=53.800651,-4.064941&sspn=11.25,27.905273&ie=UTF8&ll=52.253684,0.105486&spn=0.011375,0.027251&t=h&z=15&iwloc=A<br />
<br />
From the city centre, ride the [http://www.stagecoachbus.com/timetables/Citi7Jan09%5B3%5D.pdf Citi 7] bus towards Cottenham. Pass Histon village green (pond with ducks) on your right, the Boot and Barley Mow pubs on your left, then alight at the next stop and you will be almost directly outside the Red Lion. Travel time from the city is approximately 25 minutes and a return ticket costs about £3. Other travel options include taxi (10-15 minutes, about £10 each way) or walking (50-60 minutes, no charge). <br />
<br />
===Saturday 2009-11-07===<br />
<br />
10:00-10:15 Welcome + Agenda<br />
<br />
: Introductions and discussion/confirmation of agenda<br />
: some entries will need to be moved as few of us will have to leave earlier on Sunday (Henning, Marcin and Marco have train at 17:10)<br />
<br />
10:15-12:00 OE e.V. meeting (Mickey Lauer / e.V. board)<br />
<br />
: '''e.V. Membership Fees'''<br />
<br />
: As per our statutes, members can chose their membership fees. We should create recommendations for corporate entities (also indicate what they would gain by that).<br />
: '''Travel reimbursement policy'''<br />
: '''Financial status'''<br />
: '''Sponsors: announcement, website and memberships'''<br />
: '''Public relations committee'''<br />
<br />
12:00-13:00 Establishment of technical steering committee (Phil Blundell)<br />
<br />
13:00-14:00 Break for lunch / hacking session<br />
<br />
14:00-15:00 OE and Poky (Mickey Lauer)<br />
<br />
15:00-16:00 Software development for OE derived distributions<br />
<br />
* Quick presentation of KOBE (Eclipse plugin by KOAN for recipe creation and more)<br />
<br />
People always want to develop software for the target hardware, what can we do to make developers lives easier? The answer is not always use bitbake. How do we supply toolchains, libraries etc? How are people solving this today?<br />
<br />
16:00-16:30 Learning to love USE flags, or, What's a distro for? (Phil Blundell)<br />
<br />
16:30-17:00 State of the art in package management (Phil Blundell)<br />
<br />
* Why is opkg so bad?<br />
* What alternatives are there?<br />
* What can we do to improve the situation?<br />
<br />
17:00-18:00 Hacking session<br />
<br />
18:00 Venue closes<br />
<br />
===Sunday 2009-11-08===<br />
<br />
10:00-11:00 Splitting the recipes tree (Mickey Lauer)<br />
<br />
: Many of us feel we should split the recipes up into a couple of smaller categories to be able to handle them in a more efficient way (parsing, switching on/off, etc.), but also to indicate which packages are critical / very well maintained / not maintained at all / ...<br />
<br />
11:00-12:00 Future plans for stable branch(es)<br />
<br />
* Why stable branch is actually not so stable?<br />
* Creation of long term support branch?<br />
<br />
12:00-13:00 Bugtracker Discussion, what to do with the current bugzilla, replace/enhance/abandon. (Graeme 'XorA' Gregory)<br />
<br />
13:00-14:00 Break for lunch/hacking<br />
<br />
14:00-15:00 Hosting arrangements (Mickey Lauer) (see [[Infrastructure]])<br />
<br />
: There are still services on amethyst, although former-admin Mickey has requested them to be moved. Obviously some one needs to take the wheel here.<br />
<br />
: Services on Amethyst:<br />
<br />
* patchwork.openembedded.org<br />
* wiki.openembedded.org<br />
* www.openembedded.org<br />
<br />
: Git repository management issues:<br />
<br />
* Clearly identify user branches with a namespace?<br />
* Rename org.openembedded.dev to master?<br />
* CIA commit hook should only report dev branch changes?<br />
<br />
15:00-16:00 Death to checksums.ini? (Phil Blundell)<br />
<br />
: The current method of tracking and verifying checksums on source tarballs has various drawbacks and, due to a combination of technical and social issues, seems to bring few benefits. Can we do any better?<br />
<br />
16:00-17:00 BitBake Future Roadmap (Richard Purdie)<br />
<br />
17:00-18:00 OE Core Changes (Richard Purdie)<br />
<br />
: Discuss various possible core changes to OE such as those to the do_stage process, layout variable changes, Candian SDK Generation. Any others planned?<br />
<br />
18:00 Go home<br />
<br />
==Travel==<br />
<br />
London Stansted airport is the nearest to Cambridge with regular service. <br />
(There is a small airport in Cambridge itself but I don't think any scheduled<br />
airlines operate from there anymore.)<br />
<br />
For those travelling from Europe, Stansted is about a 30-minute train ride from Cambridge city centre and is served by Air Berlin, Ryanair and Germanwings among others. Luton airport is about 1 hour away by bus and is served by Easyjet.<br />
<br />
For those travelling from further away, most long-haul flights arrive at Heathrow or Gatwick airports (although there is some transatlantic service into Stansted). Both Heathrow and Gatwick are about 2 hours from Cambridge by train or bus: the train is quicker but involves several changes in London, whereas the bus is slow but cheaper and less complicated.<br />
<br />
If arriving at LHR airport, take the [http://thetube.com Piccadilly line] from the Underground station and ride it all the way to Kings Cross St Pancras. Ascend to street level, follow signs to Kings Cross mainline station (not St Pancras: the two stations are different although they share a subway stop) and then look for trains to Cambridge or Kings Lynn on the departure board. There are usually two fast services and two slow services to Cambridge per hour: the slow trains are often overtaken by the fast ones en route so it may be best to wait for a fast service even if this is not the next to depart.<br />
<br />
If arriving at LCY, take the [http://www.tfl.gov.uk/gettingaround/2558.aspx#London_City_Airport DLR] to Bank, then change to the Northern Line northbound. From Kings Cross St Pancras, proceed as for LHR, above.<br />
<br />
http://nationalrail.co.uk<br />
<br />
http://nationalexpress.co.uk/<br />
<br />
Alternatively you can take the Eurostar to London St Pancras, which is 50 minutes from Cambridge by train.<br />
<br />
=== Directions from Cambridge rail station to Reciva HQ ===<br />
<br />
'''By bus''' (approximate travel time 30 minutes)<br />
<br />
- take Citi 1 bus towards Fulbourn, alight at St Andrews church in Cherry Hinton, then walk down Coldhams Lane for about 500 metres. Our building will be on your right and has a large sign on the front reading "Semitool". The Citi 1 route runs 7 days a week, about every ten minutes during the daytime, less often (but still fairly frequent) in the evenings.<br />
<br />
- alternatively, take any bus to the city centre and then catch service 16 going out of town (the city centre is a terminus on this route). Alight at the first stop after the Rosemary Branch pub on Coldhams Lane and you will be directly outside the office. Note that bus #16 only runs once per hour so check departure times before choosing this route.<br />
<br />
http://www.cambridgeshire.gov.uk/transport<br />
<br />
http://www.stagecoachbus.com/cambridge<br />
<br />
'''On foot''' (approximate travel time 45 minutes) or bike (approx 15 minutes)<br />
<br />
- Turn right immediately in front of the station and cross the car park, passing the hotel and cycle shop on your left.<br />
<br />
- Upon exiting the car park, go up the steps to the cycle/footbridge and cross to the other side of the railway line.<br />
<br />
- Exit the bridge and turn left, then immediately right into Greville Road.<br />
<br />
- At the end of Greville Road, go left on Coleridge Road. Cross at the pedestrian crossing and go through the chicane onto the footpath opposite.<br />
<br />
- Proceed down Marmora Road. Cross Hobart Road and proceed down the footpath.<br />
<br />
- Go left into Montreal Road, then right into Natal Road.<br />
<br />
- Go left on Perne Road. At the lights, cross to the other side and go down Brookside.<br />
<br />
- When the road bends to the right, do not follow the curve but instead take the footpath directly ahead (across a small bridge). Follow the path until you arrive at the Holiday Inn Express.<br />
<br />
- Bear left onto Norman Way. Ascend out of the pit to the traffic lights next to the car dealership.<br />
<br />
- Turn right onto Coldhams Lane, then cross to the other side of the street. Pass the yellow self-storage depot, then Reciva HQ is the next building on your left.<br />
<br />
See [http://walkit.com walkit.com] for other route suggestions. The train station is at postcode CB1 2JB. The meeting venue is at CB1 3JS, although walkit (and most map sites, including google) place this about 500 metres too far southeast.<br />
<br />
===Directions to venue by car===<br />
<br />
'''From all points north and west'''<br />
<br />
From the A1 or A10, take the A14 eastbound. Proceed along the Cambridge northern bypass. Leave at junction 35 (for Quy, Newmarket) and take the A1303 towards Cambridge, following signs towards the airport. Turn left at the next roundabout (by the corner of the airport) towards Cherry Hinton. At the next roundabout, go straight ahead into the traffic calmed area. Cross one mini-roundabout, then two in quick succession, then turn right at the traffic lights. Look for a building on your right labelled "SEMITOOL"; this is the meeting venue. If you reach the Rosemary Branch pub and Toyota dealership, you have gone too far.<br />
<br />
==Accommodation==<br />
<br />
The nearest full-service hotel is Holiday Inn Express, http://www.expresscambridge.co.uk/<br />
<br />
Cheapest accomodation is probably the YHA hostel, http://www.yha.org.uk/find-accommodation/east-of-england/hostels/Cambridge/index.aspx<br />
<br />
There are various bed-and-breakfast establishments nearby, prices start at approx £35/night<br />
<br />
Some other hotels in Cambridge: <br />
<br />
http://www.crowneplaza.co.uk/ <br />
<br />
http://www.devere.co.uk/our-locations/university-arms <br />
<br />
http://www.hilton.co.uk/cambridgegardenhouse<br />
<br />
http://www.arundelhousehotels.co.uk/<br />
<br />
==Food and drink==<br />
<br />
There are no catering facilities on site at the meeting venue. Coffee, tea and water are provided, but bringing your own snack/lunch is recommended. There are shops within about 15 minutes' walk where provisions can be purchased.<br />
<br />
==Attending for sure==<br />
<br />
* Philip Balister<br />
* Michael Lauer<br />
* Marco Cavallini<br />
* Richard Purdie<br />
* Marcin Juszkiewicz<br />
* Henning Heinold<br />
* Robert Schuster<br />
* Florian Boor<br />
* Denys Dmytriyenko<br />
* Ken Gilmer<br />
* Esben Haabendal<br />
* Jonathan Cameron<br />
<br />
[[Category:OEDEM]]</div>MarcinHrwJuszkiewiczhttp://www.openembedded.org/index.php?title=OpenEmbedded_Tools_for_Eclipse_(OTE)&diff=3541OpenEmbedded Tools for Eclipse (OTE)2010-11-24T09:40:28Z<p>MarcinHrwJuszkiewicz: Reverted edits by Ejumuvo (Talk) to last revision by Cbrake</p>
<hr />
<div>= Overview =<br />
<br />
OpenEmbedded Tools for Eclipse (OTE) is a set of Eclipse plugins to make using OpenEmbedded from within Eclipse possible. This page describes a set of workflows that perform common OpenEmbedded tasks, as well as the current state of development of the plugins.<br />
<br />
= Status =<br />
<br />
OTE is in a beta form. Functionality present within the plugins should work well, but development on them is fairly new. Bugs are expected!<br />
<br />
== Current Work as of 12/24/09 ==<br />
* Documentation<br />
* Bug Fixes<br />
<br />
== Version ==<br />
<br />
Current available version is <tt>0.7.0</tt>.<br />
<br />
== Changelog ==<br />
<br />
=== <tt>0.7.0</tt> ===<br />
* Numerous fixes in <b>Create Project Wizard</b> to sync to latest OE-Dev install.<br />
<br />
== License ==<br />
<br />
OTE is licensed under the [http://www.eclipse.org/legal/epl-v10.html Eclipse Public License (EPL)]. <br />
<br />
== Source ==<br />
<br />
Sources are available at svn://svn.buglabs.net/ote/trunk.<br />
<br />
== Updatesite ==<br />
<br />
The OTE updatesite, used to install the plugins from within Eclipse:<br />
<br />
http://bugcommunity.com/downloads/files/ote/updatesite/<br />
<br />
= Workflow =<br />
OTE is designed to facilitate a set of typical actions or tasks that an OE developer would do.<br />
<br />
== Install OpenEmbedded ==<br />
1. To install a new copy of OpenEmbedded, select the wizard from the <tt>File -> New... -> Other...</tt> menu.<br />
[[Image:Ote create project wizard 1.png]]<br />
<br />
<br />
2. Next, select the flavor of OpenEmbedded you wish to install.<br />
[[Image:Ote create project wizard 2.png]]<br />
<br />
<br />
3. Now specify configuration parameters. If fields are unfamiliar, leave the defaults and proceed.<br />
[[Image:Ote create project wizard 3.png]]<br />
<br />
<br />
4. Assuming all the necessary system tools are available, the wizard will download sources and configure your new OpenEmbedded install.<br />
<br />
<br />
[[Image:Ote create project wizard 4.png]]<br />
<br />
5. Now by clicking finish, an Eclipse project will be created. It may take a few moments for Eclipse to index all the files in the project. Your workbench should look something like this:<br />
<br />
[[Image:Ote workbench 1.png]]<br />
<br />
== Import Existing OE into Workspace ==<br />
To access the Import Project wizard, select <tt>File -> Import...</tt> and select the <b>Import OpenEmbedded Project</b> wizard from the general dialog like so:<br />
<br />
[[Image:Ote import project wizard 1.png]]<br />
<br />
Next fill in the three fields required for importing the project. <br />
* Name: this is the name of the Eclipse project in your workspace and can be anything.<br />
* Location: this is the base directory of your OpenEmbedded project.<br />
* Init Script: this is the shell script that initializes OE environment variables and updates the path.<br />
<br />
[[Image:Ote_import_project_wizard_2.png]]<br />
<br />
The final wizard page shows the output of what you would see in the terminal after executing <tt>bitbake -e</tt>.<br />
<br />
[[Image:Ote_import_project_wizard_3.png]]<br />
<br />
After clicking finish a new project should be available in your workspace. Depending on your machine it may take some moments for Eclipse to scan the entire set of files. It is important to note that even though the project appears in your Eclipse workspace, the files are accessed from your OE project root. So, modifications to these files will be reflected in your existing OE install.<br />
<br />
== Create Recipe ==<br />
<br />
This simple wizard generates a template recipe file based on fields that are entered by the user. The wizard can be accessed via <tt>File -> New...</tt> and selecting New OpenEmbedded Recipe from the dialog. Here is what the wizard looks like:<br />
<br />
[[Image:Ote create recipe wizard 1.png]]<br />
<br />
Now by entering the fields and selecting <b>Finish</b> a new recipe will be generated. Note that currently the Location field must contain a valid directory, so if you're creating a completely new recipe you'll need to create the directory before running this wizard. Here is an example of a recipe filled out:<br />
<br />
[[Image:Ote create recipe wizard 2.png]]<br />
<br />
After clicking <b>Finish</b> Eclipse will open an editor on the generated file. Here is an example:<br />
<br />
[[Image:Ote create recipe wizard 3.png]]<br />
<br />
From here the user can add necessary details to the recipe for building.<br />
<br />
== Edit Recipe ==<br />
<br />
<br />
<br />
Recipes can be selected in the Navigator view by opening the <tt>recipes</tt> or <tt>packages</tt> directory in your OpenEmbedded install. Any file with a <tt>.bb, .inc</tt> or <tt>.conf</tt> extension will be loaded by the BitBake editor. This editor offers the following features.<br />
=== Find Recipe ===<br />
Eclipse offers a nice file selection dialog that allows for files to be quickly edited without navigating through many folders. This dialog is activated with <tt>ctrl-shift-r</tt>. The 'r' stands for resource, Eclipse terminology for a file. In this dialog begin typing the file you want to edit. Wildcards and regular expressions are supported. Previously edited files are already available. Here is a screenshot of the dialog:<br />
<br />
[[Image:Ote_resource_browser_1.png]]<br />
<br />
=== Syntax Highlighting ===<br />
The recipe file in the editor will color various sections of the recipe. For example comments will be green, variable declarations will be blue.<br />
=== Variable Auto-Completion ===<br />
Some conventional variables are available by hitting <tt>ctrl-space</tt> in the editor window. Here is a screenshot of the context menu:<br />
<br />
[[Image:Ote_edit_recipe_3.png]]<br />
=== Function Templates ===<br />
The bitbake editor will create a template function or <tt>addtask</tt> declaration when selected from the <tt>ctrl-space</tt> menu.<br />
=== Hover-over Variable Information ===<br />
The bitbake editor will show the value of previously declared variables when the mouse is put over them. The appear as tooltip text. Here is an example of this feature:<br />
<br />
[[Image:Ote_edit_recipe_2.png]]<br />
<br />
== Build Recipe ==<br />
<br />
A package can be generated from Eclipse via the toolbar or the context menu. This function essentially calls <b><tt>bitbake -b <selected package></tt></b> to perform the build. The output of the <tt>bitbake</tt> command will be displayed in the console view.<br />
<br />
== Import Recipe Sources as New Project ==<br />
<br />
This allows application developers to create a source project from an OpenEmbedded recipe. This is a simple way to begin modifying a project from within Eclipse. Other Eclipse plugins such as [http://www.eclipse.org/cdt/ CDT (C/C++ development tools)] or [http://pydev.org/ PyDev (Python development tools)] may be used with these imported projects. However automatic integration is not supported from within OTE and adding appropriate project natures will either need to be done from within the respective plugin or manually by editing the <tt>.project</tt> file in your project.<br />
<br />
== Browse OE variables ==<br />
OTE provides a quick way of viewing and searching through BitBake/OE variables. The wizard is activate from the OTE toolbar and looks like this:<br />
<br />
[[Image:Ote variable browser 1.png]]<br />
<br />
= Contact =<br />
Concerning questions or problems with OTE, please contact Ken Gilmer (kgilmer at gmail.com).<br />
<br />
[[Category:User]]</div>MarcinHrwJuszkiewiczhttp://www.openembedded.org/index.php?title=MVL6&diff=3540MVL62010-11-24T09:40:27Z<p>MarcinHrwJuszkiewicz: Reverted edits by Ejumuvo (Talk) to last revision by Laibsch</p>
<hr />
<div>The [http://mvista.com/product_detail_mvl6.php MontaVista Linux 6] product includes an Integration Platform, which includes BitBake and facilitates delivery of OpenEmbedded based metadata collections, to be used by MontaVista customers in the creation of the Linux Distribution for their devices. This is rather different from the standard usage of OpenEmbedded, as MontaVista is shipping it, rather than just using it themselves.</div>MarcinHrwJuszkiewiczhttp://www.openembedded.org/index.php?title=Category_talk:FAQ&diff=3538Category talk:FAQ2010-11-24T09:40:24Z<p>MarcinHrwJuszkiewicz: Reverted edits by Ejumuvo (Talk) to last revision by Sledz</p>
<hr />
<div>= Old Wiki Faq =<br />
<br />
<br />
The old wiki installation seems to have eaten the FAQ page. Let's try to restore some of the information from [http://web.archive.org/web/20070222090436/www.openembedded.org/node/28/edit web.archive.org], this will need to be compared with [http://74.125.39.104/search?q=cache%3Aoe.linuxtogo.org%2Fnode%2F28%2Fdiff%2F1140&ie=utf-8&oe=utf-8&aq=t&rls=com.ubuntu:en-US:unofficial&client=firefox-a the last known-good version] from google (mark all text on that page to make it visible). Content still to be moved follows<br />
<br />
--[[User:Laibsch|Laibsch]] 23:08, 4 June 2008 (UTC)<br />
<br />
= Development =<br />
<br />
== 1. what does OpenEmbedded keyword X do? ==<br />
Check out the documentation in the following file: http://www.openembedded.org/repo/org.openembedded.dev/conf/documentation.conf<br />
<br />
== 2. How can I make bitbake to use a specific version of <tool>? ==<br />
See [http://www.openembedded.org/search/node/PREFERRED_VERSION PREFERRED_VERSION]<br />
<br />
== 3. How can I make bitbake use proxychains when doing cvs operations? ==<br />
See [http://www.openembedded.org/search/node/FETCH_COMMAND FETCH_COMMAND] and [http://www.openembedded.org/search/node/UPDATE_COMMAND UPDATE_COMMAND]<br />
<br />
== 4. What is the easiest way to convert Debian ARM packages to ipkg's (if size doesn't matter)? ==<br />
mv foo.deb foo.ipk<br />
<br />
== 5. How do I add a package to OE? ==<br />
Most of the time adding a package to OE will not be as easy as 1-2-3. Many software developers do not cross-compile their packages and are generally unaware of [[Users Manual/Rules Of Thumb|good design decisions]] that facilitate or break cross-compilation.<br />
<br />
== 6. How can I do a recursive make? ==<br />
<br />
Implement a structure along the following lines.<br />
<br />
do_compile {<br />
for i in dir; oe_runmake ...; done<br />
}<br />
<br />
== 7. How do I set a variable according to the kernel version of the package being built? ==<br />
<br />
Use base_conditional in the following manner:<br />
<br />
CFLAGS_append = '${@base_conditional("KERNEL_MAJOR_VERSION", "2.6", " -D__Linux26__ ", " -D__Linux24__ ",d)}'<br />
<br />
In the example above ''-D__Linux26__'' will be added to the existing CFLAGS if the kernel is 2.6 and ''-D__Linux24__'' if the kernel is 2.4<br />
<br />
<br />
== 8. What is ARM EABI and how do I use it? ==<br />
ARM EABI is the informal name for the ABI for the ARM Architecture standard developed by ARM Ltd and others. This standard explains how tools should generate object and excecutable files.<br />
* http://www.codesourcery.com/gnu_toolchains/arm/faq.html#q_gnu_linux_long_long<br />
* http://www.arm.com/products/DevTools/ABI.html<br />
* http://wiki.debian.org/ArmEabiPort<br />
<br />
To instruct OE to build EABI parts, you typically need the following in your distro conf file:<br />
TARGET_OS=-gnueabi<br />
See the Angstrom distro for an example: http://www.openembedded.org/repo/org.openembedded.dev/conf/distro/angstrom.conf<br />
http://www.openembedded.org/repo/org.openembedded.dev/conf/distro/angstrom-2006.9.conf<br />
<br />
You also need to make sure your kernel has the needed support. From the codesourcery faq, you need the following:<br />
* CONFIG_EABI must be enabled<br />
* Kernel must include support for NPTL<br />
* kernel versions earlier than 2.6.17 should be avoided<br />
<br />
== 9. What is NPTL and how do I use it in OE? ==<br />
NPTL is the Native POSIX Thread Library which is a software feature that enables the Linux kernel to run programs written to use POSIX Threads very efficiently. It is meant to replace an older implementation named Linuxthreads.<br />
* [http://en.wikipedia.org/wiki/LinuxThreads]<br />
* [http://en.wikipedia.org/wiki/Native_POSIX_Thread_Library]<br />
* to check what threading library you have, run the following command: getconf GNU_LIBPTHREAD_VERSION. You can also type: <br />
/lib/libc.so.6 to get information on what threading lib is used.<br />
<br />
There are two options for threading (from pb email):<br />
* With linuxthreads, you need glibc-initial, then gcc-cross-initial,<br />
then glibc, then gcc-cross.<br />
* With nptl, you need glibc-initial, then gcc-cross-initial, then<br />
glibc-intermediate, then gcc-cross, then glibc.<br />
<br />
To use linuxthreads, you need something like the following:<br />
PREFERRED_PROVIDER_virtual/${TARGET_PREFIX}libc-for-gcc = glibc<br />
<br />
For NPTL, this becomes:<br />
PREFERRED_PROVIDER_virtual/${TARGET_PREFIX}libc-for-gcc = glibc-intermediate<br />
<br />
<br />
== 10. How do I apply for read-write status to the OpenEmbedded monotone repo? ==<br />
<br />
Hang around IRC in #oe, use the dev mailing list or some other way to get in [http://www.openembedded.org/contact contact] with the OE devs. Explain to them why you think you should be given rw access. If your request is granted, [http://www.openembedded.org/wiki/MonotonePhraseBook create your key and send it to the maintainers].<br />
<br />
== 11. How do I add additional packages to a bootstrap-image generated image? ==<br />
<br />
You can add packages to your build by setting the MACHINE_EXTRA_RDEPENDS or DISTRO_EXTRA_RDEPENDS in a conf file. Note, you must rebuild task-base after changing these variables (bitbake task-base -crebuild) as bitbake has no way of knowing task-base has changed. See [http://bec-systems.com/web/content/view/59/9/] for a more detailed explanation. <br />
<br />
== 12. What order are conf files parsed for variable assignment? ==<br />
See oe/conf/bitbake.conf. There should be a section that looks something like:<br />
<br />
<pre><br />
include conf/site.conf<br />
include conf/auto.conf<br />
include conf/local.conf<br />
include conf/build/${BUILD_SYS}.conf<br />
include conf/target/${TARGET_SYS}.conf<br />
include conf/machine/${MACHINE}.conf<br />
include conf/distro/${DISTRO}.conf<br />
include conf/documentation.conf<br />
require conf/sanity.conf<br />
</pre><br />
<br />
A straight "=" assignment in a machine or distro conf file will overwrite a local.conf setting. Therefore, machine and distro conf files should use the "+=" assignment if it is useful for local.conf to be able to append to a variable.<br />
<br />
= Build Errors =<br />
== 1. chown error during do_install process ==<br />
As the OE build process runs a normal using, any install process that changes file ownership or groups must be run using fakeroot. This typically involves the following change in the recipe bb file:<br />
<pre><nowiki><br />
fakeroot do_install () {<br />
oe_runmake "DSTROOT=${D}" install<br />
}<br />
</nowiki></pre><br />
<br />
== 2. Error: autoreconf2.50: unrecognized option --exclude=libtoolize ==<br />
For some reason the base system's autoreconf is being used instead of the OE version (from autoconf-native)<br />
<br />
For me personally this was a problem with my BBPATH having the paths to two branches in it org.openembedded.oz354x and org.openembedded.dev. Removing the one i wasn't trying to build, remove the tmp dir and start bitbake over fixed it.<br />
<br />
== 3. Error: Building libtool-native dies with "configure: error: source directory already configured; run "make distclean" there first" ==<br />
Your build dir path has one or more symlinks in it. Don't do that!<br />
<br />
== 4. Error: run.do_patchcleancmd.4326: line 442: syntax error near unexpected token `'INHIBIT_PACKAGE_STRIP','` ==<br />
known bug -- see: http://bugs.openembedded.org/Ticket/Display.html?id=257 There are several workarounds:<br />
** inherit package in the offending bb files<br />
** set INHERIT += "package_ipk debian" in your distro or local.conf file<br />
<br />
== 5. I updated OE.db and now my builds are failing during the glibc compile, complaining about bad symbol definitions. What's wrong? ==<br />
<br />
As of this writing, the version of glibc in the .dev branch of OE calls for a version of binutils it really shouldn't use. A patch has been applied to some DISTRO .confs which forces the "correct" version of binutils (<2.17) for the moment. But if the DISTRO .conf file you're building with isn't patched, a workaround is to add the following line to your local.conf file:<br />
<br />
PREFERRED_VERSION_binutils-cross = "2.16"<br />
<br />
then reset the glibc build with<br />
<br />
bitbake glibc -c clean<br />
<br />
and start from where you left off.<br />
<br />
== 6. My build dies during the qemu-native section. What gives? ==<br />
If the error is:<br />
| ERROR: QEMU requires SDL or Cocoa for graphical output<br />
| To build QEMU without graphical output configure with --disable-gfx-check <br />
| Note that this will disable all output from the virtual graphics card.<br />
| FATAL: oe_runconf failed<br />
Then install SDL headers (apt-get install libsdl1.2-dev under Ubuntu/Debian).<br />
<br />
Else another workaround: Install qemu from the distribution for your development computer, and include <br />
ASSUME_PROVIDED +="qemu-native"<br />
in your local.conf file.<br />
<br />
== 7. Bitbake tells me to "Please set TARGET_OS directly, or choose a MACHINE or DISTRO that does so.", but my local.conf file already does. ==<br />
<br />
Be sure you are not running bitbake as root. Doing so breaks Bitbake's use of chroot.<br />
<br />
== 8. qemu crashes during generation of binary locales ==<br />
<br />
Set ENABLE_BINARY_LOCALE_GENERATION = "0" in your local.conf. This is probably a x86_64 issue.<br />
<br />
== 9. sanity checker complains "/proc/sys/vm/mmap_min_addr is not 0" on Ubuntu ==<br />
<br />
Ubuntu Hardy Heron has this value set to 65536 by default. <br />
see /etc/sysctl.conf content below<br />
<pre><nowiki><br />
# protect bottom 64k of memory from mmap to prevent NULL-dereference<br />
# attacks against potential future kernel security vulnerabilities.<br />
# (Added in kernel 2.6.23.)<br />
vm.mmap_min_addr = 65536<br />
</nowiki></pre><br />
<br />
Since Wine suffers from the same feature, a temporary and permenant fix <br />
is already known. <br />
See this link (duh!) : http://wiki.winehq.org/PreloaderPageZeroProblem<br />
<br />
Q: Why is this necessary? I'm using debian, and mmap_min_addr is 4096, but I run qemu all the time, and it seems to work fine.<br />
<br />
= Debugging OE Builds =<br />
OE is not perfect. Due to the size, complexity, rapid pace of development, and lack of maintainers, you will often be presented with an opportunity to debug OE builds :). Fortunately, OE is easy to debug once you know a few tricks:<br />
<br />
== 1. Debugging tips ==<br />
* learn to use interactive bitbake (`bitbake -i`)<br />
* The [[BitBake]] `--verbose` option will print package dependencies. This is very useful when trying to determine why a package is being built.<br />
* The [[BitBake]] `-D` option will increase debugging level. Note `-D -D` is also a valid option and can be used to determine what conf files are being used -- look for lines begining with conf.<br />
<br />
== 2. How do I re-build a failing package? ==<br />
There are several options:<br />
* `bitbake -b <path to bb file>`<br />
* `bitbake <package name>`<br />
* start bitbake interactive mode (`bitbake -i`) and then run `build <package name>`<br />
<br />
== 3. How do I clean a package? ==<br />
There are several options:<br />
* `bitbake -b <path to bb file> -c clean`<br />
* `bitbake <package name> -c clean`<br />
* start bitbake interactive mode (`bitbake -i`) and then run `clean <package name>`<br />
You may also put several package names after the command e.g.<br />
* `bitbake -c clean pack1 pack2 ...`<br />
Sometimes you want to clean a particular package version from your build/tmp/work directory. In this case use<br />
* for example `bitbake -c clean gcc-cross-initial-4.1.1`<br />
Note: You have to use the package directory name here from your work directory without the trailing `-rx`. That means there is not an underscore before the package version but a simple dash.<br />
The above is quite useful if you want to clean up a work directory from unwanted versions of the same package.<br />
<br />
The ipk file in the directory deploy/ipk is not deleted when you perform a clean on a certain package. So make sure you manually rebuild the cleaned package in order to get an updated ipk or delete the ipk prior to a build.<br />
<br />
== 4. What tasks are available for a package/recipe? ==<br />
Building an OE package consists of a number of tasks. These tasks can be listed with the OE listtasks task. Each task can be run individually.<br />
<br />
Example:<br />
<br />
<pre><br />
bitbake -b <path to bb file> -c listtasks<br />
NOTE: package matchbox-0.9.1: started<br />
NOTE: package matchbox-0.9.1-r0: task do_listtasks: started<br />
do_listtasks<br />
do_compile<br />
do_stage<br />
do_build<br />
do_mrproper<br />
do_fetch<br />
do_configure<br />
do_clean<br />
do_emit_manifest<br />
do_populate_staging<br />
do_package<br />
do_unpack<br />
do_install<br />
do_showdata<br />
do_patch<br />
NOTE: package matchbox-0.9.1-r0: task do_listtasks: completed<br />
NOTE: package matchbox-0.9.1: completed<br />
Build statistics:<br />
Attempted builds: 1<br />
</pre><br />
<br />
== 5. How do I view the value of OE variables for a package? ==<br />
* Use the [[BitBake]] command. <br />
** `bitbake -e -b ../openembedded/recipes/meta/bootstrap-image.bb`<br />
** `bitbake -e <package name>`<br />
* Use the [[OpenEmbedded]] showdata command. Ex: `bitbake -b ../openembedded/recipes/meta/bootstrap-image.bb -c showdata`<br />
<br />
== 6. How do I unpack ipk files? ==<br />
ipk package files can be unpackaged with the `ar` command. Ex: `ar x <path to ipk file>` You can also inspect the files inside an ipk and get other information with the dpkg command if your distribution has it.</div>MarcinHrwJuszkiewiczhttp://www.openembedded.org/index.php?title=Category:FAQ&diff=3536Category:FAQ2010-11-24T09:40:23Z<p>MarcinHrwJuszkiewicz: Reverted edits by Ejumuvo (Talk) to last revision by Laibsch</p>
<hr />
<div>Howto-type documents as well as common questions and answers.<br />
<br />
[[Category:User]]</div>MarcinHrwJuszkiewiczhttp://www.openembedded.org/index.php?title=BitBake_(dev)&diff=3537BitBake (dev)2010-11-24T09:40:23Z<p>MarcinHrwJuszkiewicz: Reverted edits by Ejumuvo (Talk) to last revision by 83.171.164.148</p>
<hr />
<div>''developer homepage''<br />
<br />
* First , RTFM ;-) : http://bitbake.berlios.de/manual/<br />
* Don't forget mailinglist :<br />
** https://lists.berlios.de/pipermail/bitbake-dev/<br />
** https://lists.berlios.de/pipermail/bitbake-commit/<br />
* Best documentation for source is via python documentation system.<br />
<br />
= Tutorial =<br />
<br />
This tutorial focus bitbake developement, not bbclass or openembedded developement that is documented elsewhere.<br />
<br />
== "Helloworld" using bb library ==<br />
<br />
=== Simplest ===<br />
<br />
<pre><br />
#!/usr/bin/env python<br />
# ex:ts=4:sw=4:sts=4:et<br />
# -*- tab-width: 4; c-basic-offset: 4; indent-tabs-mode: nil -*-<br />
<br />
import bb<br />
<br />
version = bb.__version__<br />
bb.note("Hello from helloworld using lib bb v%s." % ( version ))<br />
</pre><br />
<br />
=== with data module ===<br />
<br />
<pre><br />
#!/usr/bin/env python<br />
# ex:ts=4:sw=4:sts=4:et<br />
# -*- tab-width: 4; c-basic-offset: 4; indent-tabs-mode: nil -*-<br />
<br />
import os , bb<br />
from bb import data<br />
<br />
hello = ("Hello from helloworld using lib bb v%s." % ( bb.__version__ ))<br />
<br />
d = data.init()<br />
data.setVar('HELLO_MSG', hello, d)<br />
<br />
mystring = data.getVar('HELLO_MSG', d, 1)<br />
bb.note(mystring)<br />
</pre><br />
<br />
data module is well documented because it uses doctest.<br />
Enjoy to play with the different methods. <br />
<br />
=== with persist_data module ===<br />
<br />
Now you want persistant data to exchange data between threads/tasks.<br />
This can be done using bb.persist_data module that uses sqlite via pyslite2.<br />
<br />
<pre><br />
#!/usr/bin/env python<br />
# ex:ts=4:sw=4:sts=4:et<br />
# -*- tab-width: 4; c-basic-offset: 4; indent-tabs-mode: nil -*-<br />
<br />
import bb, os, sys<br />
from bb import data, persist_data, fetch<br />
<br />
__version__ = "0.0.1"<br />
<br />
def main():<br />
"""<br />
The main Method<br />
"""<br />
<br />
# persist_data module need debug_level to be set<br />
bb.msg.set_debug_level(0) <br />
<br />
# init a data with PERSISTENT_DIR to set where the data will be saved<br />
d = data.init()<br />
data.setVar('PERSISTENT_DIR', os.getcwd(), d)<br />
<br />
# create persist_data base in bb_persist_data.sqlite3<br />
pd = persist_data.PersistData(d)<br />
<br />
# create a sql table<br />
pd.addDomain("MYBASE")<br />
<br />
# add a data in this table<br />
pd.setValue( "MYBASE", "TOTO", "hello world!")<br />
<br />
# print it<br />
val = pd.getValue ( "MYBASE", "TOTO")<br />
print val<br />
<br />
if __name__ == '__main__':<br />
main()<br />
</pre><br />
<br />
You can edit and watch your base using [http://sqlitebrowser.sourceforge.net sqlitebrowser] for example. Should be useful for debug and test purpose. You can look also at fetch module source that use bb.persist_data.<br />
<br />
[[Category:Dev]]</div>MarcinHrwJuszkiewiczhttp://www.openembedded.org/index.php?title=MotorolaEzx&diff=3535MotorolaEzx2010-11-24T09:40:21Z<p>MarcinHrwJuszkiewicz: Reverted edits by Ejumuvo (Talk) to last revision by Koan</p>
<hr />
<div>The Motorola EZX devices are a family of PXA2xx-based smartphones shipping with a Linux 2.4 kernel. The [http://www.openezx.org OpenEZX] project is delivering a modern Linux 2.6 kernel for these devices. Targets in OE are:<br />
* E680<br />
* A780<br />
* A910<br />
* A1200<br />
* ROKRE2<br />
* ROKRE2<br />
<br />
Motorola EZX support in OE is maintained by [[User:Mickey|Michael 'Mickey' Lauer]] and others from the OpenEZX team.<br />
<br />
[[Category:machine]]</div>MarcinHrwJuszkiewiczhttp://www.openembedded.org/index.php?title=Talk:Getting_started_with_OE-Classic&diff=3534Talk:Getting started with OE-Classic2010-11-24T09:40:18Z<p>MarcinHrwJuszkiewicz: Reverted edits by Ejumuvo (Talk) to last revision by Sledz</p>
<hr />
<div>=Changing distro/machine=<br />
* is it safe to change distro on the same oe tree? or mixed staged packages my produce unpredictible results?<br />
<br />
It is not recommended as results can be disaster. Each distro can define other versions of each of libraries so in the end resulting packages are not what distro wants.<br />
<br />
* on angstrom build guide you can read that changing machine/libs is safe for *Angstrom*, is it safe for other distro too?<br />
<br />
It is safe for any distro.<br />
<br />
=About The building time needed=<br />
* I have several tries on building the very basic targets (bitbake nano/helloworld/task-base), every time it cannot complete in almost a whole night, on a Intel-3.2G-CPU/512M-Memory machine, so who can tell an approximate building time needed? On Day or one week? Thank you.<br />
<br />
It depends on machine speed and amount of memory. On quad core Intel 2.4GHz with 4GB ram I am able to do console-image in 2-3 hours. But that can be also result of ccache being used with quite big storage used for caching. Build time can be longer for first build due to time required to fetch all sources so keep your DL_DIR outside of TMPDIR so next builds will use already fetched sources. You can also enable parallel make and use more BitBake threads to speed up build time ([http://marcin.juszkiewicz.com.pl/2008/04/07/speeding-up-bitbake-builds/ info how to do it ]).<br />
<br />
= Bitbake GIT=<br />
* The addition of the command to clone the bitbake tool will save time. The bitbake project homepage still list only the SVN repository. I have lost time to realize that bitbake repository is now in the openembedded site. Please add this somewere:<br />
<pre><br />
git clone git://git.openembedded.net/bitbake<br />
</pre></div>MarcinHrwJuszkiewiczhttp://www.openembedded.org/index.php?title=How_to_disable_generation_of_locales&diff=3533How to disable generation of locales2010-11-24T09:40:17Z<p>MarcinHrwJuszkiewicz: Reverted edits by Ejumuvo (Talk) to last revision by 83.171.164.148</p>
<hr />
<div>Generating locales and their packages takes a very long time. Quoting [http://cgit.openembedded.net/cgit.cgi/openembedded/tree/conf/local.conf.sample local.conf.sample] on how to skip or limit that step to significantly speed up your builds.<br />
<br />
<pre><br />
<br />
# So far, angstrom.conf sets ENABLE_BINARY_LOCALE_GENERATION<br />
# to generate binary locale packages at build time using qemu-native and<br />
# thereby guarantee i18n support on all devices. If your build breaks on <br />
# qemu-native consider disabling ENABLE_BINARY_LOCALE_GENERATION (note that<br />
# this breaks i18n on devices with less than 128MB RAM) or installing<br />
# a working third-party qemu (e.g. provided by your distribution) and<br />
# adding qemu-native to ASSUME_PROVIDED. Caveat emptor, since third-party<br />
# qemus lack patches needed to work with various OE targets.<br />
# ENABLE_BINARY_LOCALE_GENERATION = "0"<br />
# ASSUME_PROVIDED += "qemu-native"<br />
<br />
# If ENABLE_BINARY_LOCALE_GENERATION is set to "1", you can limit locales<br />
# generated to the list provided by GLIBC_GENERATE_LOCALES. This is huge<br />
# time-savior for developmental builds. Format: list of locale.encoding pairs<br />
# with spaces as separators.<br />
# GLIBC_GENERATE_LOCALES = "en_US.UTF-8 en_GB.UTF-8 de_DE.UTF-8"<br />
<br />
</pre><br />
<br />
[[Category:FAQ]]</div>MarcinHrwJuszkiewiczhttp://www.openembedded.org/index.php?title=BitBake_(user)&diff=3532BitBake (user)2010-11-24T09:40:16Z<p>MarcinHrwJuszkiewicz: Reverted edits by Ejumuvo (Talk) to last revision by Laibsch</p>
<hr />
<div>= Introduction =<br />
<br />
'''BitBake''' is, at its simplest, a tool for executing [http://en.wikipedia.org/wiki/Task_%28computing%29 tasks] and managing [http://en.wikipedia.org/wiki/Metadata metadata]. As such, its similarities to [http://en.wikipedia.org/wiki/GNU_make GNU make] and other build tools are readily apparent. It was inspired by [http://en.wikipedia.org/wiki/Portage_%28software%29 Portage], the package management system used by the Gentoo Linux distribution. <br />
<br />
BitBake is the basis of the OpenEmbedded project, which is being used to build and maintain a number of embedded Linux distributions, including OpenZaurus and Familiar.<br />
<br />
= Links =<br />
<br />
* Homepage with manual: http://bitbake.berlios.de/ <br />
* Project page at Berlios: http://developer.berlios.de/projects/bitbake/<br />
* <strike>Subversion repository: http://svn.berlios.de/svnroot/repos/bitbake/</strike><br />
* GIT repository: http://cgit.openembedded.org/cgit.cgi/bitbake/<br />
<br />
= Version information =<br />
<br />
OpenEmbedded require BitBake 1.8.18 or newer. Some features can require GIT HEAD. [http://oss.leggewie.org/oe/deb/ Laibsch provides a Debian package] for use in Ubuntu and Debian. <br />
<br />
BitBake "trunk" contain experimental code - use at your own risk.<br />
<br />
[[Category:User]]</div>MarcinHrwJuszkiewiczhttp://www.openembedded.org/index.php?title=Category:Debug_build&diff=3530Category:Debug build2010-11-24T09:40:14Z<p>MarcinHrwJuszkiewicz: Reverted edits by Ejumuvo (Talk) to last revision by Laibsch</p>
<hr />
<div>OE is not perfect. Due to the size, complexity, rapid pace of development, and lack of maintainers, you will often be presented with an opportunity to debug OE builds :). Fortunately, OE is easy to debug once you know a few tricks: <br />
<br />
[[Category:FAQ]]</div>MarcinHrwJuszkiewiczhttp://www.openembedded.org/index.php?title=User:BernhardKaindl&diff=3531User:BernhardKaindl2010-11-24T09:40:14Z<p>MarcinHrwJuszkiewicz: Reverted edits by Ejumuvo (Talk) to last revision by BernhardKaindl</p>
<hr />
<div>* Using OpenEmbedded since Summer 2009, using OpenEmbedded full-time since November 2009<br />
* full-time openSuSE package maintainer from 1999 to 2008<br />
<br />
= Contact =<br />
* Using MediaWiki's [[Special:Emailuser/BernhardKaindl|E-mail this user]] function from the middle of the toolbox on the left MediaWiki sidebar<br />
* E-mail: >firstname<.>lastname<@gmx.at</div>MarcinHrwJuszkiewiczhttp://www.openembedded.org/index.php?title=Category:Distro&diff=3529Category:Distro2010-11-24T09:40:12Z<p>MarcinHrwJuszkiewicz: Reverted edits by Ejumuvo (Talk) to last revision by Laibsch</p>
<hr />
<div>Various distributions included in OE or based on OE.</div>MarcinHrwJuszkiewiczhttp://www.openembedded.org/index.php?title=Category:Machine&diff=3528Category:Machine2010-11-24T09:40:11Z<p>MarcinHrwJuszkiewicz: Reverted edits by Ejumuvo (Talk) to last revision by Laibsch</p>
<hr />
<div>This page contains information about devices (machines) that are supported in OE.<br />
* Machine Conf files are found in the [http://cgit.openembedded.net/cgit.cgi?url=openembedded/tree/conf/machine conf/machine directory] in the OE metadata.</div>MarcinHrwJuszkiewiczhttp://www.openembedded.org/index.php?title=Talk:Generic_distro_problems&diff=3527Talk:Generic distro problems2010-11-24T09:40:10Z<p>MarcinHrwJuszkiewicz: Reverted edits by Ejumuvo (Talk) to last revision by Laibsch</p>
<hr />
<div>no nonsense talk, please.<br />
<br />
You need to be signed in with your registered account to edit this page.</div>MarcinHrwJuszkiewiczhttp://www.openembedded.org/index.php?title=GA2010&diff=3526GA20102010-11-24T09:40:04Z<p>MarcinHrwJuszkiewicz: Reverted edits by Ejumuvo (Talk) to last revision by Crofton</p>
<hr />
<div>=General Assembly 2010 Agenda=<br />
<br />
==Agenda==<br />
<br />
* Open of GA by Chairperson<br />
* Apologies<br />
* Review of last GA Minutes<br />
* Vote for new members<br />
* Report from Treasurer<br />
* Report from TSC<br />
* Online Voting System discussion/redraft/vote.<br />
* Any Other Business<br />
* Close by Chairperson</div>MarcinHrwJuszkiewiczhttp://www.openembedded.org/index.php?title=Category:Candidates_for_speedy_deletion&diff=3525Category:Candidates for speedy deletion2010-11-24T09:40:02Z<p>MarcinHrwJuszkiewicz: Reverted edits by Ejumuvo (Talk) to last revision by Glenn</p>
<hr />
<div>[[Category:Wiki Editing]]</div>MarcinHrwJuszkiewiczhttp://www.openembedded.org/index.php?title=BitBake&diff=3524BitBake2010-11-24T09:40:00Z<p>MarcinHrwJuszkiewicz: Reverted edits by Ejumuvo (Talk) to last revision by Glenn</p>
<hr />
<div>'''BitBake''':<br />
*[[BitBake (user)]] - for users.<br />
*[[BitBake (dev)]] - for developers.<br />
<br />
Wikipedia:<br />
*http://en.wikipedia.org/wiki/BitBake</div>MarcinHrwJuszkiewiczhttp://www.openembedded.org/index.php?title=User:Khem&diff=3523User:Khem2010-11-24T09:39:59Z<p>MarcinHrwJuszkiewicz: Reverted edits by Ejumuvo (Talk) to last revision by 99.57.141.118</p>
<hr />
<div>Hello peeps !<br />
<br />
<brag> Embedded Linux and toolchain expert <end brag><br />
<br />
Welcome to my den!! Check my rants on http://sakrah.dontexist.org<br />
poke me for toolchain related questions or any questions on OE in general.<br />
<br />
These days I am helping in [[Testing]] OE<br />
<br />
and general house keeping</div>MarcinHrwJuszkiewiczhttp://www.openembedded.org/index.php?title=User_talk:CharlesXu&diff=3522User talk:CharlesXu2010-11-24T09:39:58Z<p>MarcinHrwJuszkiewicz: Reverted edits by Ejumuvo (Talk) to last revision by CharlesXu</p>
<hr />
<div>Hi, Everyone<br />
<br />
I just create a wiki for TiN Device based on OMAP3.<br />
Nice to say hello to the world.<br />
<br />
Yours<br />
Charles</div>MarcinHrwJuszkiewiczhttp://www.openembedded.org/index.php?title=User:Mickey&diff=3521User:Mickey2010-11-24T09:39:57Z<p>MarcinHrwJuszkiewicz: Reverted edits by Ejumuvo (Talk) to last revision by Mickey</p>
<hr />
<div>* Free Software Enthusiast<br />
* Middleware Guy<br />
* OpenEmbedded Founder<br />
* Former Openmoko Architect<br />
* [http://freesmartphone.org freesmartphone.org] Architect<br />
* ...<br />
<br />
Want to know more? <br />
<br />
See http://www.vanille-media.de</div>MarcinHrwJuszkiewiczhttp://www.openembedded.org/index.php?title=Category:Software_Components&diff=3520Category:Software Components2010-11-24T09:39:37Z<p>MarcinHrwJuszkiewicz: Reverted edits by Ejumuvo (Talk) to last revision by Laibsch</p>
<hr />
<div>Information about major software components in OE such as Java, Python, Qt, etc.</div>MarcinHrwJuszkiewiczhttp://www.openembedded.org/index.php?title=Category:Dev&diff=3519Category:Dev2010-11-24T09:39:35Z<p>MarcinHrwJuszkiewicz: Reverted edits by Ejumuvo (Talk) to last revision by Laibsch</p>
<hr />
<div>Pages for OE developers with commit rights.</div>MarcinHrwJuszkiewiczhttp://www.openembedded.org/index.php?title=DNS_Configuration&diff=3518DNS Configuration2010-11-24T09:39:33Z<p>MarcinHrwJuszkiewicz: Reverted edits by Ejumuvo (Talk) to last revision by Glenn</p>
<hr />
<div>DNS<br />
<br />
{|<br />
|openembedded.org||A||85.214.40.226<br />
|-<br />
|bugs.openembedded.org||A||80.81.242.146<br />
|-<br />
|cgit.openembedded.org||A||140.211.169.165<br />
|-<br />
|docs.openembedded.org||A||80.81.242.146<br />
|-<br />
|git.openembedded.org||A||140.211.169.165<br />
|-<br />
|gitweb.openembedded.org||A||140.211.169.165<br />
|-<br />
|lists.openembedded.org||CNAME||openembedded.org<br />
|-<br />
|new.openembedded.org||A||80.81.242.146<br />
|-<br />
|patchwork.openembedded.org||A||80.81.242.146<br />
|-<br />
|tinderbox.openembedded.org||CNAME||tinderbox.openembedded.net<br />
|-<br />
|wiki.openembedded.org||A||80.81.242.146<br />
|-<br />
|www.openembedded.org||A||80.81.242.146<br />
|}<br />
<br />
[[Category:Community]]</div>MarcinHrwJuszkiewiczhttp://www.openembedded.org/index.php?title=Talk:OEandYourDistro&diff=3516Talk:OEandYourDistro2010-11-24T09:39:30Z<p>MarcinHrwJuszkiewicz: Reverted edits by Ejumuvo (Talk) to last revision by 98.212.232.129</p>
<hr />
<div>maybe as a last paragraph in the install page it is wise to include some checks how to test that the install is functioning.<br />
for me as a newbie, I followed the steps, but I have no idea what I have done to my system now...<br />
<br />
<br />
== Complementary packages (for debian) ==<br />
<br />
What exactly are "complementary packages" ? It is not really clear what they are needed for --[[User:Zimbatm|Zimbatm]] 12:29, 13 February 2009 (UTC)<br />
<br />
: as evidenced by the structure of the page, complementary is the opposite of mandatory packages. I'll rename the section to supplementary packages which may make the distinction more clear. --[[User:Laibsch|Laibsch]] 04:51, 14 February 2009 (UTC)<br />
<br />
== further mandatory packages ==<br />
<br />
it may be that [http://tinyurl.com/o8uydk further packages are necessary]: libmpfr-dev and gfortran<br />
<br />
== bitbake complains about chrpath ==<br />
<br />
It is necessary to install chrpath for bitbake version 1.8.18 !<br />
<br />
== Oct 2010 Tested on out of the box x86 "debian lenny" & "ubuntu karmic" ==<br />
<br />
both lenny and karmic say package "apr" not found <br />
<br />
lenny has python problems that keep bitbake from doing anything except complaining - giving up on lenny for now<br />
<br />
karmic has gotten past the part that lenny choked on and is compiling - no problems yet</div>MarcinHrwJuszkiewiczhttp://www.openembedded.org/index.php?title=OpenmokoNeo&diff=3513OpenmokoNeo2010-11-24T09:39:08Z<p>MarcinHrwJuszkiewicz: Reverted edits by Ejumuvo (Talk) to last revision by Glenn</p>
<hr />
<div>The [http://www.openmoko.org Openmoko] Neo devices are a family of Samsung S3C24xx-based smartphones. The Openmoko devices are currently the only smartphones on the market shipping completely with free software. Targets is OE are:<br />
<br />
* OM-GTA01 ([http://wiki.openmoko.org/wiki/GTA01:Neo_1973 Openmoko Neo 1973])<br />
* OM-GTA02 ([http://wiki.openmoko.org/wiki/Neo_FreeRunner Openmoko Neo FreeRunner])<br />
<br />
Openmoko devices support in OE is maintained by [[User:Mickey|Michael 'Mickey' Lauer]] and others from Openmoko team.<br />
<br />
[[Category:machine]]</div>MarcinHrwJuszkiewiczhttp://www.openembedded.org/index.php?title=Donations&diff=2994Donations2010-11-03T10:08:04Z<p>MarcinHrwJuszkiewicz: links should have proper names - think of a11y</p>
<hr />
<div>Here the OpenEmbedded project lists one-time donations in form of hardware or money. We have separate page for [[Become_Sponsor | ongoing sponsorship]].<br />
<br />
= Money =<br />
<br />
2009: 1500€ [http://www.eukrea.com/ Eukréa Electromatique] ARM based System on Module, Hardware Engineering, Embedded Linux Development and Training.<br />
<br />
2010: 3000$ [http://www.ti.com/ Texas Instruments]<br />
<br />
= Infrastructure =<br />
<br />
Details about the services can be found on our [[Infrastructure | infrastructure]] page.<br />
<br />
* Hosting for melo by [http://osuosl.org/ OSU Open Source Lab] / [http://www.nslu2-linux.org/ nslu2-linux.org]<br />
* Hosting for amethyst by [http://www.vanille-media.de Michael Lauer] and [http://www.hmw-consulting.com/ Harald Welte]<br />
* Hosting for mailling lists by [http://www.linuxtogo.org LinuxToGo]<br />
* CPU for the melo server by [http://bec-systems.com/ BEC Systems]<br />
* 3 Harddisks for the melo server by [http://www.eukrea.com/ Eukréa Electromatique]<br />
<br />
= Misc =<br />
<br />
New logo design by [http://www.buglabs.com BugLabs, Inc.]</div>MarcinHrwJuszkiewiczhttp://www.openembedded.org/index.php?title=Donations&diff=2993Donations2010-11-03T10:03:16Z<p>MarcinHrwJuszkiewicz: typo</p>
<hr />
<div>Here the OpenEmbedded project lists one-time donations in form of hardware or money. For ongoing sponsorship we have a separate [[Become_Sponsor |page]].<br />
<br />
= Money =<br />
<br />
2009: 1500€ [http://www.eukrea.com/ Eukréa Electromatique] ARM based System on Module, Hardware Engineering, Embedded Linux Development and Training.<br />
<br />
2010: 3000$ [http://www.ti.com/ Texas Instruments]<br />
<br />
= Infrastructure =<br />
<br />
Details about the services can be found on our [[Infrastructure | infrastructure]] page.<br />
<br />
* Hosting for melo by [http://osuosl.org/ OSU Open Source Lab] / [http://www.nslu2-linux.org/ nslu2-linux.org]<br />
* Hosting for amethyst by [http://www.vanille-media.de Michael Lauer] and [http://www.hmw-consulting.com/ Harald Welte]<br />
* Hosting for mailling lists by [http://www.linuxtogo.org LinuxToGo]<br />
* CPU for the melo server by [http://bec-systems.com/ BEC Systems]<br />
* 3 Harddisks for the melo server by [http://www.eukrea.com/ Eukréa Electromatique]<br />
<br />
= Misc =<br />
<br />
New logo design by [http://www.buglabs.com BugLabs, Inc.]</div>MarcinHrwJuszkiewiczhttp://www.openembedded.org/index.php?title=Fosdem_2010&diff=2141Fosdem 20102010-01-17T19:23:22Z<p>MarcinHrwJuszkiewicz: </p>
<hr />
<div>Attending FOSDEM 2010? Add your name to this page so that other developers can look out for you!<br />
<br />
* Phil Blundell<br />
* Henning Heinold<br />
* Marco Cavallini<br />
* Frans Meulenbroeks (eFfeM)<br />
* Ulf Samuelsson<br />
* Marcin Juszkiewicz</div>MarcinHrwJuszkiewiczhttp://www.openembedded.org/index.php?title=ToolingUseCases&diff=1907ToolingUseCases2009-11-13T07:00:25Z<p>MarcinHrwJuszkiewicz: typo</p>
<hr />
<div>= Overview =<br />
<br />
This page defines primary user-roles in using OpenEmbedded. The material resulted from some discussions at OEDEM that were truncated due to time restrictions.<br />
<br />
= Goals =<br />
<br />
The goal of identifying user-roles is to be able to categorize different tooling scenarios, and what types of users will be interested in specific features. Tools designed for role type may not be appropriate for other roles. For example, a GUI for recipe editing may not be helpful for an application developer that's looking to remote debug their application on a target. On the other hand, a simple press-button build GUI may not be interesting for a seasoned OE hacker.<br />
<br />
= Role Types =<br />
<br />
== Application Developer ==<br />
<br />
The application developer's main concern is developing and testing any given application on a target system. This person does not care nor want to learn much about the internal details of the build system or package metadata. The best possible case is that these systems are transparent and the developer is able to easily build and deploy applications to the target device.<br />
<br />
=== Primary Tooling Requirements ===<br />
<br />
* Build Application for Target<br />
* Debug Application on Target<br />
* Generate build system artifacts for Application (recipes)<br />
<br />
== Distro Developer ==<br />
<br />
Distro developer's concern is to compose packages and configurations into a working system. The distro developer has deep knowledge of packages available in Linux, and how sets of packages work well together. Additionally the distro developer is not afraid to work deeply within the build system to make it better, and to produce better, more maintainable package metadata and target systems.<br />
<br />
=== Primary Tooling Requirements ===<br />
<br />
* Build system image <br />
* Create/edit distro definitions<br />
* Debug build problems<br />
* Visualize package dependencies<br />
<br />
== Package Developer ==<br />
<br />
The package developer is often a mix of the previous two role types. Often they have some knowledge of the build system and applications and build tools used to create those applications. They typically act as a bridge between pure application developers and the resulting target system that's produced. Package developers write recipes, debug applications, and debug build problems.<br />
<br />
=== Primary Tooling Requirements ===<br />
<br />
* Create and edit package metadata<br />
* Easily integrate package metadata into build system<br />
* Debug build issues<br />
* Visualize Package Dependencies<br />
<br />
== Target System User ==<br />
<br />
This role type typically is not exposed to package metadata, cross compilers, or build systems. They are system users, and as such, at times want to:<br />
<br />
* Update system<br />
* Install packages<br />
* Configure package metadata<br />
<br />
=== Primary Tooling Requirements ===<br />
<br />
* install binary package on target<br />
* find new packages and package updates for target<br />
* resolve package dependencies<br />
<br />
[[Category:DevTalk]]</div>MarcinHrwJuszkiewiczhttp://www.openembedded.org/index.php?title=Getting_started_with_OE-Classic&diff=1890Getting started with OE-Classic2009-11-10T16:46:50Z<p>MarcinHrwJuszkiewicz: first we do release, then bump OE requirements so last version works</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 packages===<br />
<br />
There is a BitBake package available for more and more distros - see [[OEandYourDistro]].<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>MarcinHrwJuszkiewiczhttp://www.openembedded.org/index.php?title=Getting_started_with_OE-Classic&diff=1888Getting started with OE-Classic2009-11-10T16:30:23Z<p>MarcinHrwJuszkiewicz: BitBake versions cleanup</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.16.tar.gz<br />
<br />
===Using packages===<br />
<br />
There is a BitBake package available for more and more distros - see [[OEandYourDistro]].<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>MarcinHrwJuszkiewiczhttp://www.openembedded.org/index.php?title=Buglabs-BUG&diff=1865Buglabs-BUG2009-11-07T12:40:10Z<p>MarcinHrwJuszkiewicz: /* Hardware */</p>
<hr />
<div>= Status =<br />
<br />
The [http://buglabs.net/bug BUG] by default runs a customized version of Poky Linux. <br />
<br />
Development branch of OpenEmbedded provides basic support for device. It is possible to run BugLabs software by using "hrw/oe-stable-2009" branch available in BugLabs svn server.<br />
<br />
= Official maintainer =<br />
<br />
[[User:MarcinHrwJuszkiewicz| Marcin Juszkiewicz]]<br />
<br />
= Hardware =<br />
<br />
* CPU: i.MX31<br />
* RAM: 128MB<br />
* Flash: 32MB (used only for bootloader)<br />
* Storage: microSD card (2GB one provided with device)<br />
* Screen: built-in monochrome status display + upto 2 QVGA screens<br />
* Connectivity: <br />
** built-in WiFi (Marvell 8686 SDIO) in r1.3 version of device<br />
** built-in Bluetooth in r1.3 version of device<br />
** external module with Marvell 8686 SPI Wifi ++ BlueTooth<br />
* USB host<br />
** On-The-Go connector in device<br />
** USB Host port in VonHippel module<br />
* Expansion modules<br />
** LCD screen with touchscreen (QVGA resolution)<br />
** motion detector <br />
** GPS<br />
** BugBee<br />
** VonHippel (USB Host, GPIO, SPI, I2C, I2S, ADC, DAC, serial lines)<br />
** Camera<br />
** Audio<br />
<br />
<br />
<br />
<br />
[[Category:machine]]</div>MarcinHrwJuszkiewicz