http://www.openembedded.org/api.php?action=feedcontributions&user=Woglinde&feedformat=atomOpenembedded.org - User contributions [en]2024-03-19T02:13:28ZUser contributionsMediaWiki 1.29.0http://www.openembedded.org/index.php?title=Organization&diff=7459Organization2014-10-14T12:01:14Z<p>Woglinde: </p>
<hr />
<div>The current organization for OE is a German e.V. legal entity (similar to KDE: http://ev.kde.org/) and is for the purpose of managing finances, voting, and membership.<br />
<br />
An 'e.V.' for 'eingetragener Verein', in the German law, translates to a voluntary organization; a group of individuals who voluntarily enter into an agreement to form a body (or organization) to accomplish a purpose. The organization has members.<br />
<br />
The OpenEmbedded e.V. statues are located here: http://docs.openembedded.org/organization/2008-11-22_statutes-de.pdf<br />
<br />
A bablefish translation is here -- could German speaking folks please clean this up: [[OpenEmbedded eV Statutes | OpenEmbedded e.V. Statutes]]<br />
<br />
During FOSDEM 2008 in Brussels, Belgium, a group of founding members physically gathered to get the paperwork going.<br />
<br />
= The current board of directors =<br />
<br />
* ''Philip Balister''<br />
* Treasurer ''Leon Woestenberg ''<br />
* ''Denys Dmytriyenko''<br />
* ''Sean Hudson''<br />
<br />
= Current Members =<br />
(please keep in alphabetical order)<br />
<br />
# Alessandro Gardich<br />
# Anders Darander <br />
# Andrea Adami<br />
# Andreas Oberritter<br />
# Andrei Gherzan<br />
# Chris Larson<br />
# Cliff Brake<br />
# Daniel Willmann<br />
# Dave Stewart<br />
# Denys Dmytriyenko<br />
# Dirk Hohndel<br />
# Dirk Opfer<br />
# Dmitry EreminSolenikov<br />
# Eric Bénard<br />
# Esben Haabendal<br />
# Florian Boor<br />
# Frans Meulenbroeks<br />
# Graeme Gregory<br />
# Graham Gower<br />
# Henning Heinold<br />
# Holger Freyther<br />
# Jan Lübbe<br />
# Jason Kridner<br />
# Jeff Osier-Mixon <br />
# John Willis<br />
# Joshua Lock<br />
# Ken Gilmer<br />
# Khem Raj<br />
# Koen Kooi<br />
# Leon Woestenberg<br />
# Liam Girdwood<br />
# Marcin Juszkiewicz<br />
# Marco Cavallini<br />
# Mark Brown<br />
# Mark Hatle<br />
# Martin Jansa<br />
# Michael Lauer<br />
# Michael Smith<br />
# Otavio Salvador<br />
# Paul Eggleton<br />
# Philip Balister<br />
# Philip Blundell<br />
# Phillip Zabel<br />
# Richard Purdie<br />
# Robert Schuster<br />
# Roman I Khimov<br />
# Saul Wold<br />
# Scott Garman<br />
# Sean Hudson<br />
# Simon Busch<br />
# Stefan Schmidt<br />
# Steve Sakoman<br />
# Tom King<br />
# Tom Rini <br />
# Yu Ke <br />
# Yury Bushmelev<br />
<br />
= TSC =<br />
The e.V. installed the [[TSC]] to make technical steering of the project easier.<br />
<br />
= OE Developers =<br />
Openembedded Developers are people who have submitted code into any of the OpenEmbedded repositories. Due to the nature of OE, there are many developers, and also many different components. A good place to start is the list of git repositories [http://git.openembedded.org]. See [[OpenEmbedded Developers]] for a list of current developers.<br />
<br />
= Todo =<br />
* process for adding new members<br />
* process for voting<br />
* responsibility of the board<br />
* conflict resolution<br />
<br />
= Pointers for Board Members =<br />
* [[Checklist for the General Assembly]]<br />
<br />
= Online Voting Policy =<br />
* [[Online Voting Policy]]<br />
<br />
= Faq =<br />
; Are contributions tax deductible?<br /><br />
: Yes they are. <br />
; Should I become member of the OE e.V.?<br />
: If you are contributing to OE frequently and/or you are interested in getting involved in administrative or organisational tasks it might be a good idea to join OE e.V.<br />
; How do I become member of the OE e.V.?<br />
: Let an existing member introduce you by sending a short introduction to the 'ev' [http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-members mailinglist]. If you don't know one get in touch with us on the development mailinglist or IRC first. The e.V. is open for anyone to join and its not meant to be an exclusive club of a few developers. <br />
; Is there a membership fee?<br />
: Whist an e.V. can define a membership fee, the project has not chosen to set one.<br />
<br />
= General Assemblies =<br />
; * [[Prague, 2011]]<br />
; * [[Barcelona, 2012]]<br />
; * [[Edinburgh, 2013]]<br />
; * [[Dusseldorf, 2014]]<br />
<br />
[[Category:Verein]]</div>Woglindehttp://www.openembedded.org/index.php?title=Organization&diff=7457Organization2014-10-14T11:59:55Z<p>Woglinde: </p>
<hr />
<div>The current organization for OE is a German e.V. legal entity (similar to KDE: http://ev.kde.org/) and is for the purpose of managing finances, voting, and membership.<br />
<br />
An 'e.V.' for 'eingetragener Verein', in the German law, translates to a voluntary organization; a group of individuals who voluntarily enter into an agreement to form a body (or organization) to accomplish a purpose. The organization has members.<br />
<br />
The OpenEmbedded e.V. statues are located here: http://docs.openembedded.org/organization/2008-11-22_statutes-de.pdf<br />
<br />
A bablefish translation is here -- could German speaking folks please clean this up: [[OpenEmbedded eV Statutes]]<br />
<br />
During FOSDEM 2008 in Brussels, Belgium, a group of founding members physically gathered to get the paperwork going.<br />
<br />
= The current board of directors =<br />
<br />
* ''Philip Balister''<br />
* Treasurer ''Leon Woestenberg ''<br />
* ''Denys Dmytriyenko''<br />
* ''Sean Hudson''<br />
<br />
= Current Members =<br />
(please keep in alphabetical order)<br />
<br />
# Alessandro Gardich<br />
# Anders Darander <br />
# Andrea Adami<br />
# Andreas Oberritter<br />
# Andrei Gherzan<br />
# Chris Larson<br />
# Cliff Brake<br />
# Daniel Willmann<br />
# Dave Stewart<br />
# Denys Dmytriyenko<br />
# Dirk Hohndel<br />
# Dirk Opfer<br />
# Dmitry EreminSolenikov<br />
# Eric Bénard<br />
# Esben Haabendal<br />
# Florian Boor<br />
# Frans Meulenbroeks<br />
# Graeme Gregory<br />
# Graham Gower<br />
# Henning Heinold<br />
# Holger Freyther<br />
# Jan Lübbe<br />
# Jason Kridner<br />
# Jeff Osier-Mixon <br />
# John Willis<br />
# Joshua Lock<br />
# Ken Gilmer<br />
# Khem Raj<br />
# Koen Kooi<br />
# Leon Woestenberg<br />
# Liam Girdwood<br />
# Marcin Juszkiewicz<br />
# Marco Cavallini<br />
# Mark Brown<br />
# Mark Hatle<br />
# Martin Jansa<br />
# Michael Lauer<br />
# Michael Smith<br />
# Otavio Salvador<br />
# Paul Eggleton<br />
# Philip Balister<br />
# Philip Blundell<br />
# Phillip Zabel<br />
# Richard Purdie<br />
# Robert Schuster<br />
# Roman I Khimov<br />
# Saul Wold<br />
# Scott Garman<br />
# Sean Hudson<br />
# Simon Busch<br />
# Stefan Schmidt<br />
# Steve Sakoman<br />
# Tom King<br />
# Tom Rini <br />
# Yu Ke <br />
# Yury Bushmelev<br />
<br />
= TSC =<br />
The e.V. installed the [[TSC]] to make technical steering of the project easier.<br />
<br />
= OE Developers =<br />
Openembedded Developers are people who have submitted code into any of the OpenEmbedded repositories. Due to the nature of OE, there are many developers, and also many different components. A good place to start is the list of git repositories [http://git.openembedded.org]. See [[OpenEmbedded Developers]] for a list of current developers.<br />
<br />
= Todo =<br />
* process for adding new members<br />
* process for voting<br />
* responsibility of the board<br />
* conflict resolution<br />
<br />
= Pointers for Board Members =<br />
* [[Checklist for the General Assembly]]<br />
<br />
= Online Voting Policy =<br />
* [[Online Voting Policy]]<br />
<br />
= Faq =<br />
; Are contributions tax deductible?<br /><br />
: Yes they are. <br />
; Should I become member of the OE e.V.?<br />
: If you are contributing to OE frequently and/or you are interested in getting involved in administrative or organisational tasks it might be a good idea to join OE e.V.<br />
; How do I become member of the OE e.V.?<br />
: Let an existing member introduce you by sending a short introduction to the 'ev' [http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-members mailinglist]. If you don't know one get in touch with us on the development mailinglist or IRC first. The e.V. is open for anyone to join and its not meant to be an exclusive club of a few developers. <br />
; Is there a membership fee?<br />
: Whist an e.V. can define a membership fee, the project has not chosen to set one.<br />
<br />
= General Assemblies =<br />
; * [[Prague, 2011]]<br />
; * [[Barcelona, 2012]]<br />
; * [[Edinburgh, 2013]]<br />
; * [[Dusseldorf, 2014]]<br />
<br />
[[Category:Verein]]</div>Woglindehttp://www.openembedded.org/index.php?title=Organization&diff=7455Organization2014-10-14T11:58:41Z<p>Woglinde: /* OE Developers */</p>
<hr />
<div>The current organization for OE is a German eV legal entity (similar to KDE: http://ev.kde.org/) and is for the purpose of managing finances, voting, and membership.<br />
<br />
An 'eV' for 'eingetragener Verein', in the German law, translates to a voluntary organization; a group of individuals who voluntarily enter into an agreement to form a body (or organization) to accomplish a purpose. The organization has members.<br />
<br />
The OpenEmbedded eV statues are located here: http://docs.openembedded.org/organization/2008-11-22_statutes-de.pdf<br />
<br />
A bablefish translation is here -- could German speaking folks please clean this up: [[OpenEmbedded eV Statutes]]<br />
<br />
During FOSDEM 2008 in Brussels, Belgium, a group of founding members physically gathered to get the paperwork going.<br />
<br />
= The current board of directors =<br />
<br />
* ''Philip Balister''<br />
* Treasurer ''Leon Woestenberg ''<br />
* ''Denys Dmytriyenko''<br />
* ''Sean Hudson''<br />
<br />
= Current Members =<br />
(please keep in alphabetical order)<br />
<br />
# Alessandro Gardich<br />
# Anders Darander <br />
# Andrea Adami<br />
# Andreas Oberritter<br />
# Andrei Gherzan<br />
# Chris Larson<br />
# Cliff Brake<br />
# Daniel Willmann<br />
# Dave Stewart<br />
# Denys Dmytriyenko<br />
# Dirk Hohndel<br />
# Dirk Opfer<br />
# Dmitry EreminSolenikov<br />
# Eric Bénard<br />
# Esben Haabendal<br />
# Florian Boor<br />
# Frans Meulenbroeks<br />
# Graeme Gregory<br />
# Graham Gower<br />
# Henning Heinold<br />
# Holger Freyther<br />
# Jan Lübbe<br />
# Jason Kridner<br />
# Jeff Osier-Mixon <br />
# John Willis<br />
# Joshua Lock<br />
# Ken Gilmer<br />
# Khem Raj<br />
# Koen Kooi<br />
# Leon Woestenberg<br />
# Liam Girdwood<br />
# Marcin Juszkiewicz<br />
# Marco Cavallini<br />
# Mark Brown<br />
# Mark Hatle<br />
# Martin Jansa<br />
# Michael Lauer<br />
# Michael Smith<br />
# Otavio Salvador<br />
# Paul Eggleton<br />
# Philip Balister<br />
# Philip Blundell<br />
# Phillip Zabel<br />
# Richard Purdie<br />
# Robert Schuster<br />
# Roman I Khimov<br />
# Saul Wold<br />
# Scott Garman<br />
# Sean Hudson<br />
# Simon Busch<br />
# Stefan Schmidt<br />
# Steve Sakoman<br />
# Tom King<br />
# Tom Rini <br />
# Yu Ke <br />
# Yury Bushmelev<br />
<br />
= TSC =<br />
The e.V. installed the [[TSC]] to make technical steering of the project easier.<br />
<br />
= OE Developers =<br />
Openembedded Developers are people who have submitted code into any of the OpenEmbedded repositories. Due to the nature of OE, there are many developers, and also many different components. A good place to start is the list of git repositories [http://git.openembedded.org]. See [[OpenEmbedded Developers]] for a list of current developers.<br />
<br />
= Todo =<br />
* process for adding new members<br />
* process for voting<br />
* responsibility of the board<br />
* conflict resolution<br />
<br />
= Pointers for Board Members =<br />
* [[Checklist for the General Assembly]]<br />
<br />
= Online Voting Policy =<br />
* [[Online Voting Policy]]<br />
<br />
= Faq =<br />
; Are contributions tax deductible?<br /><br />
: Yes they are. <br />
; Should I become member of the OE e.V.?<br />
: If you are contributing to OE frequently and/or you are interested in getting involved in administrative or organisational tasks it might be a good idea to join OE e.V.<br />
; How do I become member of the OE e.V.?<br />
: Let an existing member introduce you by sending a short introduction to the 'ev' [http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-members mailinglist]. If you don't know one get in touch with us on the development mailinglist or IRC first. The e.V. is open for anyone to join and its not meant to be an exclusive club of a few developers. <br />
; Is there a membership fee?<br />
: Whist an e.V. can define a membership fee, the project has not chosen to set one.<br />
<br />
= General Assemblies =<br />
; * [[Prague, 2011]]<br />
; * [[Barcelona, 2012]]<br />
; * [[Edinburgh, 2013]]<br />
; * [[Dusseldorf, 2014]]<br />
<br />
[[Category:Verein]]</div>Woglindehttp://www.openembedded.org/index.php?title=Checklist_for_the_General_Assembly&diff=7453Checklist for the General Assembly2014-10-14T11:51:51Z<p>Woglinde: /* Paper work */</p>
<hr />
<div>== Checklist to organize the General Assembly ==<br />
<br />
=== Preparing the General Assembly ===<br />
# Pick date at least ~7 weeks from now<br />
# Pick a venue for the conference<br />
# Take the last invitation and change the date, location and the year of the assembly<br />
# Point people to the proxy form. [[File:Proxy instructions-oe.pdf]] (Source - [[File:Proxy instructions-oe.odt]])<br />
# Create a WIKI page for the Agenda (TODO: Come up with a namespace)<br />
# Send the Invitation, Proxyform and Agenda to the members list<br />
<br />
=== Holding the General Assembly ===<br />
# Start with the "Welcome"<br />
# Make sure there are no valid objections to hold the assembly<br />
# Make sure someone writes the protocol. It needs to include at least the following items:<br />
## Beginning and end of the GA<br />
## Attending members and proxies<br />
## Agenda<br />
## Decisions made by voting w/ vote stats<br />
<br />
=== Paper work ===<br />
# Turn the minutes into a proper protocol (whole sentences prefered)<br />
# Send the protocol to the member list<br />
# Send the protocol to the german authorities. The address is:<br />
## TODO: Address / Club number for Amtsgericht<br />
<br />
[[Category:Verein]][[Category:General_Assemblies]]</div>Woglindehttp://www.openembedded.org/index.php?title=Checklist_for_the_General_Assembly&diff=7451Checklist for the General Assembly2014-10-14T11:50:09Z<p>Woglinde: /* Paper work */</p>
<hr />
<div>== Checklist to organize the General Assembly ==<br />
<br />
=== Preparing the General Assembly ===<br />
# Pick date at least ~7 weeks from now<br />
# Pick a venue for the conference<br />
# Take the last invitation and change the date, location and the year of the assembly<br />
# Point people to the proxy form. [[File:Proxy instructions-oe.pdf]] (Source - [[File:Proxy instructions-oe.odt]])<br />
# Create a WIKI page for the Agenda (TODO: Come up with a namespace)<br />
# Send the Invitation, Proxyform and Agenda to the members list<br />
<br />
=== Holding the General Assembly ===<br />
# Start with the "Welcome"<br />
# Make sure there are no valid objections to hold the assembly<br />
# Make sure someone writes the protocol. It needs to include at least the following items:<br />
## Beginning and end of the GA<br />
## Attending members and proxies<br />
## Agenda<br />
## Decisions made by voting w/ vote stats<br />
<br />
=== Paper work ===<br />
# Turn the minutes into a proper protocol (whole sentences prefered)<br />
# Send the protocol to the member list<br />
# Send the protocol to the german authorities. The address is:<br />
## TODO: Address / Club number for Amtsgericht<br />
<br />
[[Category:Verein,General_Assemblies]]</div>Woglindehttp://www.openembedded.org/index.php?title=Organization&diff=7449Organization2014-10-14T11:47:44Z<p>Woglinde: /* General Assemblies */</p>
<hr />
<div>The current organization for OE is a German eV legal entity (similar to KDE: http://ev.kde.org/) and is for the purpose of managing finances, voting, and membership.<br />
<br />
An 'eV' for 'eingetragener Verein', in the German law, translates to a voluntary organization; a group of individuals who voluntarily enter into an agreement to form a body (or organization) to accomplish a purpose. The organization has members.<br />
<br />
The OpenEmbedded eV statues are located here: http://docs.openembedded.org/organization/2008-11-22_statutes-de.pdf<br />
<br />
A bablefish translation is here -- could German speaking folks please clean this up: [[OpenEmbedded eV Statutes]]<br />
<br />
During FOSDEM 2008 in Brussels, Belgium, a group of founding members physically gathered to get the paperwork going.<br />
<br />
= The current board of directors =<br />
<br />
* ''Philip Balister''<br />
* Treasurer ''Leon Woestenberg ''<br />
* ''Denys Dmytriyenko''<br />
* ''Sean Hudson''<br />
<br />
= Current Members =<br />
(please keep in alphabetical order)<br />
<br />
# Alessandro Gardich<br />
# Anders Darander <br />
# Andrea Adami<br />
# Andreas Oberritter<br />
# Andrei Gherzan<br />
# Chris Larson<br />
# Cliff Brake<br />
# Daniel Willmann<br />
# Dave Stewart<br />
# Denys Dmytriyenko<br />
# Dirk Hohndel<br />
# Dirk Opfer<br />
# Dmitry EreminSolenikov<br />
# Eric Bénard<br />
# Esben Haabendal<br />
# Florian Boor<br />
# Frans Meulenbroeks<br />
# Graeme Gregory<br />
# Graham Gower<br />
# Henning Heinold<br />
# Holger Freyther<br />
# Jan Lübbe<br />
# Jason Kridner<br />
# Jeff Osier-Mixon <br />
# John Willis<br />
# Joshua Lock<br />
# Ken Gilmer<br />
# Khem Raj<br />
# Koen Kooi<br />
# Leon Woestenberg<br />
# Liam Girdwood<br />
# Marcin Juszkiewicz<br />
# Marco Cavallini<br />
# Mark Brown<br />
# Mark Hatle<br />
# Martin Jansa<br />
# Michael Lauer<br />
# Michael Smith<br />
# Otavio Salvador<br />
# Paul Eggleton<br />
# Philip Balister<br />
# Philip Blundell<br />
# Phillip Zabel<br />
# Richard Purdie<br />
# Robert Schuster<br />
# Roman I Khimov<br />
# Saul Wold<br />
# Scott Garman<br />
# Sean Hudson<br />
# Simon Busch<br />
# Stefan Schmidt<br />
# Steve Sakoman<br />
# Tom King<br />
# Tom Rini <br />
# Yu Ke <br />
# Yury Bushmelev<br />
<br />
= OE Developers =<br />
Openembedded Developers are people who have submitted code into any of the OpenEmbedded repositories. Due to the nature of OE, there are many developers, and also many different components. A good place to start is the list of git repositories [http://git.openembedded.org]. See [[OpenEmbedded Developers]] for a list of current developers.<br />
<br />
= Todo =<br />
* process for adding new members<br />
* process for voting<br />
* responsibility of the board<br />
* conflict resolution<br />
<br />
= Pointers for Board Members =<br />
* [[Checklist for the General Assembly]]<br />
<br />
= Online Voting Policy =<br />
* [[Online Voting Policy]]<br />
<br />
= Faq =<br />
; Are contributions tax deductible?<br /><br />
: Yes they are. <br />
; Should I become member of the OE e.V.?<br />
: If you are contributing to OE frequently and/or you are interested in getting involved in administrative or organisational tasks it might be a good idea to join OE e.V.<br />
; How do I become member of the OE e.V.?<br />
: Let an existing member introduce you by sending a short introduction to the 'ev' [http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-members mailinglist]. If you don't know one get in touch with us on the development mailinglist or IRC first. The e.V. is open for anyone to join and its not meant to be an exclusive club of a few developers. <br />
; Is there a membership fee?<br />
: Whist an e.V. can define a membership fee, the project has not chosen to set one.<br />
<br />
= General Assemblies =<br />
; * [[Prague, 2011]]<br />
; * [[Barcelona, 2012]]<br />
; * [[Edinburgh, 2013]]<br />
; * [[Dusseldorf, 2014]]<br />
<br />
[[Category:Verein]]</div>Woglindehttp://www.openembedded.org/index.php?title=Prague,_2011&diff=7447Prague, 20112014-10-14T11:32:04Z<p>Woglinde: /* Forms */</p>
<hr />
<div>==Location ==<br />
<br />
Clarion Congress Hotel, Prague, Czech Republic.<br />
October 28, 2011 at 1800.<br />
<br />
== Agenda ==<br />
<br />
* Discuss holding a General Assembly in the US<br />
* Discuss relaxing the 2 proxy rule (e.g. change to 3)<br />
* Financial status<br />
* Budget plan<br />
<br />
== Forms ==<br />
<br />
* Proxy form [[File:Proxy_instructions-oe.pdf]]<br />
<br />
[[Category:General_Assemblies]]</div>Woglindehttp://www.openembedded.org/index.php?title=Barcelona,_2012&diff=7445Barcelona, 20122014-10-14T11:31:46Z<p>Woglinde: /* Meeting notes */</p>
<hr />
<div>==Location ==<br />
<br />
Hotel Fira Palace · Barcelona, Spain<br />
Nov 7, 2012 at 17:00.<br />
<br />
== Agenda ==<br />
<br />
* Financial report<br />
* Board Elections, Dr. Michael Lauer, Florian Boor, and Philip Balister's terms are ending.<br />
<br />
== Forms ==<br />
<br />
* Proxy form [[File:Proxy_instructions-oe.pdf]]<br />
<br />
== Attendence Record ==<br />
<br />
(Proxies are in brackets)<br />
<br />
* Philip Balister (Denys Dmytriyenko, Steve Sakoman)<br />
* Stefan Schmidt (Michael Lauer, Simon Busch)<br />
* Jan Lübbe <br />
* Marco Cavallini (Frans Meulenbrooks) <br />
* Mark Hatle <br />
* Marcin Juszkiewicz<br />
* Richard Purdie (Dirk Hohndel)<br />
* Saul Wold<br />
* David Stewart<br />
* Scott Garman<br />
* Otavio Salvador <br />
* Andrei Gherzan<br />
* Khen Raj<br />
* Leon Woestenberg<br />
* Paul Eggleton<br />
* Andrea Adami<br />
* Anders Darander <br />
* Esben Haabendal<br />
* Koen Kooi (Tom Rini, Graeme Gregory)<br />
* Sean Hudson (Jeff Osier-Mixon)<br />
<br />
== Meeting notes ==<br />
<br />
Meeting opened 17:00<br />
Philip presented Finance Report<br />
Main expenses on event box<br />
Vote in Otavio Salvador and Andrei Gherzan as new members of the e.V, no objections<br />
TSC report:<br />
* Next election Jul 2013 for Richard<br />
* reported on TSC activity, generally happy with the way its working<br />
* noted that we need to publish minutes on time<br />
Election of board members. Candidates, Philip Balister, Leon Woestenberg, Sean Hudson, three people, three positions, voted in with no objections<br />
Reminder to membership that if changes to the voting procedure or statutes are wanted, someone needs to drive and present a coherent proposal<br />
Meeting closed 17:38<br />
<br />
[[Category:General_Assemblies]]</div>Woglindehttp://www.openembedded.org/index.php?title=Edinburgh,_2013&diff=7443Edinburgh, 20132014-10-14T11:31:24Z<p>Woglinde: /* Action Items */</p>
<hr />
<div>==Location ==<br />
<br />
Edinburgh International Conference Centre, Edinburgh, UK<br />
<br />
October 25, 2013 at 1830 - 1930 in Harris 1.<br />
<br />
== Agenda ==<br />
<br />
* Financial report<br />
* Election of new members<br />
<br />
== Forms ==<br />
<br />
* Proxy form [[File:Proxy_instructions-oe.pdf]]<br />
<br />
== Attendence Record ==<br />
<br />
(Proxies are in brackets)<br />
<br />
* Marco Cavallini 'mckoan' (proxying for Eric Bénard 'ericben')<br />
* Paul Eggleton 'bluelightning' (proxying for Andrea Adami 'ant')<br />
* Philip Balister 'Crofton' [board member]<br />
* Richard Purdie 'RP'<br />
* Martin Jansa 'JaMa' (Simon Busch 'morphis')<br />
* Denys Dmytriyenko 'denix' [board member]<br />
* Koen Kooi 'koen' ( Khem Raj 'khem')<br />
* Anders Darander<br />
* Mark Hatle 'fray' (Otavio Salvador 'otavio')<br />
* Sean Hudson 'darknighte' [board member]<br />
* Saul Wold 'sgw'<br />
* Stefan Schmidt<br />
* Leon Woestenberg 'likewise' [board member]<br />
* David Stewart<br />
* Jefro<br />
* Scott Garman<br />
<br />
Non members present and elected to become members<br />
<br />
* Jack Mitchell<br />
* Andrea Galbusera<br />
* Ross Burton<br />
<br />
Non members not present but elected to become members<br />
<br />
* Bruce Ashfield<br />
* Ulf Samuelsson<br />
<br />
== Meeting notes ==<br />
<br />
Meeting opened 18:35<br />
Attendees Documented<br />
Financially Summary Presented<br />
* Euro 1731<br />
* Taxes had to be filed, issues due to board transition<br />
* German language issues and documents required to be at a German address. Lots of overhead<br />
* No spending in last financial year<br />
* No donations received either<br />
* Setup SPI affiliation to allow for funds to be collected in and held in the US<br />
Financial Report Approved<br />
Discussion of possible uses for collected funds:<br />
Things membership generally in favor of:<br />
- travel sponsorship preferred <br />
- ship event box for conferences<br />
- create additional event box for NA<br />
- financial availability for emergency hardware<br />
- promotion at events<br />
Things membership generally not in favor of:<br />
- sponsorship at events e.g. coffee breaks<br />
Discussion about future of e.V. and whether SPI (as an example) would make sense<br />
- nobody against dissolving e.V. in principle<br />
- Feeling that board should investigate and consult members and come up with a proposal<br />
Meeting Ended 19:20<br />
<br />
== Action Items ==<br />
# Board to review alternate legal structures including affiliation with foundations, e.g. Apache, Gnome, etc<br />
# Board to put together draft budget proposal<br />
# Members: Investigate opportunities for "hack fest" sponsorship (close to conferences)<br />
<br />
[[Category:General_Assemblies]]</div>Woglindehttp://www.openembedded.org/index.php?title=Dusseldorf,_2014&diff=7441Dusseldorf, 20142014-10-14T11:30:22Z<p>Woglinde: /* Action Items */</p>
<hr />
<div>==Location ==<br />
<br />
Congress Centre Düsseldorf, Düsseldorf, Germany<br />
<br />
October 14, 2014 at 1300 - 1500 in room 111 (room changed, was 10 before).<br />
<br />
== Agenda ==<br />
<br />
* Financial report<br />
* Election of new members<br />
* Discussion about future of e.V. (started in 2013)<br />
<br />
== Forms ==<br />
<br />
* Proxy form [[File:Proxy_instructions-oe.pdf]]<br />
<br />
== Attendance ==<br />
* Leon<br />
* Philip "Crofton" Balister<br />
* Denys 'denix' Dmytriyenko<br />
* Sean 'darknighte' Hudson<br />
* 'Khem' Raj<br />
* Andrea 'g1zer0' Galbusera<br />
* Marco 'mckoan' Cavallini - (proxy for Andrea 'ant_work' Adami)<br />
* Martin 'JaMa' Jansa<br />
* Mark 'fray' Hatle<br />
* Henning "woglinde" Heinold<br />
* Anders Darander<br />
* Leon Woestenberg<br />
* Richard Purdie (proxy for Paul Eggleton + David Stewart)<br />
* Koen Kooi (proxy Graeme)<br />
<br />
Non members present and elected to become members <br />
<br />
* Nicolas Dechesne<br />
<br />
Non members not present but elected to become members <br />
<br />
* Trevor Woerner<br />
* Gary Thomas<br />
<br />
* Tim Orling<br />
* (need name from Crofton)<br />
<br />
== Meeting notes ==<br />
Meeting opened 13:05<br />
Atendees Documented<br />
Financial Summary Presented<br />
* Various forms had to be filed<br />
* Challenges due to lack of German address and language barriers<br />
* SPI Account created with one donation<br />
* No other changes to accounts<br />
* Treasures report approved<br />
<br />
== Action Items ==<br />
<br />
[[Category:General_Assemblies]]</div>Woglindehttp://www.openembedded.org/index.php?title=Template:Main_page/news&diff=7431Template:Main page/news2014-10-14T07:05:06Z<p>Woglinde: </p>
<hr />
<div><!-- Please use ISO date format (YYYY-MM-DD) --><br />
<!-- Please only three entries of recent news, if there are more, move the oldest one to the top of the NewsArchive page --><br />
<br />
'''Recent News:'''.<br />
* '''''2014-10-14:''''' OpenEmbedded e.V. will have the annual meeting at the [[Dusseldorf,_2014 | ELCE]] in Düsseldorf<br />
* '''''2014-05-02:''''' OpenEmbedded will host [[OEDAM]] in Santa Clara. See you there!<br />
* '''''2014-01-06:''''' OpenEmbedded will have a stand at [[FOSDEM 2014]] in Brussels. See you there!<br />
* '''''2013-05-21:''''' OpenEmbedded will have a stand at [http://www.linuxtag.org/2013/ LinuxTag] in Berlin. See you there!<br />
* '''''2013-01-22:''''' OpenEmbedded will have a stand at Europe's largest free software conference - [[FOSDEM 2013]] in Brussels. See you there!<br />
* '''''2012-08-31:''''' Meta-webos added<br />
* '''''2012-07-16:''''' Meta-systemd moved from meta-oe <br />
<br />
<br />
<br />
See [[NewsArchive|News Archive]] for older news.</div>Woglindehttp://www.openembedded.org/index.php?title=Dusseldorf,_2014&diff=7429Dusseldorf, 20142014-10-14T06:56:05Z<p>Woglinde: /* Location */</p>
<hr />
<div>==Location ==<br />
<br />
Congress Centre Düsseldorf, Düsseldorf, Germany<br />
<br />
October 14, 2014 at 1300 - 1500 in room 111 (room changed, was 10 before).<br />
<br />
== Agenda ==<br />
<br />
* Financial report<br />
* Election of new members<br />
* Discussion about future of e.V. (started in 2013)<br />
<br />
== Forms ==<br />
<br />
* Proxy form [[File:Proxy_instructions-oe.pdf]]<br />
<br />
== Attendance ==<br />
* Sean 'darknighte' Hudson<br />
* Martin 'JaMa' Jansa<br />
* Jeff 'Jefro' Osier-Mixon<br />
* Denys 'denix' Dmytriyenko<br />
* Dave "davest" Stewart (likely)<br />
* Philip "Crofton" Balister<br />
* Ross "rburton" Burton<br />
* 'Khem' Raj<br />
* Mark 'fray' Hatle<br />
* Henning "woglinde" Heinold (I think, I need the reactivation)<br />
* Anders Darander<br />
* Andrea 'g1zer0' Galbusera<br />
* Marco 'mckoan' Cavallini - (proxy for Andrea 'ant_work' Adami)<br />
<br />
== Meeting notes ==<br />
<br />
== Action Items ==</div>Woglindehttp://www.openembedded.org/index.php?title=Dusseldorf,_2014&diff=7395Dusseldorf, 20142014-09-07T16:43:56Z<p>Woglinde: /* Attendance */</p>
<hr />
<div>==Location ==<br />
<br />
Congress Centre Düsseldorf, Düsseldorf, Germany<br />
<br />
October 14, 2014 at 1300 - 1500 in room 10.<br />
<br />
== Agenda ==<br />
<br />
* Financial report<br />
* Election of new members<br />
<br />
== Forms ==<br />
<br />
* Proxy form [[File:Proxy_instructions-oe.pdf]]<br />
<br />
== Attendance ==<br />
* Martin 'JaMa' Jansa<br />
* Jeff 'Jefro' Osier-Mixon<br />
* Denys 'denix' Dmytriyenko<br />
* Dave "davest" Stewart (likely)<br />
* Philip "Crofton" Balister<br />
* Ross "rburton" Burton<br />
* 'Khem' Raj<br />
* Mark 'fray' Hatle<br />
* Henning "woglinde" Heinold (I think, I need the reactivation)<br />
<br />
== Meeting notes ==<br />
<br />
== Action Items ==</div>Woglindehttp://www.openembedded.org/index.php?title=FOSDEM_2014&diff=6739FOSDEM 20142014-01-15T22:43:26Z<p>Woglinde: /* 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, possibly 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 />
<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/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>Woglindehttp://www.openembedded.org/index.php?title=FOSDEM_2014&diff=6737FOSDEM 20142014-01-15T22:42:30Z<p>Woglinde: /* Manning */</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, possibly 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 />
<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/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>Woglindehttp://www.openembedded.org/index.php?title=Fosdem_2012&diff=4537Fosdem 20122012-01-13T15:04:13Z<p>Woglinde: /* 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 />
* 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 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 our SCM?) 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 />
== Flyers and posters ==<br />
You can bring and/or print OpenEmbedded flyers and posters? Add your name and what you'll bring.<br />
<br />
== Power extensions, adapters and other stand material ==<br />
Bringing devices is cool but we need a way to bring power to them too. Additionally people might need power sockets for different systems than the european one. List your name<br />
and what stuff you can bring.<br />
<br />
* Robert Schuster:<br />
**3-socket power extension (EU)<br />
**tape<br />
**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.</div>Woglindehttp://www.openembedded.org/index.php?title=Fosdem_2012&diff=4535Fosdem 20122012-01-13T15:03:10Z<p>Woglinde: /* Manning */</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 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 our SCM?) 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 />
== Flyers and posters ==<br />
You can bring and/or print OpenEmbedded flyers and posters? Add your name and what you'll bring.<br />
<br />
== Power extensions, adapters and other stand material ==<br />
Bringing devices is cool but we need a way to bring power to them too. Additionally people might need power sockets for different systems than the european one. List your name<br />
and what stuff you can bring.<br />
<br />
* Robert Schuster:<br />
**3-socket power extension (EU)<br />
**tape<br />
**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 />
<br />
== Hotels ==<br />
<br />
Although FOSDEM itself takes place at the ULB campus, most folks prefer to stay nearer the city centre.<br />
<br />
The Astrid has traditionally been the default choice for OE developers, though there are many other hotels in the area. If you are staying in a hotel other than the Astrid, feel free to add it to this section for the benefit of others.<br />
<br />
Scandic Grand Place.<br />
Rue d'Arenberg 18<br />
Close to beer event (300 m) and Central Station.<br />
Tram to Fosdem around the corner.</div>Woglindehttp://www.openembedded.org/index.php?title=Fosdem_2011&diff=4435Fosdem 20112011-10-27T15:17:38Z<p>Woglinde: </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)<br />
* Ulf Samuelsson (Saturday and Sunday occasionally)<br />
* Philip Balister (As needed)<br />
* Florian Boor (Saturday)<br />
<br />
== Devices ==<br />
Add your name and what devices you'll bring for the stand.<br />
<br />
Ulf Samuelsson - AT91SAM9M10EKES booting Openembedded/Android from SD-Card<br />
(No flash on board enabled)<br />
<br />
Robert Schuster - Pandaboard - Hopefully booting Angstrom with some desktop and Java foo. Try to get hold of a small TFT display<br />
<br />
== Flyers and posters ==<br />
You can bring and/or print OpenEmbedded flyers and posters? Add your name and what you'll bring.<br />
<br />
* Florian: Poster from last year, flyers<br />
<br />
== Power extensions, adapters and other stand material ==<br />
Bringing devices is cool but we need a way to bring power to them too. Additionally people might need power sockets for different systems than the european one. List your name<br />
and what stuff you can bring.<br />
<br />
* Robert Schuster:<br />
**3-socket power extension (EU)<br />
**tape<br />
<br />
= General attendance =<br />
<br />
Attending FOSDEM 2011? Add your name to this page so that other developers can look out for you!<br />
<br />
* Esben Haabendal<br />
* Frans Meulenbroeks (eFfeM) (sunday only)<br />
* Philip Balister (Crofton)<br />
* Robert Schuster (rschus/thebohemian)<br />
* Ulf Samuelsson<br />
* Graeme Gregory (XorA)<br />
* Florian Boor (florian)<br />
* Denis Carikli (GNUtoo)<br />
<br />
== Hotels ==<br />
<br />
Although FOSDEM itself takes place at the ULB campus, most folks prefer to stay nearer the city centre.<br />
<br />
The Astrid has traditionally been the default choice for OE developers, though there are many other hotels in the area. If you are staying in a hotel other than the Astrid, feel free to add it to this section for the benefit of others.<br />
<br />
Scandic Grand Place.<br />
Rue d'Arenberg 18<br />
Close to beer event (300 m) and Central Station.<br />
Tram to Fosdem around the corner.</div>Woglindehttp://www.openembedded.org/index.php?title=Fosdem_2010&diff=4433Fosdem 20102011-10-27T15:16:52Z<p>Woglinde: </p>
<hr />
<div>[[Category:Conferences]]<br />
<br />
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 (mckoan)<br />
* Frans Meulenbroeks (eFfeM)<br />
* Ulf Samuelsson<br />
* Marcin Juszkiewicz<br />
* Alessandro Gardich (gremlin)<br />
* Florian Boor<br />
* Denis Carikli (GNUtoo)<br />
* Robert Schuster (rschuster/thebohemian)<br />
* Paul Eggleton (bluelightning)<br />
* Boudewijn Kranendonk<br />
* Klaas van Gend<br />
* Rolf 'Laibsch' Leggewie<br />
* Xerxes Ranby<br />
* Joshua Lock (incandescant)<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 />
<br />
Staying at Scandic, (75 Euro/night)<br />
A stone throw from the Friday Beer Event<br />
Good communications with the Campus. Bus Stop right outside.<br />
/Ulf Samuelsson<br />
<br />
Staying in Atlas (near Astrid), only saturday evening. I will also bring some books and my eeepc and openrd board --- eFfeM</div>Woglindehttp://www.openembedded.org/index.php?title=Category:Conferences&diff=4431Category:Conferences2011-10-27T15:15:03Z<p>Woglinde: Created page with "Category for all the conferences"</p>
<hr />
<div>Category for all the conferences</div>Woglindehttp://www.openembedded.org/index.php?title=Category:OEDEM&diff=4429Category:OEDEM2011-10-27T15:03:00Z<p>Woglinde: </p>
<hr />
<div>OE Developper meetings - see you in the real world<br />
<br />
planning and documentation</div>Woglindehttp://www.openembedded.org/index.php?title=Category:OEDEM&diff=4427Category:OEDEM2011-10-27T15:01:30Z<p>Woglinde: </p>
<hr />
<div>[[Category:]<br />
<br />
<br />
OE Developper meetings - see you in the real world<br />
<br />
planning and documentation</div>Woglindehttp://www.openembedded.org/index.php?title=Category:OEDEM&diff=4425Category:OEDEM2011-10-27T14:59:35Z<p>Woglinde: </p>
<hr />
<div>[[Category:Categories]]<br />
<br />
<br />
OE Developper meetings - see you in the real world<br />
<br />
planning and documentation</div>Woglindehttp://www.openembedded.org/index.php?title=Java&diff=4339Java2011-07-26T08:26:10Z<p>Woglinde: /* Version suggestions */</p>
<hr />
<div>This page is here to answer all things Java related to OpenEmbedded.<br />
<br />
=State of support=<br />
==Virtual machine and class library==<br />
Currently (since September 2008) you will be able to build packages for your target system that use a many VMs and their class libraries. For a full J2SE environment on the target you can build JamVM and Cacao as the virtual machine and GNU Classpath as the class library.<br />
<br />
For J2ME you can have the "Connected Device Configuration" (CDC) in either the "Foundation" or "Personal" profile using the GPLed PhoneME Advanced virtual machine. See below for details.<br />
<br />
For J2ME's "Mobile Information Device Profile" (MIDP2.0) you can use MIDPath.<br />
<br />
Support for OpenJDK (with either Cacao or Hotspot/Zero as the runtime) is available through the Jalimo overlay. This will be merged soon. Future additions will also include Hotspot/Shark which is a variant of Hotspot using a generic JIT compiler based on LLVM.<br />
<br />
It is planned to use OpenJDK as the native Java runtime. That way Java packages will be compiled against this library.<br />
<br />
==Java libraries==<br />
The number of available Java libraries is still small but can grow quickly as the necessary infrastructure is in place. Currently libraries such as dbus-java, kxml2, libmatthew, librxtx, sqlitejdbc, javasqlite, woodstox, xmlpull, SWT (3.4, Gtk+), a large bunch of the Jakarta commons libraries and stuff like BSF, POI, log4j, logkit and ORO are available.<br />
<br />
For the Maemo platform's "hildon" environment special SWT packages are available which allow a better integration (i.e. hildon menus, hildon file chooser dialog).<br />
<br />
== PhoneME Advanced ==<br />
PhoneME Advanced is provided in the 'Foundation' and 'Personal' profile through the recipes phoneme-advanced-foundation and (surprise!) phoneme-advanced-personal. The way the recipes are written both can be compiled and installed at the same time on the target device.<br />
<br />
''Note:'' At the moment the personal profile's AWT support relies on Qt3 which is heavily outdated. If possible you should prefer the foundation profile with SWT for the GUI or contribute to [https://phoneme.dev.java.net PhoneME] to fix this. :)<br />
<br />
When a PhoneME Advanced package is installed you will find the VM in $libdir_jvm (which is ''/usr/lib/jvm'' by default). The package provides a java-cdc symlink which is changeable through update-alternatives and a cvm-<profile name> symlink.<br />
<br />
==J2ME MIDP2.0==<br />
J2ME MIDP2.0 is supported through the MIDPath project. MIDPath provides the neccessary libraries (taken from PhoneME and/or the respective JSRs) and OpenEmbedded has direct support for a few devices (e.g. button mappings). Please note that while MIDPath can run most MIDP2.0 programs it is no official MIDP2.0 implementation.<br />
<br />
MIDPath can be run on top of either PhoneME Advanced or a J2SE-like environment (JamVM/Cacao and GNU Classpath or any of the OpenJDK variants). If PhoneME is installed it is preferred.<br />
<br />
==OpenJDK==<br />
OpenJDK is the name of the F/OSS Java stack from Sun. It normally consists of the class library (often referred to as OpenJDK as well), the Hotspot runtime and many many tools (e.g. javah, rmic, javaws). OpenEmbedded support building OpenJDK with the CacaoVM. This gives many platforms which Hotspot does not directly support a fast Java VM. Please note that Cacao lacks many advanced features like JVMTI. Your only other option is the Zero port of Hotspot. Zero is a C++-based interpreter and can be run on any platform supporting libffi. This gives you a featurefull VM for many platforms at the cost of performance.<br />
<br />
==Toolchain==<br />
In order to build Java packages no virtual machine needs to be installed on the build machine. OpenEmbedded builds everything on its own.<br />
<br />
Missing but planned to be included are popular Java build tools like Ant.<br />
<br />
=== GNU Classpath Tools ===<br />
Included in the package classpath-native are the tools 'gjar', 'gjavah', 'gjavap', 'gjarsigner' (and soon gjdoc). Those tools usually work without problems and should be fully compatible to the ones provided by OpenJDK.<br />
<br />
=== OpenJDK language tools ===<br />
OpenEmbedded supports the OpenJDK language tools consisting of 'sun-javac', 'javap', 'javah' and 'apt'. Put 'openjdk-langtools-native' to the dependencies of your recipe to use those binaries. Albeit the tools are from OpenJDK they run on Cacao/JamVM and GNU Classpath.<br />
<br />
'''Note:''' openjdk-langtools-native is not a provider of 'virtual/javac-native' it only provides a 'sun-javac' binary. Refer to the [[#Native Java compiler aka virtual/javac-native|virtual/javac-native discussion]] for details.<br />
<br />
=== Ant ===<br />
Ant is an often used tool in the Java world. Even OpenJDK uses it. Unfortunately it is also a complex beast with many dependencies (many of which use Ant itself). Despite all this troubles Ant (1.7.1) is available and supported as an application which can be run from build recipes.<br />
<br />
=A word of warning=<br />
Every so often people on the net suggest that in order to get Java stuff running in OpenEmbedded, you need to install a JDK, Kaffe or Jikes and then make modifications to the PATH variable in order to allow the<br />
build use the runtime or compiler. '''These suggestions are wrong!''' The Java support in OpenEmbedded is (and strives to stay) ''completely'' self-hosting. You should not need a single bit of Java on your host OS to get the Java recipes to compile.<br />
<br />
On the other hand the Java support in OE can happily co-exist with whatever 'java', 'javac' and other tools you might have installed in your OS. Due to the nature of some configure scripts, those will sometimes find these executables but in the end only the tools from OpenEmbedded's staging directory will be used (if not its a bug that needs to be fixed).<br />
<br />
Please note that problem reports that are caused by pulling in native Java tools (those from your OS) into the OpenEmbedded build process will be closed as invalid. The reason is that the recipes are only supposed to work with the built-in toolchain.<br />
<br />
=Configuring (add info about what and where)=<br />
In this section you learn about the things you can set up. In many OpenEmbedded-based distributions some or most of these decision may have already been made for you so there is no need to specify them. However in case you want to provide the Java support in your distribution you need to know which knobs are available.<br />
<br />
==Bootstrap process==<br />
As told in the toolchain support section the whole Java support in OpenEmbedded is self-hosting. This mean you do not need to have any bit of Java on your build machine as OpenEmbedded will build this itself.<br />
<br />
This bootstrap process contains the following steps: At first jikes-native is compiled which is a Java 1.4-capable compiler that does not need a runtime or (strictly) a class library to work. With this compiler we compile the initial runtime (package virtual/java-initial).<br />
<br />
virtual/java-initial is a preliminary runtime. This virtual package is currently provided by cacao-initial or jamvm-initial. After that ecj-initial is built. At that point we have a 1.5-capable compiler running on a Java 1.4 compatible VM.<br />
<br />
The compiler is then used to build virtual/java-native and finally virtual/javac-native. The former virtual package is provided by either cacao-native or jamvm-native. The latter package is currently only provided through ecj-bootstrap-native. Having built these packages provides the OpenEmbedded build environment with a Java5-capable compiler and runtime. At that point we are ready to compile any other Java package.<br />
<br />
==Bootstrap virtual machine aka virtual/java-initial==<br />
The bootstrap virtual machine has the sole purpose of running ecj-initial (the bootstrap compiler) to compile a 1.5-capable runtime and library. The bootstrap VM runs on your build host and is therefore a -native package. Inside the native staging directory the VM provides a 'java-initial' executable.<br />
<br />
As told above there are currently two packages that provide 'virtual/java-native'. Add<br />
<br />
PREFERRED_PROVIDER_virtual/java-initial = "cacao-initial"<br />
PREFERRED_VERSION_cacao-initial = "0.98"<br />
<br />
to your local or site configuration to choose the Cacao VM. This virtual machine has a JIT compiler and is generally faster but takes a bit longer to compile. Furthermore this VM is only tested to work correctly on X86 build hosts. If you chose Cacao there will also be a 'cacao-initial' binary in your native staging directory.<br />
<br />
'''Note:''' There is a problem with Cacao 0.98 running on recent distributions where mmaping the zero page is not allowed. Chose jamvm-initial (see below) if you do not want to change the vm_mmap_min_adr restriction on your system.<br />
<br />
In case Cacao is unsuitable for you add<br />
<br />
PREFERRED_PROVIDER_virtual/java-initial = "jamvm-initial"<br />
PREFERRED_VERSION_jamvm-initial = "1.4.5"<br />
<br />
to your configuration. JamVM is an interpreting Java virtual machine. Despite interpreting only it is very fast (implements many modern interpreter techniques) and compiles quickly. Furthermore it is known to work on X86 and PowerPC build hosts.<br />
<br />
==Native virtual machine aka virtual/java-native==<br />
As for virtual/java-initial this virtual package provides a Java virtual machine which runs on your build host. Its purpose is to run any Java programs that are needed during your build process. The most prominent program that it is supposed to run is the compiler ECJ. The virtual/java-native package provides a 'java' binary inside the native staging directory. At the moment you can chose between two runtimes: Cacao and JamVM.<br />
<br />
As for the general features it is the same as for java-initial. However for virtual/java-native later versions of the VMs are used so stability and platform support is better. For instance you can use cacao-native on PowerPC as well since the version of Cacao used properly supports it.<br />
<br />
To chose Cacao add the following line to your configuration:<br />
<br />
PREFERRED_PROVIDER_virtual/java-native = "cacao-native"<br />
<br />
Besides 'java' cacao-native install a 'cacao' binary into the native staging directory.<br />
<br />
If you favor JamVM (or are having trouble with Cacao) use:<br />
<br />
PREFERRED_PROVIDER_virtual/java-native = "jamvm-native"<br />
<br />
There will also be a 'jamvm' binary in native staging directory besides the 'java' one with jamvm-native.<br />
<br />
'''Note:''' Native versions of jamvm are unsupported on amd64/x86_64 hosts since OpenEmbedded lacks a native libffi. If you desperately need jamvm on your platform consider installing the development package for libffi of your distro.<br />
<br />
== Native Java compiler aka virtual/javac-native ==<br />
The virtual/javac-native package provides the 'javac' binary which is to be found within the native staging directory. This compiler is used to build all of the Java packages within OpenEmbedded. <br />
<br />
There are two recipes which provide this functionality: <br />
<br />
ecj-bootstrap-native uses the commandline variant of the Eclipse IDE's integrated compiler. In order to use that compiler add the following to your configuration:<br />
<br />
PREFERRED_PROVIDER_virtual/javac-native = "ecj-bootstrap-native"<br />
<br />
The second option is OpenJDK's Java compiler which is the F/OSS variant of good old 'javac'. If you experience trouble with ecj you should try OpenJDK's<br />
Java compiler by setting the following in your configuration:<br />
<br />
PREFERRED_PROVIDER_virtual/javac-native = "openjdk-javac-native"<br />
<br />
<br />
'''Note:''' OpenJDK's javac is actually build in the package openjdk-language-tools-native (provides a 'sun-javac' binary). The reason for this is to allow 'ecj-bootstrap-native' and 'openjdk-language-tools-native' to coexist in the staging dir.<br />
<br />
=== ecj-bootstrap-native, ecj-initial and libecj-bootstrap ===<br />
Since ecj-initial and ecj-bootstrap-native use the same jar file the compilation step for both packages is done through in the libecj-bootstrap recipe. Therefore in order to decide which ECJ version to use for compilation you need to set a version preference for that recipe:<br />
<br />
PREFERRED_VERSION_libecj-bootstrap = "3.4"<br />
<br />
== Target virtual machine ==<br />
'''Note:''' There used to be a virtual/java package. It turned out that by having this it prevented offering multiple J2SE-compatible VMs for the target device.<br />
<br />
From a distributors point of view you can build the jamvm, cacao, phoneme or openjdk recipes and provide them to your users. Those can then either install the packages directly by its name or rely<br />
on a chosing of the packaging.<br />
<br />
At the moment Cacao and JamVM are supported runtimes. Cacao is ready for x86, PowerPC and ARM systems (others are untested and AVR32 is not suppported) and has a JIT compiler. JamVM can be used on x86, PowerPC, ARM and MIPS. PhoneME Advanced should support x86, PowerPC, ARM, MIPS and Sparc.<br />
<br />
Additionally OpenJDK can be built using either Cacao (same properties as above) or the Zero port of Hotspot. Zero is an C++-based interpreter capable of running on any platform that is supported by libffi.<br />
<br />
When installed all J2SE runtimes provide the 'java' executable (chosen through update-alternatives). PhoneME Advanced gives you a 'java-cdc' executable.<br />
<br />
=== Runtime provider ===<br />
'''Warning:''' When we talk of 'runtime provider' here this is meant in the OpenEmbedded sense (PROVIDES = build provides, RPROVIDES = runtime provides)<br />
The Cacao, JamVM or OpenJDK packages are set to provide 'java2-runtime'. Packages which need a J2SE-capable VM should RDEPEND on this. By inheriting the 'java-library' class in your recipe this is done automatically.<br />
<br />
PhoneME on the other hand is set to provide 'java-cdc-runtime'.<br />
<br />
== GNU Classpath for headless machines aka classpath-minimal ==<br />
Through setting the provider for 'classpath' you can decide whether you build a full class library with support for AWT/Swing (having a gtk+ dependency) or a variant that works without that and is primarily meant for headless devices. It might also be handy if you decide not to use AWT/Swing and use SWT instead. To chose the minimal variant add this to your configuration:<br />
<br />
PREFERRED_PROVIDER_classpath = "classpath-minimal"<br />
<br />
Otherwise you need to add this line:<br />
<br />
PREFERRED_PROVIDER_classpath = "classpath"<br />
<br />
Currently the Angstrom distribution does not set a preference and you have to provide your own.<br />
<br />
=Writing a Java recipe=<br />
This section is going to tell you, how to write a proper recipe to build a Java library or program.<br />
<br />
'''At the moment this is a stub and you will only find some scattered information which at a later point will be merged into a consistent whole.'''<br />
<br />
==java-native.bbclass==<br />
If you use the ''java-library'' bbclass in a recipe ''foo'' and generate a native variant (e.g. ''foo-native'') you should use<br />
<br />
inherit java-native<br />
<br />
instead of ''native''. By doing so, you make sure, that any jars created by the recipe are properly installed into staging.<br />
<br />
==ant-native==<br />
If you need Ant to build your recipe add ''ant-native'' to your recipes dependencies. This will allow you to call the built-in Ant executable.<br />
<br />
= Information on specific libraries =<br />
== swt3.4-gtk and swt3.4-gtk-hildon ==<br />
Some effort has been done to integrate Gtk+-based SWT 3.4 into the Hildon environment (that is what Maemo provides). Distributions targeting Maemo should set the preferred provider for swt3.4-gtk like this:<br />
<br />
PREFERRED_PROVIDER_swt3.4-gtk = "swt3.4-gtk-hildon"<br />
<br />
''Important'': If you do not want the hildon variant it is best to declare<br />
<br />
PREFERRED_PROVIDER_swt3.4-gtk = "swt3.4-gtk"<br />
<br />
as well. So bitbake will not chose the wrong one by accident (which would otherwise pull in all kinds of unwanted dependencies).<br />
<br />
= Caveats, known issues, hints, miscellaneous information =<br />
== Version suggestions ==<br />
Everyone and his dog knows that combining glibc 2.8, gcc 2.95 and Linux kernel 2.6.26 is not going to work. In the GNU Classpath realm we also have a set of versions that do not fit together. Here are some suggestions for your PREFERRED_VERSIONs. Stick to these if you are unsure. You can always find out which version are ''supposed'' to be compatible by reading the READMEs of the VMs.<br />
<br />
=== openjdk ===<br />
To prevent building of cacao for target add this in your local.conf<br />
<br />
PREFERRED_PROVIDER_openjdk-6-jre = "openjdk-6-jre"<br />
<br />
=== jamvm-initial and classpath-initial ===<br />
Use this and nothing else:<br />
<br />
PREFERRED_VERSION_jamvm-initial = "1.4.5"<br />
PREFERRED_VERSION_classpath-initial = "0.93"<br />
<br />
=== cacao-initial and classpath-initial ===<br />
Use this and nothing else:<br />
<br />
PREFERRED_VERSION_cacao-initial = "0.98"<br />
PREFERRED_VERSION_classpath-initial = "0.93"<br />
<br />
=== jamvm[-native] and classpath[-native] ===<br />
These are the releases that appear to be stable.<br />
<br />
PREFERRED_VERSION_jamvm-native = "1.5.3"<br />
PREFERRED_VERSION_classpath-native = "0.98"<br />
<br />
For the target device:<br />
<br />
PREFERRED_VERSION_jamvm = "1.5.2"<br />
PREFERRED_VERSION_classpath = "0.98"<br />
<br />
=== cacao[-native] and classpath[-native] ===<br />
These releases appear to be stable:<br />
<br />
PREFERRED_VERSION_cacao-native = "0.99.3"<br />
PREFERRED_VERSION_classpath-native = "0.97.2"<br />
<br />
For the target device take these:<br />
<br />
PREFERRED_VERSION_cacao = "0.99.4"<br />
PREFERRED_VERSION_classpath = "0.98"<br />
<br />
== Extra binaries and symlinks ==<br />
Since both Cacao and JamVM can be installed in staging you can use this and modify the 'java' or 'java-initial' symlink if you want to switch to a certain VM.<br />
<br />
== Debugging Cacao on the target ==<br />
You need to debug the Cacao JVM on your target device using GDB and need some pointers on how to get started? Read [https://wiki.evolvis.org/jalimo/index.php/CacaoDebugging this] page from the Jalimo Wiki.<br />
<br />
=Future plans =<br />
==Default Bytecode compliance level==<br />
Soon an option will be introduced to set the default bytecode compliance level. For any Java package that does not explicitly provide this level (not many do this) the one you set in your configuration will be used.<br />
<br />
==OpenJDK + Cacao==<br />
The flexibility of the Cacao runtime allows it to run it with OpenJDK's class library. This allows you to use the official class library and a JIT-capable runtime on an ARM device (as of today Hotspot has no JIT on ARM).<br />
<br />
Since the middle of August 2008 OpenJDK + Cacao can be build and is included in the Debian armel sid repositories (package cacao-oj6-sdk). Xerxes Rånby is showing some webbapplets running using OpenJDK + CACAO on his blog: http://labb.zafena.se/?p=1<br />
<br />
Since December 2008 OpenJDK + Cacao can be crosscompiled with OpenEmbedded as demonstrated by Robert Schuster!<br />
Check out http://rschuster.blogs.evolvis.org/2008/12/21/serving-cross-compiled-openjdk-with-icedtea/ and the answers http://rschuster.blogs.evolvis.org/2008/12/23/comments-on-latest-post-on-openjdk/<br />
<br />
==Ant integration for build recipes==<br />
Although ''ant'' can be used as a standalone tool there is no direct support for it in the recipe. E.g. the Debian buildsystem (CDBS) has support classes that can be used for Ant-based Java sourcepackages. It would be nice to have this too for OpenEmbedded.<br />
<br />
= FAQ =<br />
This space is for *your* questions and those that appeared more often on the mailing list. Things will be added here by the Jalimo folk/OE-Java maintainers or by you asking a question.<br />
<br />
== Q: I do get all these editions, configurations and profiles that exist in the Java world wrong. Any pointer on this? ==<br />
I found these articles in Wikipedia helpful to clarify the situation [http://en.wikipedia.org/wiki/Java_platform Java platform], [http://en.wikipedia.org/wiki/Java_ME Java ME].<br />
<br />
== Q: I need to solve a specific Java problem in OE and want to throw money at this. Whom can I contact? ==<br />
The [http://jalimo.org Jalimo] project has done a lot of Java work in OE and are available for contract work. You can also ask for experienced devs on the openembedded-devel mailing list.<br />
<br />
<br />
<br />
[[Category:FAQ]]<br />
[[Category:Software Components]]<br />
[[Category:Java]]</div>Woglindehttp://www.openembedded.org/index.php?title=Java&diff=4337Java2011-07-26T08:24:27Z<p>Woglinde: /* libecj-bootstrap */</p>
<hr />
<div>This page is here to answer all things Java related to OpenEmbedded.<br />
<br />
=State of support=<br />
==Virtual machine and class library==<br />
Currently (since September 2008) you will be able to build packages for your target system that use a many VMs and their class libraries. For a full J2SE environment on the target you can build JamVM and Cacao as the virtual machine and GNU Classpath as the class library.<br />
<br />
For J2ME you can have the "Connected Device Configuration" (CDC) in either the "Foundation" or "Personal" profile using the GPLed PhoneME Advanced virtual machine. See below for details.<br />
<br />
For J2ME's "Mobile Information Device Profile" (MIDP2.0) you can use MIDPath.<br />
<br />
Support for OpenJDK (with either Cacao or Hotspot/Zero as the runtime) is available through the Jalimo overlay. This will be merged soon. Future additions will also include Hotspot/Shark which is a variant of Hotspot using a generic JIT compiler based on LLVM.<br />
<br />
It is planned to use OpenJDK as the native Java runtime. That way Java packages will be compiled against this library.<br />
<br />
==Java libraries==<br />
The number of available Java libraries is still small but can grow quickly as the necessary infrastructure is in place. Currently libraries such as dbus-java, kxml2, libmatthew, librxtx, sqlitejdbc, javasqlite, woodstox, xmlpull, SWT (3.4, Gtk+), a large bunch of the Jakarta commons libraries and stuff like BSF, POI, log4j, logkit and ORO are available.<br />
<br />
For the Maemo platform's "hildon" environment special SWT packages are available which allow a better integration (i.e. hildon menus, hildon file chooser dialog).<br />
<br />
== PhoneME Advanced ==<br />
PhoneME Advanced is provided in the 'Foundation' and 'Personal' profile through the recipes phoneme-advanced-foundation and (surprise!) phoneme-advanced-personal. The way the recipes are written both can be compiled and installed at the same time on the target device.<br />
<br />
''Note:'' At the moment the personal profile's AWT support relies on Qt3 which is heavily outdated. If possible you should prefer the foundation profile with SWT for the GUI or contribute to [https://phoneme.dev.java.net PhoneME] to fix this. :)<br />
<br />
When a PhoneME Advanced package is installed you will find the VM in $libdir_jvm (which is ''/usr/lib/jvm'' by default). The package provides a java-cdc symlink which is changeable through update-alternatives and a cvm-<profile name> symlink.<br />
<br />
==J2ME MIDP2.0==<br />
J2ME MIDP2.0 is supported through the MIDPath project. MIDPath provides the neccessary libraries (taken from PhoneME and/or the respective JSRs) and OpenEmbedded has direct support for a few devices (e.g. button mappings). Please note that while MIDPath can run most MIDP2.0 programs it is no official MIDP2.0 implementation.<br />
<br />
MIDPath can be run on top of either PhoneME Advanced or a J2SE-like environment (JamVM/Cacao and GNU Classpath or any of the OpenJDK variants). If PhoneME is installed it is preferred.<br />
<br />
==OpenJDK==<br />
OpenJDK is the name of the F/OSS Java stack from Sun. It normally consists of the class library (often referred to as OpenJDK as well), the Hotspot runtime and many many tools (e.g. javah, rmic, javaws). OpenEmbedded support building OpenJDK with the CacaoVM. This gives many platforms which Hotspot does not directly support a fast Java VM. Please note that Cacao lacks many advanced features like JVMTI. Your only other option is the Zero port of Hotspot. Zero is a C++-based interpreter and can be run on any platform supporting libffi. This gives you a featurefull VM for many platforms at the cost of performance.<br />
<br />
==Toolchain==<br />
In order to build Java packages no virtual machine needs to be installed on the build machine. OpenEmbedded builds everything on its own.<br />
<br />
Missing but planned to be included are popular Java build tools like Ant.<br />
<br />
=== GNU Classpath Tools ===<br />
Included in the package classpath-native are the tools 'gjar', 'gjavah', 'gjavap', 'gjarsigner' (and soon gjdoc). Those tools usually work without problems and should be fully compatible to the ones provided by OpenJDK.<br />
<br />
=== OpenJDK language tools ===<br />
OpenEmbedded supports the OpenJDK language tools consisting of 'sun-javac', 'javap', 'javah' and 'apt'. Put 'openjdk-langtools-native' to the dependencies of your recipe to use those binaries. Albeit the tools are from OpenJDK they run on Cacao/JamVM and GNU Classpath.<br />
<br />
'''Note:''' openjdk-langtools-native is not a provider of 'virtual/javac-native' it only provides a 'sun-javac' binary. Refer to the [[#Native Java compiler aka virtual/javac-native|virtual/javac-native discussion]] for details.<br />
<br />
=== Ant ===<br />
Ant is an often used tool in the Java world. Even OpenJDK uses it. Unfortunately it is also a complex beast with many dependencies (many of which use Ant itself). Despite all this troubles Ant (1.7.1) is available and supported as an application which can be run from build recipes.<br />
<br />
=A word of warning=<br />
Every so often people on the net suggest that in order to get Java stuff running in OpenEmbedded, you need to install a JDK, Kaffe or Jikes and then make modifications to the PATH variable in order to allow the<br />
build use the runtime or compiler. '''These suggestions are wrong!''' The Java support in OpenEmbedded is (and strives to stay) ''completely'' self-hosting. You should not need a single bit of Java on your host OS to get the Java recipes to compile.<br />
<br />
On the other hand the Java support in OE can happily co-exist with whatever 'java', 'javac' and other tools you might have installed in your OS. Due to the nature of some configure scripts, those will sometimes find these executables but in the end only the tools from OpenEmbedded's staging directory will be used (if not its a bug that needs to be fixed).<br />
<br />
Please note that problem reports that are caused by pulling in native Java tools (those from your OS) into the OpenEmbedded build process will be closed as invalid. The reason is that the recipes are only supposed to work with the built-in toolchain.<br />
<br />
=Configuring (add info about what and where)=<br />
In this section you learn about the things you can set up. In many OpenEmbedded-based distributions some or most of these decision may have already been made for you so there is no need to specify them. However in case you want to provide the Java support in your distribution you need to know which knobs are available.<br />
<br />
==Bootstrap process==<br />
As told in the toolchain support section the whole Java support in OpenEmbedded is self-hosting. This mean you do not need to have any bit of Java on your build machine as OpenEmbedded will build this itself.<br />
<br />
This bootstrap process contains the following steps: At first jikes-native is compiled which is a Java 1.4-capable compiler that does not need a runtime or (strictly) a class library to work. With this compiler we compile the initial runtime (package virtual/java-initial).<br />
<br />
virtual/java-initial is a preliminary runtime. This virtual package is currently provided by cacao-initial or jamvm-initial. After that ecj-initial is built. At that point we have a 1.5-capable compiler running on a Java 1.4 compatible VM.<br />
<br />
The compiler is then used to build virtual/java-native and finally virtual/javac-native. The former virtual package is provided by either cacao-native or jamvm-native. The latter package is currently only provided through ecj-bootstrap-native. Having built these packages provides the OpenEmbedded build environment with a Java5-capable compiler and runtime. At that point we are ready to compile any other Java package.<br />
<br />
==Bootstrap virtual machine aka virtual/java-initial==<br />
The bootstrap virtual machine has the sole purpose of running ecj-initial (the bootstrap compiler) to compile a 1.5-capable runtime and library. The bootstrap VM runs on your build host and is therefore a -native package. Inside the native staging directory the VM provides a 'java-initial' executable.<br />
<br />
As told above there are currently two packages that provide 'virtual/java-native'. Add<br />
<br />
PREFERRED_PROVIDER_virtual/java-initial = "cacao-initial"<br />
PREFERRED_VERSION_cacao-initial = "0.98"<br />
<br />
to your local or site configuration to choose the Cacao VM. This virtual machine has a JIT compiler and is generally faster but takes a bit longer to compile. Furthermore this VM is only tested to work correctly on X86 build hosts. If you chose Cacao there will also be a 'cacao-initial' binary in your native staging directory.<br />
<br />
'''Note:''' There is a problem with Cacao 0.98 running on recent distributions where mmaping the zero page is not allowed. Chose jamvm-initial (see below) if you do not want to change the vm_mmap_min_adr restriction on your system.<br />
<br />
In case Cacao is unsuitable for you add<br />
<br />
PREFERRED_PROVIDER_virtual/java-initial = "jamvm-initial"<br />
PREFERRED_VERSION_jamvm-initial = "1.4.5"<br />
<br />
to your configuration. JamVM is an interpreting Java virtual machine. Despite interpreting only it is very fast (implements many modern interpreter techniques) and compiles quickly. Furthermore it is known to work on X86 and PowerPC build hosts.<br />
<br />
==Native virtual machine aka virtual/java-native==<br />
As for virtual/java-initial this virtual package provides a Java virtual machine which runs on your build host. Its purpose is to run any Java programs that are needed during your build process. The most prominent program that it is supposed to run is the compiler ECJ. The virtual/java-native package provides a 'java' binary inside the native staging directory. At the moment you can chose between two runtimes: Cacao and JamVM.<br />
<br />
As for the general features it is the same as for java-initial. However for virtual/java-native later versions of the VMs are used so stability and platform support is better. For instance you can use cacao-native on PowerPC as well since the version of Cacao used properly supports it.<br />
<br />
To chose Cacao add the following line to your configuration:<br />
<br />
PREFERRED_PROVIDER_virtual/java-native = "cacao-native"<br />
<br />
Besides 'java' cacao-native install a 'cacao' binary into the native staging directory.<br />
<br />
If you favor JamVM (or are having trouble with Cacao) use:<br />
<br />
PREFERRED_PROVIDER_virtual/java-native = "jamvm-native"<br />
<br />
There will also be a 'jamvm' binary in native staging directory besides the 'java' one with jamvm-native.<br />
<br />
'''Note:''' Native versions of jamvm are unsupported on amd64/x86_64 hosts since OpenEmbedded lacks a native libffi. If you desperately need jamvm on your platform consider installing the development package for libffi of your distro.<br />
<br />
== Native Java compiler aka virtual/javac-native ==<br />
The virtual/javac-native package provides the 'javac' binary which is to be found within the native staging directory. This compiler is used to build all of the Java packages within OpenEmbedded. <br />
<br />
There are two recipes which provide this functionality: <br />
<br />
ecj-bootstrap-native uses the commandline variant of the Eclipse IDE's integrated compiler. In order to use that compiler add the following to your configuration:<br />
<br />
PREFERRED_PROVIDER_virtual/javac-native = "ecj-bootstrap-native"<br />
<br />
The second option is OpenJDK's Java compiler which is the F/OSS variant of good old 'javac'. If you experience trouble with ecj you should try OpenJDK's<br />
Java compiler by setting the following in your configuration:<br />
<br />
PREFERRED_PROVIDER_virtual/javac-native = "openjdk-javac-native"<br />
<br />
<br />
'''Note:''' OpenJDK's javac is actually build in the package openjdk-language-tools-native (provides a 'sun-javac' binary). The reason for this is to allow 'ecj-bootstrap-native' and 'openjdk-language-tools-native' to coexist in the staging dir.<br />
<br />
=== ecj-bootstrap-native, ecj-initial and libecj-bootstrap ===<br />
Since ecj-initial and ecj-bootstrap-native use the same jar file the compilation step for both packages is done through in the libecj-bootstrap recipe. Therefore in order to decide which ECJ version to use for compilation you need to set a version preference for that recipe:<br />
<br />
PREFERRED_VERSION_libecj-bootstrap = "3.4"<br />
<br />
== Target virtual machine ==<br />
'''Note:''' There used to be a virtual/java package. It turned out that by having this it prevented offering multiple J2SE-compatible VMs for the target device.<br />
<br />
From a distributors point of view you can build the jamvm, cacao, phoneme or openjdk recipes and provide them to your users. Those can then either install the packages directly by its name or rely<br />
on a chosing of the packaging.<br />
<br />
At the moment Cacao and JamVM are supported runtimes. Cacao is ready for x86, PowerPC and ARM systems (others are untested and AVR32 is not suppported) and has a JIT compiler. JamVM can be used on x86, PowerPC, ARM and MIPS. PhoneME Advanced should support x86, PowerPC, ARM, MIPS and Sparc.<br />
<br />
Additionally OpenJDK can be built using either Cacao (same properties as above) or the Zero port of Hotspot. Zero is an C++-based interpreter capable of running on any platform that is supported by libffi.<br />
<br />
When installed all J2SE runtimes provide the 'java' executable (chosen through update-alternatives). PhoneME Advanced gives you a 'java-cdc' executable.<br />
<br />
=== Runtime provider ===<br />
'''Warning:''' When we talk of 'runtime provider' here this is meant in the OpenEmbedded sense (PROVIDES = build provides, RPROVIDES = runtime provides)<br />
The Cacao, JamVM or OpenJDK packages are set to provide 'java2-runtime'. Packages which need a J2SE-capable VM should RDEPEND on this. By inheriting the 'java-library' class in your recipe this is done automatically.<br />
<br />
PhoneME on the other hand is set to provide 'java-cdc-runtime'.<br />
<br />
== GNU Classpath for headless machines aka classpath-minimal ==<br />
Through setting the provider for 'classpath' you can decide whether you build a full class library with support for AWT/Swing (having a gtk+ dependency) or a variant that works without that and is primarily meant for headless devices. It might also be handy if you decide not to use AWT/Swing and use SWT instead. To chose the minimal variant add this to your configuration:<br />
<br />
PREFERRED_PROVIDER_classpath = "classpath-minimal"<br />
<br />
Otherwise you need to add this line:<br />
<br />
PREFERRED_PROVIDER_classpath = "classpath"<br />
<br />
Currently the Angstrom distribution does not set a preference and you have to provide your own.<br />
<br />
=Writing a Java recipe=<br />
This section is going to tell you, how to write a proper recipe to build a Java library or program.<br />
<br />
'''At the moment this is a stub and you will only find some scattered information which at a later point will be merged into a consistent whole.'''<br />
<br />
==java-native.bbclass==<br />
If you use the ''java-library'' bbclass in a recipe ''foo'' and generate a native variant (e.g. ''foo-native'') you should use<br />
<br />
inherit java-native<br />
<br />
instead of ''native''. By doing so, you make sure, that any jars created by the recipe are properly installed into staging.<br />
<br />
==ant-native==<br />
If you need Ant to build your recipe add ''ant-native'' to your recipes dependencies. This will allow you to call the built-in Ant executable.<br />
<br />
= Information on specific libraries =<br />
== swt3.4-gtk and swt3.4-gtk-hildon ==<br />
Some effort has been done to integrate Gtk+-based SWT 3.4 into the Hildon environment (that is what Maemo provides). Distributions targeting Maemo should set the preferred provider for swt3.4-gtk like this:<br />
<br />
PREFERRED_PROVIDER_swt3.4-gtk = "swt3.4-gtk-hildon"<br />
<br />
''Important'': If you do not want the hildon variant it is best to declare<br />
<br />
PREFERRED_PROVIDER_swt3.4-gtk = "swt3.4-gtk"<br />
<br />
as well. So bitbake will not chose the wrong one by accident (which would otherwise pull in all kinds of unwanted dependencies).<br />
<br />
= Caveats, known issues, hints, miscellaneous information =<br />
== Version suggestions ==<br />
Everyone and his dog knows that combining glibc 2.8, gcc 2.95 and Linux kernel 2.6.26 is not going to work. In the GNU Classpath realm we also have a set of versions that do not fit together. Here are some suggestions for your PREFERRED_VERSIONs. Stick to these if you are unsure. You can always find out which version are ''supposed'' to be compatible by reading the READMEs of the VMs.<br />
<br />
=== jamvm-initial and classpath-initial ===<br />
Use this and nothing else:<br />
<br />
PREFERRED_VERSION_jamvm-initial = "1.4.5"<br />
PREFERRED_VERSION_classpath-initial = "0.93"<br />
<br />
=== cacao-initial and classpath-initial ===<br />
Use this and nothing else:<br />
<br />
PREFERRED_VERSION_cacao-initial = "0.98"<br />
PREFERRED_VERSION_classpath-initial = "0.93"<br />
<br />
=== jamvm[-native] and classpath[-native] ===<br />
These are the releases that appear to be stable.<br />
<br />
PREFERRED_VERSION_jamvm-native = "1.5.3"<br />
PREFERRED_VERSION_classpath-native = "0.98"<br />
<br />
For the target device:<br />
<br />
PREFERRED_VERSION_jamvm = "1.5.2"<br />
PREFERRED_VERSION_classpath = "0.98"<br />
<br />
=== cacao[-native] and classpath[-native] ===<br />
These releases appear to be stable:<br />
<br />
PREFERRED_VERSION_cacao-native = "0.99.3"<br />
PREFERRED_VERSION_classpath-native = "0.97.2"<br />
<br />
For the target device take these:<br />
<br />
PREFERRED_VERSION_cacao = "0.99.4"<br />
PREFERRED_VERSION_classpath = "0.98"<br />
<br />
== Extra binaries and symlinks ==<br />
Since both Cacao and JamVM can be installed in staging you can use this and modify the 'java' or 'java-initial' symlink if you want to switch to a certain VM.<br />
<br />
== Debugging Cacao on the target ==<br />
You need to debug the Cacao JVM on your target device using GDB and need some pointers on how to get started? Read [https://wiki.evolvis.org/jalimo/index.php/CacaoDebugging this] page from the Jalimo Wiki.<br />
<br />
=Future plans =<br />
==Default Bytecode compliance level==<br />
Soon an option will be introduced to set the default bytecode compliance level. For any Java package that does not explicitly provide this level (not many do this) the one you set in your configuration will be used.<br />
<br />
==OpenJDK + Cacao==<br />
The flexibility of the Cacao runtime allows it to run it with OpenJDK's class library. This allows you to use the official class library and a JIT-capable runtime on an ARM device (as of today Hotspot has no JIT on ARM).<br />
<br />
Since the middle of August 2008 OpenJDK + Cacao can be build and is included in the Debian armel sid repositories (package cacao-oj6-sdk). Xerxes Rånby is showing some webbapplets running using OpenJDK + CACAO on his blog: http://labb.zafena.se/?p=1<br />
<br />
Since December 2008 OpenJDK + Cacao can be crosscompiled with OpenEmbedded as demonstrated by Robert Schuster!<br />
Check out http://rschuster.blogs.evolvis.org/2008/12/21/serving-cross-compiled-openjdk-with-icedtea/ and the answers http://rschuster.blogs.evolvis.org/2008/12/23/comments-on-latest-post-on-openjdk/<br />
<br />
==Ant integration for build recipes==<br />
Although ''ant'' can be used as a standalone tool there is no direct support for it in the recipe. E.g. the Debian buildsystem (CDBS) has support classes that can be used for Ant-based Java sourcepackages. It would be nice to have this too for OpenEmbedded.<br />
<br />
= FAQ =<br />
This space is for *your* questions and those that appeared more often on the mailing list. Things will be added here by the Jalimo folk/OE-Java maintainers or by you asking a question.<br />
<br />
== Q: I do get all these editions, configurations and profiles that exist in the Java world wrong. Any pointer on this? ==<br />
I found these articles in Wikipedia helpful to clarify the situation [http://en.wikipedia.org/wiki/Java_platform Java platform], [http://en.wikipedia.org/wiki/Java_ME Java ME].<br />
<br />
== Q: I need to solve a specific Java problem in OE and want to throw money at this. Whom can I contact? ==<br />
The [http://jalimo.org Jalimo] project has done a lot of Java work in OE and are available for contract work. You can also ask for experienced devs on the openembedded-devel mailing list.<br />
<br />
<br />
<br />
[[Category:FAQ]]<br />
[[Category:Software Components]]<br />
[[Category:Java]]</div>Woglindehttp://www.openembedded.org/index.php?title=LinuxTag&diff=4223LinuxTag2011-04-18T12:18:49Z<p>Woglinde: </p>
<hr />
<div>== LinuxTag 2011 ==<br />
* takes place in Berlin, Germany<br />
* May 11th to 14th 2011<br />
* LinuxTag is Germany's biggest F/OSS event<br />
* Berlin is supercool and quite cheap<br />
<br />
== Manning ==<br />
You are going to LinuxTag and can spend some time at the OpenEmbedded stand to explain interested individuals the virtues of OpenEmbedded? Add your name and on which day you'll be available.<br />
<br />
* Florian Boor<br />
* Robert Schuster (remains to be decided by employer)<br />
* Henning Heinold (occassionally, can jump in so that other people can take a break)<br />
* <your name here><br />
<br />
== Yocto/oe-core ==<br />
<br />
* be informed of what will come<br />
* oe-core/layers bsp's<br />
<br />
== Booth support material ==<br />
* power extensions and converters<br />
* TFT screen<br />
* transport box<br />
* SD cards and reader<br />
* WIFI AP in managed mode (provide wired network to embedded devices)<br />
<br />
== Marketing material ==<br />
* Flyer availability?<br />
* Poster availability?<br />
- Poster needs to be updated<br />
- where are poster sources?<br />
* embedded devices to show (+ what is running on them)<br />
-<br />
-<br />
-<br />
* booth presentation slideshow<br />
- Robert Schuster made one for CeBIT, will update it and bring it to the event<br />
* OE booth demo image</div>Woglindehttp://www.openembedded.org/index.php?title=CeBIT_2011&diff=4109CeBIT 20112011-03-01T12:30:24Z<p>Woglinde: /* OpenEmbedded booth */</p>
<hr />
<div>= OpenEmbedded booth =<br />
== Visit us ==<br />
Hall 2, Booth F44<br />
<br />
== Manning ==<br />
You are going to CeBIT 2011 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<br />
* Mickey Lauer<br />
* Henning Heinold (3.3-5.3, only parttime, mainly on the navit booth)<br />
<br />
== Devices ==<br />
<br />
== Flyers and posters ==<br />
* Robert Schuster: ~500 OpenEmbedded flyers (will be sent from Florian to tarent office in Bonn)<br />
<br />
== Free Tickets ==<br />
<br />
CeBIT organizers provided us with lots of free tickets for the event. If you want one leave your name and email here (don't forget to obfuscate the later a bit).</div>Woglindehttp://www.openembedded.org/index.php?title=CeBIT_2011&diff=4071CeBIT 20112011-02-18T10:34:00Z<p>Woglinde: /* Manning */</p>
<hr />
<div>= OpenEmbedded booth =<br />
== Manning ==<br />
You are going to CeBIT 2011 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<br />
* Mickey Lauer<br />
* Henning Heinold (3.3-5.3, only parttime, mainly on the navit booth)<br />
<br />
== Devices ==<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 />
== Free Tickets ==<br />
<br />
CeBIT organizers provided us with lots of free tickets for the event. If you want one leave your name and email here (don't forget to obfuscate the later a bit).</div>Woglindehttp://www.openembedded.org/index.php?title=Required_software&diff=2385Required software2010-07-14T14:09:03Z<p>Woglinde: /* OpenEmbedded's Software Requirements */</p>
<hr />
<div>= OpenEmbedded's Software Requirements =<br />
<br />
This page is the reference of what software is needed. But [[OEandYourDistro]] is likely much faster in getting you that software actually installed.<br />
<br />
To use the OE build system the following software is required on your system:<br />
* [http://www.python.org/ Python] (Version 2.5.0 or 2.6.x for latest development version of bitbake)<br />
** Note that you may also need certain development files for Python e.g. for bitbake's setup.py to work. Depending on the distribution you use you may want to look for a package called "python-dev", "python-devel", or similar.<br />
* [http://www.gnu.org/software/patch/patch.html GNU Patch] (Version 2.5.9 or later, see ftp://alpha.gnu.org/gnu/diffutils/ . It is a "testing release" and is not mirrored on the GNU mirrors.)<br />
* [http://www.gnu.org/software/m4/m4.html GNU m4]<br />
* [http://www.gnu.org/software/make/ GNU make] (Version 3.80 or later for hh.org kernels)<br />
* [http://psyco.sourceforge.net/ Psyco JIT Compiler] is recommended to increase performance (32bit only)<br />
* [http://www.perl.org/ perl] (needs newer than 5.0, how much newer? probably at least 5.6.2)<br />
* [http://invisible-island.net/diffstat/diffstat.html diffstat]<br />
* [http://developer.berlios.de/projects/bitbake bitbake]<br />
<br />
== Tools to download source files ==<br />
* wget <br />
* curl <br />
* ftp<br />
* [http://www.nongnu.org/cvs/ cvs]<br />
* [http://subversion.tigris.org/ subversion]<br />
* [http://git.or.cz/index.html git]<br />
<br />
== Tools to verify integrity of the downloaded sources ==<br />
* md5sum<br />
* sha256sum<br />
<br />
== Tools to unpack sources ==<br />
* tar<br />
* bzip2<br />
* gzip<br />
* unzip<br />
<br />
== Tools to build the various *-doc packages==<br />
* [http://www.jclark.com/jade/ Jade] or [http://www.netfolder.com/DSSSL/ OpenJade]<br />
** I don't know which of these is preferred<br />
* [http://sourceforge.net/projects/docbook/ Docbook] DTDs and DSSSL stylesheets<br />
* [http://sgmltools-lite.sourceforge.net/ sgmltools], called "sgmltools-lite" too<br />
* [http://sources.redhat.com/docbook-tools/ docbook-utils]<br />
** docbook-utils download is hard to find; look in ftp://sources.redhat.com/pub/docbook-tools/new-trials/SOURCES<br />
* [ftp://ftp.gnu.org/pub/gnu/texinfo/ Texinfo]<br />
* [http://www.nongnu.org/texi2html/ texi2html] (Perl script that converts Texinfo to HTML)<br />
<br />
== Other packages ==<br />
* [http://www.gnu.org/software/sed/sed.html GNU sed] 4.x<br />
* [http://www.gnu.org/software/bison/bison.html Bison]<br />
* bc (binary calculator), if you want to build a Zaurus 2.4 or any of the collie kernels<br />
* glibc headers (libc6-dev in Debian, glibc-devel in RPM based (in PLD also glibc-static is needed))<br />
* [http://www.pcre.org/ pcre headers] (Perl 5 Compatible Regular Expression Library, required for e.g. konqueror-embedded)<br />
* SDL headers to build qemu-native (apt-get install libsdl1.2-dev under Ubuntu/Debian)<br />
* [http://www.mktemp.org/mktemp/ mktemp] (required by quilt and used in some package patches)<br />
* help2man - Create simple man pages from --help output<br />
<br />
There is an ongoing effort to accurately document the required software within the OpenEmbedded and ultimately, this will be reflected in the ASSUME_PROVIDED variable.<br />
<br />
[[Category:User]]</div>Woglinde