https://www.openembedded.org/api.php?action=feedcontributions&user=Laibsch&feedformat=atomOpenembedded.org - User contributions [en]2024-03-19T01:02:41ZUser contributionsMediaWiki 1.29.0https://www.openembedded.org/index.php?title=Category_talk:FAQ&diff=2276Category talk:FAQ2010-04-07T12:48:25Z<p>Laibsch: restoring last good version</p>
<hr />
<div>= Old Wiki Faq =<br />
<br />
<br />
The old wiki installation seems to have eaten the FAQ page. Let's try to restore some of the information from [http://web.archive.org/web/20070222090436/www.openembedded.org/node/28/edit web.archive.org], this will need to be compared with [http://74.125.39.104/search?q=cache%3Aoe.linuxtogo.org%2Fnode%2F28%2Fdiff%2F1140&ie=utf-8&oe=utf-8&aq=t&rls=com.ubuntu:en-US:unofficial&client=firefox-a the last known-good version] from google (mark all text on that page to make it visible). Content still to be moved follows<br />
<br />
--[[User:Laibsch|Laibsch]] 23:08, 4 June 2008 (UTC)<br />
<br />
= Development =<br />
<br />
== 1. what does OpenEmbedded keyword X do? ==<br />
Check out the documentation in the following file: http://www.openembedded.org/repo/org.openembedded.dev/conf/documentation.conf<br />
<br />
== 2. How can I make bitbake to use a specific version of <tool>? ==<br />
See [http://www.openembedded.org/search/node/PREFERRED_VERSION PREFERRED_VERSION]<br />
<br />
== 3. How can I make bitbake use proxychains when doing cvs operations? ==<br />
See [http://www.openembedded.org/search/node/FETCH_COMMAND FETCH_COMMAND] and [http://www.openembedded.org/search/node/UPDATE_COMMAND UPDATE_COMMAND]<br />
<br />
== 4. What is the easiest way to convert Debian ARM packages to ipkg's (if size doesn't matter)? ==<br />
mv foo.deb foo.ipk<br />
<br />
== 5. How do I add a package to OE? ==<br />
Most of the time adding a package to OE will not be as easy as 1-2-3. Many software developers do not cross-compile their packages and are generally unaware of [[Users Manual/Rules Of Thumb|good design decisions]] that facilitate or break cross-compilation.<br />
<br />
== 6. How can I do a recursive make? ==<br />
<br />
Implement a structure along the following lines.<br />
<br />
do_compile {<br />
for i in dir; oe_runmake ...; done<br />
}<br />
<br />
== 7. How do I set a variable according to the kernel version of the package being built? ==<br />
<br />
Use base_conditional in the following manner:<br />
<br />
CFLAGS_append = '${@base_conditional("KERNEL_MAJOR_VERSION", "2.6", " -D__Linux26__ ", " -D__Linux24__ ",d)}'<br />
<br />
In the example above ''-D__Linux26__'' will be added to the existing CFLAGS if the kernel is 2.6 and ''-D__Linux24__'' if the kernel is 2.4<br />
<br />
<br />
== 8. What is ARM EABI and how do I use it? ==<br />
ARM EABI is the informal name for the ABI for the ARM Architecture standard developed by ARM Ltd and others. This standard explains how tools should generate object and excecutable files.<br />
* http://www.codesourcery.com/gnu_toolchains/arm/faq.html#q_gnu_linux_long_long<br />
* http://www.arm.com/products/DevTools/ABI.html<br />
* http://wiki.debian.org/ArmEabiPort<br />
<br />
To instruct OE to build EABI parts, you typically need the following in your distro conf file:<br />
TARGET_OS=-gnueabi<br />
See the Angstrom distro for an example: http://www.openembedded.org/repo/org.openembedded.dev/conf/distro/angstrom.conf<br />
http://www.openembedded.org/repo/org.openembedded.dev/conf/distro/angstrom-2006.9.conf<br />
<br />
You also need to make sure your kernel has the needed support. From the codesourcery faq, you need the following:<br />
* CONFIG_EABI must be enabled<br />
* Kernel must include support for NPTL<br />
* kernel versions earlier than 2.6.17 should be avoided<br />
<br />
== 9. What is NPTL and how do I use it in OE? ==<br />
NPTL is the Native POSIX Thread Library which is a software feature that enables the Linux kernel to run programs written to use POSIX Threads very efficiently. It is meant to replace an older implementation named Linuxthreads.<br />
* [http://en.wikipedia.org/wiki/LinuxThreads]<br />
* [http://en.wikipedia.org/wiki/Native_POSIX_Thread_Library]<br />
* to check what threading library you have, run the following command: getconf GNU_LIBPTHREAD_VERSION. You can also type: <br />
/lib/libc.so.6 to get information on what threading lib is used.<br />
<br />
There are two options for threading (from pb email):<br />
* With linuxthreads, you need glibc-initial, then gcc-cross-initial,<br />
then glibc, then gcc-cross.<br />
* With nptl, you need glibc-initial, then gcc-cross-initial, then<br />
glibc-intermediate, then gcc-cross, then glibc.<br />
<br />
To use linuxthreads, you need something like the following:<br />
PREFERRED_PROVIDER_virtual/${TARGET_PREFIX}libc-for-gcc = glibc<br />
<br />
For NPTL, this becomes:<br />
PREFERRED_PROVIDER_virtual/${TARGET_PREFIX}libc-for-gcc = glibc-intermediate<br />
<br />
<br />
== 10. How do I apply for read-write status to the OpenEmbedded monotone repo? ==<br />
<br />
Hang around IRC in #oe, use the dev mailing list or some other way to get in [http://www.openembedded.org/contact contact] with the OE devs. Explain to them why you think you should be given rw access. If your request is granted, [http://www.openembedded.org/wiki/MonotonePhraseBook create your key and send it to the maintainers].<br />
<br />
== 11. How do I add additional packages to a bootstrap-image generated image? ==<br />
<br />
You can add packages to your build by setting the MACHINE_EXTRA_RDEPENDS or DISTRO_EXTRA_RDEPENDS in a conf file. Note, you must rebuild task-base after changing these variables (bitbake task-base -crebuild) as bitbake has no way of knowing task-base has changed. See [http://bec-systems.com/web/content/view/59/9/] for a more detailed explanation. <br />
<br />
== 12. What order are conf files parsed for variable assignment? ==<br />
See oe/conf/bitbake.conf. There should be a section that looks something like:<br />
<br />
<pre><br />
include conf/site.conf<br />
include conf/auto.conf<br />
include conf/local.conf<br />
include conf/build/${BUILD_SYS}.conf<br />
include conf/target/${TARGET_SYS}.conf<br />
include conf/machine/${MACHINE}.conf<br />
include conf/distro/${DISTRO}.conf<br />
include conf/documentation.conf<br />
require conf/sanity.conf<br />
</pre><br />
<br />
A straight "=" assignment in a machine or distro conf file will overwrite a local.conf setting. Therefore, machine and distro conf files should use the "+=" assignment if it is useful for local.conf to be able to append to a variable.<br />
<br />
= Build Errors =<br />
== 1. chown error during do_install process ==<br />
As the OE build process runs a normal using, any install process that changes file ownership or groups must be run using fakeroot. This typically involves the following change in the recipe bb file:<br />
<pre><nowiki><br />
fakeroot do_install () {<br />
oe_runmake "DSTROOT=${D}" install<br />
}<br />
</nowiki></pre><br />
<br />
== 2. Error: autoreconf2.50: unrecognized option --exclude=libtoolize ==<br />
For some reason the base system's autoreconf is being used instead of the OE version (from autoconf-native)<br />
<br />
For me personally this was a problem with my BBPATH having the paths to two branches in it org.openembedded.oz354x and org.openembedded.dev. Removing the one i wasn't trying to build, remove the tmp dir and start bitbake over fixed it.<br />
<br />
== 3. Error: Building libtool-native dies with "configure: error: source directory already configured; run "make distclean" there first" ==<br />
Your build dir path has one or more symlinks in it. Don't do that!<br />
<br />
== 4. Error: run.do_patchcleancmd.4326: line 442: syntax error near unexpected token `'INHIBIT_PACKAGE_STRIP','` ==<br />
known bug -- see: http://bugs.openembedded.org/Ticket/Display.html?id=257 There are several workarounds:<br />
** inherit package in the offending bb files<br />
** set INHERIT += "package_ipk debian" in your distro or local.conf file<br />
<br />
== 5. I updated OE.db and now my builds are failing during the glibc compile, complaining about bad symbol definitions. What's wrong? ==<br />
<br />
As of this writing, the version of glibc in the .dev branch of OE calls for a version of binutils it really shouldn't use. A patch has been applied to some DISTRO .confs which forces the "correct" version of binutils (<2.17) for the moment. But if the DISTRO .conf file you're building with isn't patched, a workaround is to add the following line to your local.conf file:<br />
<br />
PREFERRED_VERSION_binutils-cross = "2.16"<br />
<br />
then reset the glibc build with<br />
<br />
bitbake glibc -c clean<br />
<br />
and start from where you left off.<br />
<br />
== 6. My build dies during the qemu-native section. What gives? ==<br />
If the error is:<br />
| ERROR: QEMU requires SDL or Cocoa for graphical output<br />
| To build QEMU without graphical output configure with --disable-gfx-check <br />
| Note that this will disable all output from the virtual graphics card.<br />
| FATAL: oe_runconf failed<br />
Then install SDL headers (apt-get install libsdl1.2-dev under Ubuntu/Debian).<br />
<br />
Else another workaround: Install qemu from the distribution for your development computer, and include <br />
ASSUME_PROVIDED +="qemu-native"<br />
in your local.conf file.<br />
<br />
== 7. Bitbake tells me to "Please set TARGET_OS directly, or choose a MACHINE or DISTRO that does so.", but my local.conf file already does. ==<br />
<br />
Be sure you are not running bitbake as root. Doing so breaks Bitbake's use of chroot.<br />
<br />
== 8. qemu crashes during generation of binary locales ==<br />
<br />
Set ENABLE_BINARY_LOCALE_GENERATION = "0" in your local.conf. This is probably a x86_64 issue.<br />
<br />
== 9. sanity checker complains "/proc/sys/vm/mmap_min_addr is not 0" on Ubuntu ==<br />
<br />
Ubuntu Hardy Heron has this value set to 65536 by default. <br />
see /etc/sysctl.conf content below<br />
<pre><nowiki><br />
# protect bottom 64k of memory from mmap to prevent NULL-dereference<br />
# attacks against potential future kernel security vulnerabilities.<br />
# (Added in kernel 2.6.23.)<br />
vm.mmap_min_addr = 65536<br />
</nowiki></pre><br />
<br />
Since Wine suffers from the same feature, a temporary and permenant fix <br />
is already known. <br />
See this link (duh!) : http://wiki.winehq.org/PreloaderPageZeroProblem<br />
<br />
Q: Why is this necessary? I'm using debian, and mmap_min_addr is 4096, but I run qemu all the time, and it seems to work fine.<br />
<br />
= Debugging OE Builds =<br />
OE is not perfect. Due to the size, complexity, rapid pace of development, and lack of maintainers, you will often be presented with an opportunity to debug OE builds :). Fortunately, OE is easy to debug once you know a few tricks:<br />
<br />
== 1. Debugging tips ==<br />
* learn to use interactive bitbake (`bitbake -i`)<br />
* The [[BitBake]] `--verbose` option will print package dependencies. This is very useful when trying to determine why a package is being built.<br />
* The [[BitBake]] `-D` option will increase debugging level. Note `-D -D` is also a valid option and can be used to determine what conf files are being used -- look for lines begining with conf.<br />
<br />
== 2. How do I re-build a failing package? ==<br />
There are several options:<br />
* `bitbake -b <path to bb file>`<br />
* `bitbake <package name>`<br />
* start bitbake interactive mode (`bitbake -i`) and then run `build <package name>`<br />
<br />
== 3. How do I clean a package? ==<br />
There are several options:<br />
* `bitbake -b <path to bb file> -c clean`<br />
* `bitbake <package name> -c clean`<br />
* start bitbake interactive mode (`bitbake -i`) and then run `clean <package name>`<br />
You may also put several package names after the command e.g.<br />
* `bitbake -c clean pack1 pack2 ...`<br />
Sometimes you want to clean a particular package version from your build/tmp/work directory. In this case use<br />
* for example `bitbake -c clean gcc-cross-initial-4.1.1`<br />
Note: You have to use the package directory name here from your work directory without the trailing `-rx`. That means there is not an underscore before the package version but a simple dash.<br />
The above is quite useful if you want to clean up a work directory from unwanted versions of the same package.<br />
<br />
The ipk file in the directory deploy/ipk is not deleted when you perform a clean on a certain package. So make sure you manually rebuild the cleaned package in order to get an updated ipk or delete the ipk prior to a build.<br />
<br />
== 4. What tasks are available for a package/recipe? ==<br />
Building an OE package consists of a number of tasks. These tasks can be listed with the OE listtasks task. Each task can be run individually.<br />
<br />
Example:<br />
<br />
<pre><br />
bitbake -b <path to bb file> -c listtasks<br />
NOTE: package matchbox-0.9.1: started<br />
NOTE: package matchbox-0.9.1-r0: task do_listtasks: started<br />
do_listtasks<br />
do_compile<br />
do_stage<br />
do_build<br />
do_mrproper<br />
do_fetch<br />
do_configure<br />
do_clean<br />
do_emit_manifest<br />
do_populate_staging<br />
do_package<br />
do_unpack<br />
do_install<br />
do_showdata<br />
do_patch<br />
NOTE: package matchbox-0.9.1-r0: task do_listtasks: completed<br />
NOTE: package matchbox-0.9.1: completed<br />
Build statistics:<br />
Attempted builds: 1<br />
</pre><br />
<br />
== 5. How do I view the value of OE variables for a package? ==<br />
* Use the [[BitBake]] command. <br />
** `bitbake -e ../openembedded/recipes/meta/bootstrap-image.bb`<br />
** `bitbake -e <package name>`<br />
* Use the [[OpenEmbedded]] showdata command. Ex: `bitbake -b ../openembedded/recipes/meta/bootstrap-image.bb -c showdata`<br />
<br />
== 6. How do I unpack ipk files? ==<br />
ipk package files can be unpackaged with the `ar` command. Ex: `ar x <path to ipk file>` You can also inspect the files inside an ipk and get other information with the dpkg command if your distribution has it.</div>Laibschhttps://www.openembedded.org/index.php?title=Web_Site_Infrastructure_Discussion&diff=2275Web Site Infrastructure Discussion2010-04-07T12:45:12Z<p>Laibsch: Reverted edits by 212.235.107.153 (Talk); changed back to last version by Laibsch</p>
<hr />
<div>Discussion about using a project management tool like Redmine. Would likely replace bugzilla, and some wiki functionality. It seems likely the main OE web site would remain in mediawiki.<br />
<br />
= Redmine =<br />
<br />
== Benefits/Losses ==<br />
<br />
* '''Benefits'''<br />
** easy to automatically reference issues from commits: refs #123<br />
** easy to close issues from commits: closes #123<br />
** everything is in one place, milestones, tickets, wiki, and it is easy to cross reference everything. With everything in one place, it is more likely that all the tools will get used.<br />
** one place to look for all project activity, Issue changes, wiki edits, source code changes, etc<br />
** very good multiple project support<br />
** additional features such as news, roadmap, etc.<br />
* '''Losses'''<br />
** Redmine does not have a concept of workflow in tickets (not sure we use this anyway)<br />
** what to do with the wiki? With two wikis, it is very clumsy to have stuff in two places.<br />
** spam protection, security. Mediawiki and bugzilla are robust apps. Redmine is relatively new.<br />
** bug linking, example: http://bugs.openembedded.net/show_bug.cgi?id=3591<br />
* '''To think about'''<br />
** Redmine is geared toward "projects" where everyone is working toward the same goal. OSS projects typically involve a lot of people with different goals. Would there be any benefit to integration?<br />
** would roadmap planning help us set goals for the next release and get more people working toward common goals? As OE is combination of many things, I'm not sure this is applicable.<br />
<br />
== IRC Discussion ==<br />
That started this.<br />
<br />
<pre><br />
07:21 < zecke> cbrake: do you use the accounting part of it?<br />
07:21 < otavio> accounting of what?<br />
07:21 < cbrake> zecke: I use the time estimation part, percent done, but I don't log time on task.<br />
07:22 < otavio> ah<br />
07:22 < cbrake> zecke: my needs are primarialy to estimate remaining work on a project.<br />
07:22 < otavio> cbrake: same here<br />
07:22 < otavio> cbrake: we don't use the time planning<br />
07:22 < otavio> cbrake: but few internal projects, when we hire external consultants, we use<br />
07:23 < zecke> cbrake: yes, that is good enough. Do you manage to update this information? Or, is your busines context forcing you to update it anyway?<br />
07:23 < cbrake> zecke: the Gantt chart stuff is pretty elementary, but is still fairly useful for mapping out tasks on a weekly basis<br />
07:24 < cbrake> zecke: not sure I understand your question<br />
07:25 < zecke> cbrake: The issue most of the time is updating the information once the project is going<br />
07:25 < zecke> cbrake: combining this with the fact that humans are lazy, most projects I know stop the book keeping... so how easy is it to keep the<br />
information up to date?<br />
07:26 < cbrake> zecke: yes thats a problem to keep up to date, and I'm as lazy as the next :-)<br />
07:26 < cbrake> zecke: but redmine is the least painful method I've found so far -- UI is excellent. Even small things like back arrow is truely back<br />
instead of the last for change, etc.<br />
07:27 < cbrake> zecke: I do other things that help me like record every commit in a ticket (redmine can do some of this automatically), but it forces me to<br />
look at tickets often, and keep everything up to date.<br />
07:28 < cbrake> zecke: that is probably the most useful process I've found yet -- every commit references a ticket, and the ticket lists all changsets.<br />
07:29 < cbrake> zecke: its tough to get people to buy into that, but when they do, it really works well.<br />
07:30 < Crofton|work> gm<br />
07:31 < CIA-5> Koen Kooi <koen@openembedded.org> org.openembedded.dev * rd74bc04b79 openembedded.git/contrib/angstrom/build-feeds.sh: angstrom feed builder:<br />
add geda<br />
07:34 < CIA-5> Koen Kooi <koen@openembedded.org> org.openembedded.dev * rf0678db614 openembedded.git/packages/xorg-xserver/ (xorg-xserver-common.inc<br />
xserver-xorg_1.5.3.bb): xserver xorg: split of Xfbdev to make it parallel installable with kdrive<br />
07:35 < otavio> cbrake: and it is quite easy to close a ticket too; using commits. That is very helpful too :-)<br />
07:36 < otavio> zecke: redmine does a great job and is much more active then trac and other alternatives.<br />
07:36 < otavio> zecke: even though trac still has a larger installed basic, redmine has evolved fastly<br />
07:37 < cbrake> otavio: interesting, I'll have to get that working<br />
07:38 < otavio> cbrake: same place where you adds refs, there is a place to add the closes and other words to be used to close a ticket.<br />
07:39 < otavio> cbrake: it is quite easy<br />
07:41 < cbrake> otavio: ok, I see that. So is the sytax simply: closes 342<br />
07:41 < cbrake> otavio: what is "plugonrails" ?<br />
07:42 < Crofton|work> you guys aren't thinking we should use this for OE?<br />
07:43 * Crofton|work really likes the idea, but isn't sure how well it would in practice for a large diverse group<br />
07:43 < otavio> cbrake: closes #342<br />
07:43 < otavio> cbrake: it is a place where we put our internal plugins to others to use<br />
07:43 < cbrake> Crofton|work: I'm not sure it would add much value to OE. I'm more talking in the context of smaller, commercial projects<br />
07:43 < Crofton|work> yeah<br />
07:43 < otavio> cbrake: we use rails for our client painel<br />
07:44 * Crofton|work thinks OE might benefit from it, but implementation would be challenging<br />
07:45 < cbrake> Crofton|work: one of the challenges with commercial projects is they move fast, and there has to be close teamwork and high visibility to<br />
build trust. Redmine helps build this. It seems like OSS projects are somewhat different.<br />
07:46 < cbrake> * perhaps transparency is a better word<br />
07:46 < Crofton|work> similar but different<br />
07:46 < Crofton|work> on commercial projects everyone has the same goal<br />
07:46 < cbrake> with OSS projects, there is by default transparency, where with commercial projects its often very difficult to achive this<br />
07:47 < Crofton|work> on OSS projects there are different goals for each participant<br />
07:47 < cbrake> nod<br />
07:48 < zecke> pb_: ping<br />
07:48 < otavio> right but different goals doesn't means we shouldn't have a milestone, bug tracking, bug assignation and like<br />
07:49 < otavio> and bugzilla makes it somewhat boring, while new tools (redmine included) makes it easier and neat<br />
07:49 < Crofton|work> otavio, agreed<br />
07:50 < Crofton|work> bugzilla is very good at managing bugs<br />
07:50 < cbrake> otavio: interesting point<br />
07:51 < cbrake> media wiki and bugzilla are obviously more capable as stand-alone tools, so the question is the integration of the tools worth more than the<br />
features we would lose?<br />
07:51 < Crofton|work> I really like having good history (beyond commit messages) for all commits, but I have been accused of being a control freak at times<br />
:)<br />
07:51 < otavio> cbrake: I believe it is worth<br />
07:52 < otavio> cbrake: I never like bugzilla mostly because it doesn't help to track project improvement. It just track issues<br />
07:52 < otavio> cbrake: a project is more the issues ...<br />
07:53 < otavio> cbrake: and redmine, trac and others make all this integrated. It is easy to find what is needed to be done<br />
07:54 < otavio> cbrake: I dislike media wiki and bugzilla and prefer a integrated and a single environment for all this.<br />
07:54 < otavio> cbrake: this also makes easier to write supporting tools to integrate with it<br />
07:56 < Crofton|work> I have seen good rsults with people using trac<br />
07:56 < cbrake> otavio: I think I agree, and I've had lots of good experience using trac/redmine.<br />
07:56 < Crofton|work> but any tool system is only as good as it users<br />
07:56 < Crofton|work> do you knwo a good redmine example?<br />
07:57 < cbrake> well, why don't we paste this discussion on a wiki page, and start listing pluses/minuses and see what everyone else thinks.<br />
07:57 * Crofton|work was going to say post to the list, but maybe trying to flesh the ideas out on a wiki page would be good<br />
07:58 < cbrake> I think we need a clear list of benefits and losses.<br />
08:01 < Crofton|work> yeah<br />
</pre><br />
<br />
[[Category:Dev]]</div>Laibschhttps://www.openembedded.org/index.php?title=Organization&diff=2274Organization2010-04-07T12:37:19Z<p>Laibsch: Reverted edits by 212.235.107.153 (Talk); changed back to last version by XorA</p>
<hr />
<div>The current organization for OE is a German eV legal entity (similar to KDE: http://ev.kde.org/) and is for the purpose of managing finances, voting, and membership.<br />
<br />
An 'eV' for 'eingetragener Verein', in the German law, translates to a voluntary organization; a group of individuals who voluntarily enter into an agreement to form a body (or organization) to accomplish a purpose. The organization has members.<br />
<br />
The OpenEmbedded eV statues are located here: http://docs.openembedded.org/organization/2008-11-22_statutes-de.pdf<br />
<br />
A bablefish translation is here -- could German speaking folks please clean this up: [[OpenEmbedded eV Statutes]]<br />
<br />
During FOSDEM 2008 in Brussels, Belgium, a group of founding members physically gathered to get the paperwork going.<br />
<br />
= The current board of directors =<br />
<br />
* President ''Dr. Michael Lauer''<br />
* Vice President ''Philip Balister''<br />
* Vice President and Treasurer ''Florian Boor''<br />
* Board Member ''Graeme Gregory''<br />
<br />
= Current Members =<br />
(please keep in alphabetical order)<br />
# Alessandro Gardich<br />
# Chris Larson<br />
# Cliff Brake<br />
# Daniel Willmann<br />
# Denys Dmytriyenko<br />
# Dirk Opfer<br />
# Dmitry EreminSolenikov<br />
# Florian Boor<br />
# Graeme Gregory<br />
# Henning Heinold<br />
# Holger Freyther<br />
# Jan Lübbe<br />
# Ken Gilmer<br />
# Khem Raj<br />
# Koen Kooi<br />
# Leon Woestenberg<br />
# Liam Girdwood<br />
# Marcin Juszkiewicz<br />
# Marco Cavallini<br />
# Mark Brown<br />
# Michael Lauer<br />
# Philip Balister<br />
# Philip Blundell<br />
# Phillip Zabel<br />
# Richard Purdie<br />
# Robert Schuster<br />
# Stefan Schmidt<br />
<br />
= OE Developers =<br />
Openembedded Developers are people who have write access to the git repository. Due to the nature of OE, there are many developers, and each one tends to maintain a section of OE. A list of maintainers can be found [http://cgit.openembedded.net/cgit.cgi?url=openembedded/tree/MAINTAINERS here]. See [[OpenEmbedded Developers]] for a list of current developers.<br />
<br />
= Todo =<br />
* process for adding new members<br />
* process for voting<br />
* responsibility of the board<br />
* conflict resolution<br />
<br />
= Pointers for Board Members =<br />
* [[Checklist for the General Assembly]]<br />
<br />
= Online Voting Policy =<br />
* [[Online Voting Policy]]<br />
<br />
= Faq =<br />
; Are contributions tax deductible?<br /><br />
: Yes they are. <br />
; Should I become member of the OE e.V.?<br />
: If you are contributing to OE frequently and/or you are interested in getting involved in administrative or organisational tasks it might be a good idea to join OE e.V.<br />
; How do I become member of the OE e.V.?<br />
: Let an existing member introduce you by sending a short introduction to the 'ev' [http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-members mailinglist]. If you don't know one get in touch with us on the development mailinglist or IRC first. The e.V. is open for anyone to join and its not meant to be an exclusive club of a few developers. <br />
; Is there a membership fee?<br />
: Yes, and no, since you are allowed to defined the amount on your own.<br />
<br />
[[Category:Dev]]</div>Laibschhttps://www.openembedded.org/index.php?title=BeagleBoard&diff=2273BeagleBoard2010-04-07T12:36:40Z<p>Laibsch: Reverted edits by 195.216.197.104 (Talk); changed back to last version by 119.226.217.133</p>
<hr />
<div>== Kernel Support in OE ==<br />
<br />
=== Linux ===<br />
<br />
OpenEmbedded offers more than one kernel for the BeagleBoard. All come with several patches but the support of the BeagleBoard hardware is not perfect yet.<br />
The table summarizes the current status of hardware support. Please note that this applies to the kernels we have in OE only.<br />
<br />
{| border="1" cellspacing="0" cellpadding="6" align="center"<br />
! Boot <br />
! USB OTG <br />
! USB host <br />
! DVI <br />
! Audio out<br />
! Audio in<br />
! S-Video out<br />
! MMC / SD<br />
! RS232<br />
! Flash<br />
! DSP<br />
! SGX<br />
|-<br />
| 2.6.27-r11<br />
| style="background:yellow;" | host only <br />
| style="background:green;" | <br />
| style="background:green;" | <br />
| style="background:yellow;" | <br />
| style="background:red;" |<br />
| style="background:red;" | <br />
| style="background:green;" | <br />
| style="background:green;" | <br />
| style="background:green;" | <br />
| style="background:green;" | <br />
| style="background:green;" | <br />
|-<br />
| 2.6.28-r12<br />
| style="background:green;" | <br />
| style="background:green;" | <br />
| style="background:green;" | <br />
| style="background:green;" | <br />
| style="background:green;" |<br />
| style="background:green;" | <br />
| style="background:green;" | <br />
| style="background:green;" | <br />
| style="background:green;" | <br />
| style="background:green;" | <br />
| style="background:green;" | <br />
|-<br />
|}<br />
<br />
Currently 2.6.27 is the default kernel in OE. If you want to build 2.6.28 you can set PREFERRED_VERSION_linux-omap = "2.6.28" in your local.conf. Then build the kernel <code>bitbake virtual/kernel</code> or a filesystem that should include the kernel modules.<br />
Another way to build the desired kernel is to point OE to the kernel bb directly. <br />
<br />
[[Category: Machine]]</div>Laibschhttps://www.openembedded.org/index.php?title=OEandYourDistro&diff=2202OEandYourDistro2010-02-18T13:26:32Z<p>Laibsch: /* Mandatory packages */</p>
<hr />
<div>See [[Required software]] for the list of the software required by Openembedded.<br />
<br />
= Using OpenEmbedded on Linux systems =<br />
<br />
== deb-based distributions ==<br />
<br />
The easiest way is via [http://blog.leggewie.org/?p=39 apt-get'able Openembedded] which will pull the OE meta-data for you and keep it up-to-date. Plus, it makes sure all necessary software for cross-compilation is installed. Easy as 1-2-3.<br />
<br />
=== Debian ===<br />
<br />
==== Mandatory packages ====<br />
<br />
aptitude install sed wget cvs subversion git-core \<br />
coreutils unzip texi2html texinfo libsdl1.2-dev docbook-utils \<br />
gawk python-pysqlite2 diffstat help2man make gcc build-essential g++ \<br />
desktop-file-utils<br />
<br />
'''Git'''<br />
<br />
On debian you may have to run <br />
<br />
update-alternatives --config git (as root)<br />
<br />
and select /usr/bin/git-scm to provide git instead of /usr/bin/git.transition. This is not necessary in sid<br />
<br />
==== Supplimentary packages ====<br />
<br />
<pre><nowiki><br />
apt-get install libxml2-utils xmlto python-psyco<br />
</nowiki></pre><br />
<br />
<br />
OPTIONAL: these packages and their dependencies need to be installed in order to build the bitbake documentation (warning: over 160MB of installed packages).<br />
<br />
<pre><nowiki><br />
apt-get install docbook<br />
</nowiki></pre><br />
This package is necessary to build some packages (in particular the esound documentation needs it).<br />
<br />
=== Ubuntu ===<br />
<br />
Ubuntu is based on Debian and instructions above for [[#deb-based distributions|Debian]] apply here as well. Make sure that you have the universe repositories in your apt configuration.<br />
<br />
* Check that /bin/sh (ls -l /bin/sh) is not symbolically linked to dash. "dash" is a POSIX compliant shell that is much smaller than "bash" -- however some broken shell scripts still make use of bash extensions while calling into /bin/sh. To work around this issue call "''sudo dpkg-reconfigure dash''" and select No when it asks you to install dash as /bin/sh.<br />
* You can also install Psyco Python JIT compiler to speed up BitBake. Psyco works on 32-bit x86 platforms only. "''aptitude install python-psyco''<br />
* there are known [[gcc issues in Intrepid and later]] when cross-compiling with OE<br />
<br />
== rpm-based distributions ==<br />
<br />
=== Mandriva Linux ===<br />
<br />
Follow the Debian instructions, only using `urpmi` instead of `apt-get install`. You can find it in the contrib section of any Mandriva mirror or seach for it using the Mandriva Club rpm database [http://rpms.mandrakeclub.com]. You may need libpythonV.V-devel for bitbake setup instead of python-dev.<br />
If you're building a 2.6 kernel, you also need the glibc-static-devel package.<br />
<br />
with Mandriva Linux 2006, you need to issue the following command:<br />
<br />
<pre><nowiki><br />
urpmi python python-devel python-psyco patch m4 sed bison make wget bzip2 \<br />
cvs gawk glibc-devel gcc-c++ subversion sharutils coreutils docbook-utils openjade \<br />
quilt pcre-devel unzip glibc-static-devel<br />
</nowiki></pre><br />
<br />
=== openSUSE ===<br />
<br />
==== openSUSE 11.1 ====<br />
<br />
Use zypper to install the required packages:<br />
<br />
zypper in subversion git python help2man diffstat wget gcc gcc-c++ libstdc++ glibc-devel texinfo automake patch<br />
<br />
These packages may be useful as well: bison and [http://software.opensuse.org/search?baseproject=ALL&p=1&q=gcc33 gcc33] (for faster build using ASSUME_PROVIDED), gtk2-devel (in case your build will fail on missing gdk-pixbuf-csource), bc (for collie kernel), ncurses-devel (if you want to call kernel menuconfig). python psyco package is optional.<br />
<br />
=== Fedora ===<br />
<br />
==== Fedora Core 2/3 ====<br />
Much of the following is probably already installed, but you can check with the following commands. You may want to use the yum.conf located at http://www.fedorafaq.org/. Note, this has not been tested yes as I am in the process of setting up a development environment.<br />
<br />
<pre><nowiki> yum install python patch m4 sed make docbook* openjade glibc-devel xmlto</nowiki></pre><br />
<br />
* psyco: Download psyco-1.4-src.tar.gz (or later) and extract it. Go to the psycho top-level directory and run: `python setup.py install`.<br />
<br />
* patch: FC3 default version should be enough. Optionally, install SuSe 9.1 package of it.<br />
<br />
==== Fedora Core 4 ====<br />
Almost all required packages for Openembedded are available in Fedora Core 4 and the Fedora Extras for Core 4. You can download them from <http://download.fedora.redhat.com/pub/fedora/linux/core> and <http://download.fedora.redhat.com/pub/fedora/linux/extras>. Check <http://download.fedora.redhat.com/pub/fedora/linux/core/updates/4> for updates on the Core 4 packages.<br />
<br />
Apart from the usual (native) development packages like gcc and binutils, you should check that you have the following RPM's installed: <br />
<br />
* bison<br />
* docbook* packages<br />
* libpcre<br />
* m4<br />
* make<br />
* openjade<br />
* patch<br />
* PyQt<br />
* python<br />
* python-psyco<br />
* sed<br />
* xmlto<br />
* quilt (not required as OE builds it by itself, but install it if you want to use gquilt)<br />
<br />
Use apt, synaptic, up2date or yum to automagically retrieve these packages or download and install them manually (lots of work).<br />
<br />
==== Fedora Core 5/6 ====<br />
<br />
Commands I used to install OE pre-requisites on FC5/6<br />
<br />
This long command will ensure all pre-requisites are installed (patch is 2.5.4, not 2.5.9, but appears to work).<br />
<br />
<pre><nowiki><br />
su -c "yum install python m4 make wget curl ftp cvs subversion tar bzip2 gzip \<br />
unzip python-psyco perl texinfo texi2html diffstat openjade docbook-style-dsssl \<br />
docbook-style-xsl docbook-dtds docbook-utils sed bison bc glibc-devel gcc binutils \<br />
pcre pcre-devel git quilt groff linuxdoc-tools patch gcc gcc-c++ python-sqlite2 help2man"<br />
</nowiki></pre><br />
<br />
or download the metapackage http://www.openembedded.org/dl/packages/rpm/openembedded-essential-1.1-1.noarch.rpm (may be out of date).<br />
<br />
then do<br />
<br />
<pre><nowiki><br />
su -c "yum localinstall openembedded-essential-1.1-1.noarch.rpm"<br />
</nowiki></pre><br />
<br />
<br />
There are also rpm and src.rpm packages of bitbake 1.6.2 at http://www.openembedded.org/dl/packages/rpm/ pending a later version in Extras, currently 1.6.0.<br />
<br />
Update - Current FC6 version is patch-2.5.4-29.2.2 as of this writing and works-for-me (see revision history for build instructions if current patch does not work for you).<br />
<br />
I didn't install SGML tools. Please add if you know how<br />
<br />
Update - Since about 2002 sgml-tools has apparently been replaced by linuxdoc-tools for FC.<br />
<br />
==== Fedora 7 ====<br />
<br />
This long command will ensure all pre-requisites are installed (patch is 2.5.4, not 2.5.9, but appears to work).<br />
<br />
<pre><nowiki><br />
su -c "yum install python m4 make wget curl ftp cvs subversion tar bzip2 gzip unzip \<br />
python-psyco perl texinfo texi2html diffstat openjade docbook-style-dsssl \<br />
docbook-style-xsl docbook-dtds docbook-utils sed bison bc glibc-devel gcc binutils \<br />
pcre pcre-devel git quilt groff linuxdoc-tools patch linuxdoc-tools gcc gcc-c++ \<br />
help2man perl-ExtUtils-MakeMaker"<br />
</nowiki></pre><br />
<br />
(if this is hard to copy from this HTML page, go to edit mode and copy from editor)<br />
<br />
==== Fedora 11 ====<br />
<br />
Fedora 11, compared to previous versions, brings the need to install "glibc-static" as well:<br />
<br />
<pre><nowiki><br />
su -c "yum install python m4 make wget curl ftp cvs subversion tar bzip2 gzip unzip \<br />
python-psyco perl texinfo texi2html diffstat openjade docbook-style-dsssl \<br />
docbook-style-xsl docbook-dtds docbook-utils sed bison bc glibc-devel glibc-static \<br />
gcc binutils pcre pcre-devel git quilt groff linuxdoc-tools patch linuxdoc-tools \<br />
gcc-c++ help2man perl-ExtUtils-MakeMaker"<br />
</nowiki></pre><br />
<br />
(if this is hard to copy from this HTML page, go to edit mode and copy from editor)<br />
<br />
=== CentOS 4.4 / Red Hat Enterprise Linux 4 ===<br />
May also work for true EL4 or Scientific Linux - another RHEL rebuild<br />
<br />
Even with several optional and 3rd party yum repos enabled (centosplus, kbsingh, RPMforge/Dag, Dries) a number of required packages are too old or unavailable for CentOS4. [It should be possible to use other package managers including apt/synaptic, up2date, and smart to get the required packages. The following assumes yum.]<br />
<br />
I re-built the following SRPMS (with "$ rpmbuild --rebuild ..."):<br />
* boost-1.33.1-10.fc5.src.rpm<br />
* bitbake-1.6.2-1.src.rpm (Latest tarball from http://developer.berlios.de/projects/bitbake/ + modified spec from bitbake-1.6.0-2.fc7.src.rpm)<br />
<br />
Might also want to try the rpm and src.rpm packages of bitbake 1.6.2 at http://www.openembedded.org/dl/packages/rpm/ - I have not.<br />
<br />
Extra requirements for the builds included rpmdevtools, xmlto, and lynx.<br />
<br />
I put packages in a local repo so I can do "yum install ...", otherwise can do "yum localinstall foo.1.2.3.noarch.rpm ...". It may be necessary to temporarily set "gpgcheck=0" in /etc/yum.conf to avoid complaints about unsigned packages.<br />
<br />
For EL4 texi2html is available from the tetex package, currently tetex-2.0.2-22.EL4.7<br />
<br />
Note that the the metapackage http://www.openembedded.org/dl/packages/rpm/openembedded-essential-1.1-1.noarch.rpm<br />
should work except that it depends on texi2html.<br />
<br />
Instead as root do<br />
<br />
<pre><nowiki><br />
yum install bison coreutils cvs docbook-utils gawk git-core python quilt rpmlib \<br />
sed subversion tetex texinfo unzip wget<br />
</nowiki></pre><br />
<br />
I ended up with the following set of relevant packages after several iterations of building/updating to get "bitbake nano" to complete successfully:<br />
<br />
* python-2.3.4-14.3<br />
* m4-1.4.1-16<br />
* make-3.80-6.EL4<br />
* wget-1.10.2-0.40E<br />
* curl-7.12.1-8.rhel4<br />
* ftp-0.17-22<br />
* cvs-1.11.17-9.RHEL4<br />
* subversion-1.4.3-0.1.el4.rf<br />
* tar-1.14-12.RHEL4<br />
* bzip2-1.0.2-13.EL4.3<br />
* gzip-1.3.3-16.rhel4<br />
* unzip-5.51-7<br />
* python-psyco-1.5-3.el4.kb<br />
* perl-5.8.5-36.RHEL4<br />
* texinfo-4.7-5.el4.2<br />
* tetex-2.0.2-22.EL4.7<br />
* diffstat-1.34-0_6.el4.at<br />
* openjade-1.3.2-16_9.el4.at<br />
* docbook-style-dsssl-1.78-4<br />
* docbook-style-xsl-1.65.1-2<br />
* docbook-dtds-1.0-25<br />
* docbook-utils-0.6.14-4<br />
* sed-4.1.2-5.EL4<br />
* bison-1.875c-2<br />
* bc-1.06-17.1<br />
* glibc-devel-2.3.4-2.25<br />
* gcc-3.4.6-3<br />
* binutils-2.15.92.0.2-21<br />
* pcre-4.5-3.2.RHEL4<br />
* pcre-devel-4.5-3.2.RHEL4<br />
* git-1.4.4.2-2.el4.kb<br />
* bitbake-1.6.2-1<br />
<br />
=== ALT Linux ===<br />
<br />
You can read more about ALT Linux here: http://www.altlinux.com/en/<br />
<br />
You can use synaptic or aptitude to install packages. Or use apt-get as shown below.<br />
<br />
<pre><nowiki><br />
apt-get install git-core python python-dev python-module-psyco python-modules-sqlite3 \<br />
patch m4 sed bison make wget bzip2 cvs gawk gcc-c++ subversion sharutils coreutils \<br />
docbook-utils openjade quilt libpcre-devel unzip glibc-devel glibc-devel-static \<br />
help2man texi2html perl-devel<br />
</nowiki></pre><br />
<br />
For building bitbake manuals you have to install 'xmlto' package:<br />
<br />
<pre><nowiki><br />
apt-get install xmlto<br />
</nowiki></pre><br />
<br />
NOTES:<br />
* This is tested on ALD 4.0/4.1/5.0.<br />
* gcc-c++ is virtual package and can be provided by gcc4.3-c++ (ALD 5.0) and gcc4.1-c++ (ALD 4.0/4.1). Just select higher version.<br />
<br />
=== Ark Linux 2008.1 ===<br />
[http://www.arklinux.org/ Ark Linux] is a modern distribution well suited for Openembedded development. Footprint only 2.1G.<br />
<br />
Required steps:<br />
<br />
1) install required packages<br />
<pre><nowiki><br />
apt-get install devel-core diffstat texi2html cvs subversion git texinfo psyco python-devel \<br />
python-encodings python-sqlite help2man bitbake<br />
</nowiki></pre><br />
<br />
2) upgrade<br />
<pre><nowiki><br />
apt-get update<br />
apt-get dist-upgrade <br />
<br />
The following packages will be REPLACED:<br />
texi2html (by texlive-texi2html)<br />
The following NEW packages will be installed:<br />
texlive-texi2html<br />
</nowiki></pre><br />
<br />
3) finally create your OE tree (see [[Getting started]] instructions). bitbake is already included, so you can skip that step.<br />
<br />
== other Linux distributions ==<br />
<br />
=== Gentoo instructions ===<br />
<pre><nowiki><br />
emerge -n \<br />
psyco \<br />
patch \<br />
make \<br />
sed \<br />
dev-lang/python \<br />
m4 \<br />
bison \<br />
cvs \<br />
openjade \<br />
quilt \<br />
sgmltools-lite \<br />
docbook-xml-dtd \<br />
docbook-dsssl-stylesheets \<br />
xmlto \<br />
docbook-sgml-utils \<br />
libpcre \<br />
boost \<br />
subversion \<br />
texi2html \<br />
pysqlite<br />
</nowiki></pre><br />
<br />
Then follow the instructions in [[Getting started]] for obtaining bitbake and start the build.<br />
<br />
=== Arch Linux (Duke) ===<br />
<br />
Most of the packages are available in the repositories.<br />
<br />
<pre><nowiki><br />
sudo pacman -S psyco patch make sed python m4 bison cvs quilt sgmltools-lite docbook-xml \<br />
xmlto pcre boost jade git texinfo<br />
</nowiki></pre><br />
<br />
In Arch Linux the install command is in /bin/install. Since most of Linux distribution assume that install is located in /usr/bin/install, you have to create a symlink:<br />
<br />
<pre><nowiki><br />
sudo ln -s /bin/install /usr/bin/install<br />
</nowiki></pre><br />
<br />
You can build BitBake by using this PKGBUILD:<br />
<pre><nowiki><br />
pkgname=bitbake<br />
pkgver=1.8.4<br />
pkgrel=1<br />
pkgdesc="A simple tool for task execution derived from Gentoo's portage"<br />
url="http://developer.berlios.de/projects/bitbake/"<br />
arch=('i686')<br />
license=('GPL' 'custom')<br />
depends=('python')<br />
source=(http://download.berlios.de/bitbake/${pkgname}-${pkgver}.tar.gz)<br />
md5sums=('508d9a61c635d469be8facc95151158b')<br />
<br />
build() {<br />
cd ${startdir}/src/${pkgname}-${pkgver}<br />
python setup.py install --root=${startdir}/pkg<br />
<br />
# Install vim extensions<br />
install -D -m644 ${startdir}/src/${pkgname}-${pkgver}/contrib/vim/ftdetect/bitbake.vim \<br />
${startdir}/pkg/usr/share/vim/ftplugin/bitbake.vim<br />
install -D -m644 ${startdir}/src/${pkgname}-${pkgver}/contrib/vim/syntax/bitbake.vim \<br />
${startdir}/pkg/usr/share/vim/syntax/bitbake.vim<br />
<br />
# Handle MIT license<br />
install -D -m644 ${startdir}/src/${pkgname}-${pkgver}/doc/COPYING.MIT \<br />
${startdir}/pkg/usr/share/licenses/${pkgname}/COPYING.MIT<br />
}<br />
</nowiki></pre><br />
<br />
= Using OpenEmbedded on FreeBSD and other NON Linux Systems =<br />
<br />
tbd<br />
<br />
== FreeBSD ==<br />
<br />
* Python == /usr/ports/lang/python<br />
* GNU Patch == /usr/ports/devel/patch<br />
* GNU m4 == /usr/ports/devel/m4<br />
* GNU make == /usr/ports/devel/gmake<br />
* wget == /usr/ports/ftp/wget<br />
* Psyco JIT Compiler == /usr/ports/devel/py-psyco<br />
* GNU sed == /usr/ports/textproc/gsed<br />
* Bison == /usr/ports/devel/bison<br />
* GCC 2.95.3 == /usr/ports/lang/gcc295<br />
* bc == already in FreeBSD<br />
* PyQt == /usr/ports/x11-toolkits/py-qt<br />
* glibc headers (ignore)<br />
* subversion == /usr/ports/devel/subversion<br />
* git == /usr/ports/devel/git<br />
* pcre == /usr/ports/devel/pcre<br />
<br />
Ports has also has these: fileutils, jade, docbook, dsssl-docbook-modular, sgmltools<br />
<br />
== Using OpenEmbedded on Mac OS X ==<br />
<br />
By default OS X uses a filesystem that is '''not''' case sensitive. You need to ensure that at least your tmp directory is on a case sensitive filesystem or you may come across various packages that break, including the Linux kernel! These steps were carried out on a early 32 bit 10.5/Intel Mac - the install order matters for a couple of packages as does having them installed in a more normal location.<br />
<br />
# Register at [https://connect.apple.com ADC] and download and install Xcode<br />
# Compile and install [http://www.gnu.org/software/gettext/ GNU gettext]<br />
# Using CPAN install Locale::gettext<br />
# Compile and install [http://www.gnu.org/software/help2man/ help2man 1.29] - newer versions will not build without hacks<br />
# Compile and install [http://www.gnu.org/software/wget/ wget], [http://www.gnu.org/software/gawk/ gawk], [http://www.gnu.org/software/coreutils/ coreutils] and [http://git-scm.com/ git] - wget appears to not work if you install it in /usr/local so use --prefix=/usr also note OS X provides a different version of mktemp which functions differently, be careful not to overwrite this as OS X might need it<br />
# If you are on a 32 bit Mac you can of course install [http://psyco.sourceforge.net/ psyco]<br />
# Fixup your PATH variable for your build user so that /usr/local/bin (or where ever coreutils etc is installed) comes before the OS X version in /usr/bin<br />
# Install GNU sed 3.0.2, this will give you a version of sed that allows you to build sed 4.1.5 - you will need to overwrite the one provided by OS X with --prefix=/usr and ensure you are using 4.1.5 not 3.0.2 as 3.0.2 does not provide various options you need<br />
# Install getopt from [http://software.frodo.looijaard.name/getopt/download.php here] - modify WITHOUT_GETTEXT=0 to WITHOUT_GETTEXT=1 in the Makefile and add -DWITHOUT_GETTEXT=$(WITHOUT_GETTEXT) to the line beginning with CPPFLAGS=<br />
<br />
Now follow the Getting Started OpenEmbedded wiki guide. Unfortunately there are various issues building on OS X that will most likely prevent the toolchain from building.<br />
<br />
Unfinished - tbd<br />
<br />
= Using OpenEmbedded on Windows/Cygwin Systems =<br />
<br />
<br />
Building Openembedded on Windows is currently unsupported, but [http://oe.linuxtogo.org/wiki/BuildOnCygwin work is in progress] to support buidling of meta-toolchain.bb on Windows/Cygwin hosts.<br />
<br />
[[Category:User]]</div>Laibschhttps://www.openembedded.org/index.php?title=Inspect_DEPENDS&diff=2201Inspect DEPENDS2010-02-18T13:24:52Z<p>Laibsch: </p>
<hr />
<div>'''How do do I inspect compile-time dependencies for packages?'''<br />
<br />
You want a "visual" output of the dependency tree for a particular package?<br />
<br />
bitbake --dry-run --verbose $packagename | grep "current path" | less<br />
<br />
should give you that information. Another way is the more recent<br />
<br />
bitbake -g $packagename && less *.dot<br />
<br />
If you have graphviz installed, you can convert the .dot file to PostScript (.ps).<br />
<br />
dot -Tps task-depends.dot -o task-depends.ps<br />
<br />
And then we can open the .ps file with gimp or evince, send it to the printer or whatever you usually do with these files.<br />
<br />
''Be careful that a complex package such as mplayer gives .dot and .ps files that will require too much RAM, so they can't actually be opened''<br />
<br />
[[Category:FAQ]]<br />
[[Category:Debug build]]</div>Laibschhttps://www.openembedded.org/index.php?title=Oedem/2009&diff=2200Oedem/20092010-02-18T13:19:46Z<p>Laibsch: Reverted edits by 216.45.58.187 (Talk); changed back to last version by Laibsch</p>
<hr />
<div>OpenEmbedded developers' meeting 2009 will be in Cambridge, UK on the weekend of November 7/8.<br />
<br />
All developers and other interested parties are welcome.<br />
<br />
==Location==<br />
<br />
Reciva Ltd have generously offered to host the meeting at their offices: 509 Coldhams Lane, Cambridge, CB1 3JS.<br />
<br />
The Reciva offices are on the east side of the city, about 2km from the centre of town. See below for detailed travel information.<br />
<br />
Call Phil on +44 7973 869202 if you get hopelessly lost and cannot find the venue.<br />
<br />
==Registration==<br />
<br />
Due to restricted space at the venue, the number of attendees is strictly limited.<br />
<br />
Pre-registration is now closed, although it is possible that more spaces may become available if previously-registered attendees drop out. Send mail to Phil if you wish to attend but missed the deadline for initial registration.<br />
<br />
==Agenda==<br />
<br />
===Friday 2009-11-06===<br />
<br />
20:00 (approx) Pre-meeting beer session at the Red Lion, Histon, CB24 9BD<br />
<br />
http://maps.google.co.uk/maps?f=q&source=s_q&hl=en&geocode=&q=cb24+9jd&sll=53.800651,-4.064941&sspn=11.25,27.905273&ie=UTF8&ll=52.253684,0.105486&spn=0.011375,0.027251&t=h&z=15&iwloc=A<br />
<br />
From the city centre, ride the [http://www.stagecoachbus.com/timetables/Citi7Jan09%5B3%5D.pdf Citi 7] bus towards Cottenham. Pass Histon village green (pond with ducks) on your right, the Boot and Barley Mow pubs on your left, then alight at the next stop and you will be almost directly outside the Red Lion. Travel time from the city is approximately 25 minutes and a return ticket costs about £3. Other travel options include taxi (10-15 minutes, about £10 each way) or walking (50-60 minutes, no charge). <br />
<br />
===Saturday 2009-11-07===<br />
<br />
10:00-10:15 Welcome + Agenda<br />
<br />
: Introductions and discussion/confirmation of agenda<br />
: some entries will need to be moved as few of us will have to leave earlier on Sunday (Henning, Marcin and Marco have train at 17:10)<br />
<br />
10:15-12:00 OE e.V. meeting (Mickey Lauer / e.V. board)<br />
<br />
: '''e.V. Membership Fees'''<br />
<br />
: As per our statutes, members can chose their membership fees. We should create recommendations for corporate entities (also indicate what they would gain by that).<br />
: '''Travel reimbursement policy'''<br />
: '''Financial status'''<br />
: '''Sponsors: announcement, website and memberships'''<br />
: '''Public relations committee'''<br />
<br />
12:00-13:00 Establishment of technical steering committee (Phil Blundell)<br />
<br />
13:00-14:00 Break for lunch / hacking session<br />
<br />
14:00-15:00 OE and Poky (Mickey Lauer)<br />
<br />
15:00-16:00 Software development for OE derived distributions<br />
<br />
* Quick presentation of KOBE (Eclipse plugin by KOAN for recipe creation and more)<br />
<br />
People always want to develop software for the target hardware, what can we do to make developers lives easier? The answer is not always use bitbake. How do we supply toolchains, libraries etc? How are people solving this today?<br />
<br />
16:00-16:30 Learning to love USE flags, or, What's a distro for? (Phil Blundell)<br />
<br />
16:30-17:00 State of the art in package management (Phil Blundell)<br />
<br />
* Why is opkg so bad?<br />
* What alternatives are there?<br />
* What can we do to improve the situation?<br />
<br />
17:00-18:00 Hacking session<br />
<br />
18:00 Venue closes<br />
<br />
===Sunday 2009-11-08===<br />
<br />
10:00-11:00 Splitting the recipes tree (Mickey Lauer)<br />
<br />
: Many of us feel we should split the recipes up into a couple of smaller categories to be able to handle them in a more efficient way (parsing, switching on/off, etc.), but also to indicate which packages are critical / very well maintained / not maintained at all / ...<br />
<br />
11:00-12:00 Future plans for stable branch(es)<br />
<br />
* Why stable branch is actually not so stable?<br />
* Creation of long term support branch?<br />
<br />
12:00-13:00 Bugtracker Discussion, what to do with the current bugzilla, replace/enhance/abandon. (Graeme 'XorA' Gregory)<br />
<br />
13:00-14:00 Break for lunch/hacking<br />
<br />
14:00-15:00 Hosting arrangements (Mickey Lauer) (see [[Infrastructure]])<br />
<br />
: There are still services on amethyst, although former-admin Mickey has requested them to be moved. Obviously some one needs to take the wheel here.<br />
<br />
: Services on Amethyst:<br />
<br />
* patchwork.openembedded.org<br />
* wiki.openembedded.org<br />
* www.openembedded.org<br />
<br />
: Git repository management issues:<br />
<br />
* Clearly identify user branches with a namespace?<br />
* Rename org.openembedded.dev to master?<br />
* CIA commit hook should only report dev branch changes?<br />
<br />
15:00-16:00 Death to checksums.ini? (Phil Blundell)<br />
<br />
: The current method of tracking and verifying checksums on source tarballs has various drawbacks and, due to a combination of technical and social issues, seems to bring few benefits. Can we do any better?<br />
<br />
16:00-17:00 BitBake Future Roadmap (Richard Purdie)<br />
<br />
17:00-18:00 OE Core Changes (Richard Purdie)<br />
<br />
: Discuss various possible core changes to OE such as those to the do_stage process, layout variable changes, Candian SDK Generation. Any others planned?<br />
<br />
18:00 Go home<br />
<br />
==Travel==<br />
<br />
London Stansted airport is the nearest to Cambridge with regular service. <br />
(There is a small airport in Cambridge itself but I don't think any scheduled<br />
airlines operate from there anymore.)<br />
<br />
For those travelling from Europe, Stansted is about a 30-minute train ride from Cambridge city centre and is served by Air Berlin, Ryanair and Germanwings among others. Luton airport is about 1 hour away by bus and is served by Easyjet.<br />
<br />
For those travelling from further away, most long-haul flights arrive at Heathrow or Gatwick airports (although there is some transatlantic service into Stansted). Both Heathrow and Gatwick are about 2 hours from Cambridge by train or bus: the train is quicker but involves several changes in London, whereas the bus is slow but cheaper and less complicated.<br />
<br />
If arriving at LHR airport, take the [http://thetube.com Piccadilly line] from the Underground station and ride it all the way to Kings Cross St Pancras. Ascend to street level, follow signs to Kings Cross mainline station (not St Pancras: the two stations are different although they share a subway stop) and then look for trains to Cambridge or Kings Lynn on the departure board. There are usually two fast services and two slow services to Cambridge per hour: the slow trains are often overtaken by the fast ones en route so it may be best to wait for a fast service even if this is not the next to depart.<br />
<br />
If arriving at LCY, take the [http://www.tfl.gov.uk/gettingaround/2558.aspx#London_City_Airport DLR] to Bank, then change to the Northern Line northbound. From Kings Cross St Pancras, proceed as for LHR, above.<br />
<br />
http://nationalrail.co.uk<br />
<br />
http://nationalexpress.co.uk/<br />
<br />
Alternatively you can take the Eurostar to London St Pancras, which is 50 minutes from Cambridge by train.<br />
<br />
=== Directions from Cambridge rail station to Reciva HQ ===<br />
<br />
'''By bus''' (approximate travel time 30 minutes)<br />
<br />
- take Citi 1 bus towards Fulbourn, alight at St Andrews church in Cherry Hinton, then walk down Coldhams Lane for about 500 metres. Our building will be on your right and has a large sign on the front reading "Semitool". The Citi 1 route runs 7 days a week, about every ten minutes during the daytime, less often (but still fairly frequent) in the evenings.<br />
<br />
- alternatively, take any bus to the city centre and then catch service 16 going out of town (the city centre is a terminus on this route). Alight at the first stop after the Rosemary Branch pub on Coldhams Lane and you will be directly outside the office. Note that bus #16 only runs once per hour so check departure times before choosing this route.<br />
<br />
http://www.cambridgeshire.gov.uk/transport<br />
<br />
http://www.stagecoachbus.com/cambridge<br />
<br />
'''On foot''' (approximate travel time 45 minutes) or bike (approx 15 minutes)<br />
<br />
- Turn right immediately in front of the station and cross the car park, passing the hotel and cycle shop on your left.<br />
<br />
- Upon exiting the car park, go up the steps to the cycle/footbridge and cross to the other side of the railway line.<br />
<br />
- Exit the bridge and turn left, then immediately right into Greville Road.<br />
<br />
- At the end of Greville Road, go left on Coleridge Road. Cross at the pedestrian crossing and go through the chicane onto the footpath opposite.<br />
<br />
- Proceed down Marmora Road. Cross Hobart Road and proceed down the footpath.<br />
<br />
- Go left into Montreal Road, then right into Natal Road.<br />
<br />
- Go left on Perne Road. At the lights, cross to the other side and go down Brookside.<br />
<br />
- When the road bends to the right, do not follow the curve but instead take the footpath directly ahead (across a small bridge). Follow the path until you arrive at the Holiday Inn Express.<br />
<br />
- Bear left onto Norman Way. Ascend out of the pit to the traffic lights next to the car dealership.<br />
<br />
- Turn right onto Coldhams Lane, then cross to the other side of the street. Pass the yellow self-storage depot, then Reciva HQ is the next building on your left.<br />
<br />
See [http://walkit.com walkit.com] for other route suggestions. The train station is at postcode CB1 2JB. The meeting venue is at CB1 3JS, although walkit (and most map sites, including google) place this about 500 metres too far southeast.<br />
<br />
===Directions to venue by car===<br />
<br />
'''From all points north and west'''<br />
<br />
From the A1 or A10, take the A14 eastbound. Proceed along the Cambridge northern bypass. Leave at junction 35 (for Quy, Newmarket) and take the A1303 towards Cambridge, following signs towards the airport. Turn left at the next roundabout (by the corner of the airport) towards Cherry Hinton. At the next roundabout, go straight ahead into the traffic calmed area. Cross one mini-roundabout, then two in quick succession, then turn right at the traffic lights. Look for a building on your right labelled "SEMITOOL"; this is the meeting venue. If you reach the Rosemary Branch pub and Toyota dealership, you have gone too far.<br />
<br />
==Accommodation==<br />
<br />
The nearest full-service hotel is Holiday Inn Express, http://www.expresscambridge.co.uk/<br />
<br />
Cheapest accomodation is probably the YHA hostel, http://www.yha.org.uk/find-accommodation/east-of-england/hostels/Cambridge/index.aspx<br />
<br />
There are various bed-and-breakfast establishments nearby, prices start at approx £35/night<br />
<br />
Some other hotels in Cambridge: <br />
<br />
http://www.crowneplaza.co.uk/ <br />
<br />
http://www.devere.co.uk/our-locations/university-arms <br />
<br />
http://www.hilton.co.uk/cambridgegardenhouse<br />
<br />
http://www.arundelhousehotels.co.uk/<br />
<br />
==Food and drink==<br />
<br />
There are no catering facilities on site at the meeting venue. Coffee, tea and water are provided, but bringing your own snack/lunch is recommended. There are shops within about 15 minutes' walk where provisions can be purchased.<br />
<br />
==Attending for sure==<br />
<br />
* Philip Balister<br />
* Michael Lauer<br />
* Marco Cavallini<br />
* Richard Purdie<br />
* Marcin Juszkiewicz<br />
* Henning Heinold<br />
* Robert Schuster<br />
* Florian Boor<br />
* Denys Dmytriyenko<br />
* Ken Gilmer<br />
* Esben Haabendal<br />
* Jonathan Cameron<br />
<br />
[[Category:OEDEM]]</div>Laibschhttps://www.openembedded.org/index.php?title=Fosdem_2010&diff=2171Fosdem 20102010-02-02T03:39:29Z<p>Laibsch: add myself to the FOSDEM crowd</p>
<hr />
<div>Attending FOSDEM 2010? Add your name to this page so that other developers can look out for you!<br />
<br />
* Phil Blundell<br />
* Henning Heinold<br />
* Marco Cavallini (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 />
<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.</div>Laibschhttps://www.openembedded.org/index.php?title=How_to_help_out&diff=2165How to help out2010-01-24T15:38:54Z<p>Laibsch: Reverted edits by ShanonDoberman (Talk); changed back to last version by Laibsch</p>
<hr />
<div>'''OE is great and I want to contribute something back. How?'''<br />
<br />
That of course depends on your skills. But you don't need to be an Überhacker to be welcome in the OE community. This is an absolutely non-complete list of things you might want to consider<br />
<br />
* tell others about your positive experience with OE<br />
* donate some money (tax-deductible!) to the [[Organization|e.V.]]<br />
* try to verify, refute or fix some [http://tinderbox.openembedded.net/packages/?status=Failed compile failures] or [http://bugzilla.openembedded.org other bugs]<br />
* Help out with the [http://docs.openembedded.org/usermanual/usermanual.html documentation]. The source is controlled in our [http://cgit.openembedded.net/cgit.cgi?url=openembedded/tree/docs/usermanual git repo]<br />
* Help us [[push patches upstream]] or participate in our [[bug days]]<br />
* add another entry to this list of how to help, yes, that would help us, too ;-)<br />
<br />
[[Category:FAQ]]<br />
[[Category:User]]</div>Laibschhttps://www.openembedded.org/index.php?title=Template:Main_page/news&diff=2157Template:Main page/news2010-01-19T13:42:57Z<p>Laibsch: we prefer Openembedded, not OpenEmbedded, if I remember correctly</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 />
* '''''2010-02-06:''''' Openembedded at [http://fosdem.org FOSDEM'10] - We have a booth at Europe's finest F/OSS event. [[Fosdem 2010|See you in Brussels]]!<br />
* '''''2009-11-07:''''' [[Oedem/2009|Openembedded Developer Meeting 2009]] in Cambridge, UK<br />
* '''''2009-08-12:''''' Openembedded gains ability to create [http://docs.openembedded.org/usermanual/html/ch05s08.html Qt Embedded Linux SDK]<br />
* '''''2009-05-27:''''' Palm is using Openembedded to build Palm [http://developer.palm.com/ webOS]<br />
See [[NewsArchive|News Archive]] for older news.</div>Laibschhttps://www.openembedded.org/index.php?title=Template:Main_page/news&diff=2156Template:Main page/news2010-01-19T13:42:04Z<p>Laibsch: </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 />
* '''''2010-02-06:''''' OpenEmbedded at [http://fosdem.org FOSDEM'10] - We have a booth at Europe's finest F/OSS event. [[Fosdem 2010|See you in Brussels]]!<br />
* '''''2009-11-07:''''' [[Oedem/2009|OpenEmbedded Developer Meeting 2009]] in Cambridge, UK<br />
* '''''2009-08-12:''''' OpenEmbedded gains ability to create [http://docs.openembedded.org/usermanual/html/ch05s08.html Qt Embedded Linux SDK]<br />
* '''''2009-05-27:''''' Palm is using OpenEmbedded to build Palm [http://developer.palm.com/ webOS]<br />
See [[NewsArchive|News Archive]] for older news.</div>Laibschhttps://www.openembedded.org/index.php?title=Template:Main_page/news&diff=2155Template:Main page/news2010-01-19T13:39:39Z<p>Laibsch: </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 />
* '''''2010-01-19:''''' OpenEmbedded at [http://fosdem.org FOSDEM'10] - We have a booth at Europe's finest F/OSS event. [[Fosdem 2010|See you in Brussels]]!<br />
* '''''2009-11-07:''''' [[Oedem/2009|OpenEmbedded Developer Meeting 2009]] in Cambridge, UK<br />
* '''''2009-08-12:''''' OpenEmbedded gains ability to create [http://docs.openembedded.org/usermanual/html/ch05s08.html Qt Embedded Linux SDK]<br />
* '''''2009-05-27:''''' Palm is using OpenEmbedded to build Palm [http://developer.palm.com/ webOS]<br />
See [[NewsArchive|News Archive]] for older news.</div>Laibschhttps://www.openembedded.org/index.php?title=Poky&diff=2150Poky2010-01-18T18:52:00Z<p>Laibsch: </p>
<hr />
<div>[http://www.pokylinux.org/ Poky]<br />
<br />
[[Category:Distro]]</div>Laibschhttps://www.openembedded.org/index.php?title=Talk:Gcc_issues_in_Intrepid_and_later&diff=2148Talk:Gcc issues in Intrepid and later2010-01-18T16:38:52Z<p>Laibsch: </p>
<hr />
<div>Is this still an issue with OE?<br />
<br />
I'm using 9.04 and was at least able to compile one basic image.<br />
I didn't go much further though?<br />
--[[User:Klausfpga|Klausfpga]] 17:49, 9 September 2009 (UTC)<br />
<br />
: This is definitely still an issue.<br />
<br />
: I've tried compiling on a fresh install of latest ubuntu and got all these problems and more.<br />
<br />
: Correct me if i'm wrong but the whole point of the combination of CVS and bitbake is that it can be kept updated so users don't spend days working on workarounds and fixes, most of which could be fixed with some updated packages or .patch's.<br />
<br />
: I've spent the last 3 days fixing compiler errors and researching the multiple issues that have plagued the build with gcc 4.4 (the default in new ubuntu).<br />
<br />
: Surely if it doesn't build with 4.4, the fix should not be "install and use 4.1", it should be "the fix has been committed".<br />
<br />
:: I agree that the proper solution would be "the fix has been committed". The question is who makes, tests and provides us with this patch? Most people are not being paid for what they do with OE, so I guess the only sensible answer to that question would be "those affected". Not all devs are using gcc4.4. So, basically you have three options a) downgrade gcc as suggested, b) prepare the patch yourself (or pay someone to do it), c) wait until somebody else fixes the particular package you want to compile. I would venture to guess that for the ordinary user the order of preference would be a>b>c --[[User:Laibsch|Laibsch]] 16:36, 18 January 2010 (UTC)<br />
<br />
:: Oh, since you asked to be corrected (although it has no effect on the above reasoning), the problem is not in bitbake (which also does not use CVS, but git, you may need to update). The problems are in the upstream projects, although we can fix them in the OE metadata. But bitbake has nothing to do with this at all. --[[User:Laibsch|Laibsch]] 16:38, 18 January 2010 (UTC)</div>Laibschhttps://www.openembedded.org/index.php?title=Talk:Gcc_issues_in_Intrepid_and_later&diff=2147Talk:Gcc issues in Intrepid and later2010-01-18T16:36:34Z<p>Laibsch: </p>
<hr />
<div>Is this still an issue with OE?<br />
<br />
I'm using 9.04 and was at least able to compile one basic image.<br />
I didn't go much further though?<br />
--[[User:Klausfpga|Klausfpga]] 17:49, 9 September 2009 (UTC)<br />
<br />
: This is definitely still an issue.<br />
<br />
: I've tried compiling on a fresh install of latest ubuntu and got all these problems and more.<br />
<br />
: Correct me if i'm wrong but the whole point of the combination of CVS and bitbake is that it can be kept updated so users don't spend days working on workarounds and fixes, most of which could be fixed with some updated packages or .patch's.<br />
<br />
: I've spent the last 3 days fixing compiler errors and researching the multiple issues that have plagued the build with gcc 4.4 (the default in new ubuntu).<br />
<br />
: Surely if it doesn't build with 4.4, the fix should not be "install and use 4.1", it should be "the fix has been committed".<br />
<br />
:: I agree that the proper solution would be "the fix has been committed". The question is who makes, tests and provides us with this patch? Most people are not being paid for what they do with OE, so I guess the only sensible answer to that question would be "those affected". Not all devs are using gcc4.4. So, basically you have three options a) downgrade gcc as suggested, b) prepare the patch yourself (or pay someone to do it), c) wait until somebody else fixes the particular package you want to compile. I would venture to guess that for the ordinary user the order of preference would be a>b>c --[[User:Laibsch|Laibsch]] 16:36, 18 January 2010 (UTC)</div>Laibschhttps://www.openembedded.org/index.php?title=Talk:Gcc_issues_in_Intrepid_and_later&diff=2146Talk:Gcc issues in Intrepid and later2010-01-18T16:36:12Z<p>Laibsch: </p>
<hr />
<div>Is this still an issue with OE?<br />
<br />
I'm using 9.04 and was at least able to compile one basic image.<br />
I didn't go much further though?<br />
--[[User:Klausfpga|Klausfpga]] 17:49, 9 September 2009 (UTC)<br />
<br />
: This is definitely still an issue.<br />
<br />
: I've tried compiling on a fresh install of latest ubuntu and got all these problems and more.<br />
<br />
: Correct me if i'm wrong but the whole point of the combination of CVS and bitbake is that it can be kept updated so users don't spend days working on workarounds and fixes, most of which could be fixed with some updated packages or .patch's.<br />
<br />
: I've spent the last 3 days fixing compiler errors and researching the multiple issues that have plagued the build with gcc 4.4 (the default in new ubuntu).<br />
<br />
: Surely if it doesn't build with 4.4, the fix should not be "install and use 4.1", it should be "the fix has been committed".<br />
<br />
:: I agree that the proper solution would be "the fix has been committed". The question is who makes, tests and provides us with this patch? Most people are not being paid for what they do with OE, so I guess the only sensible answer to that would be "those affected". Not all devs are using gcc4.4. So, basically you have three options a) downgrade gcc as suggested, b) prepare the patch yourself (or pay someone to do it), c) wait until somebody else fixes the particular package you want to compile. I would venture to guess that for the ordinary user the order of preference would be a>b>c --[[User:Laibsch|Laibsch]] 16:36, 18 January 2010 (UTC)</div>Laibschhttps://www.openembedded.org/index.php?title=Styleguide&diff=2145Styleguide2010-01-18T16:27:48Z<p>Laibsch: /* PR variables with recipes that use INC files */</p>
<hr />
<div>= Naming Conventions =<br />
<br />
[[Versioning Policy|Use $packagename_$version.bb]]<br />
<br />
= Format Guidelines =<br />
<br />
* No spaces are allowed behind the line continuation symbol<br />
* The correct spacing for a variable is FOO = "BAR".<br />
* Use quotes on the right hand side of assignments: FOO = "BAR"<br />
* Comments inside bb files are allowed using the '#' character at the beginning of a line.<br />
* Use spaces for indentation as developers tends to use different amount of spaces per one tab.<br />
* Indentation of multiline variables such as SRC_URI is desireable.<br />
<br />
= Style Checking tools =<br />
<br />
Please run ./contrib/oe-stylize.py on your recipes before submitting them.<br />
<br />
= Style Guidelines =<br />
<br />
* Put the ''inherit'' declaration after the initial variables are set up and before any custom ''do_'' routines. This is flexible as ordering is often important.<br />
* If you define custom ''do_'' routines, keep them in the order of the tasks being executed, that is:<br />
** do_fetch<br />
** do_unpack<br />
** do_patch<br />
** do_configure<br />
** do_compile<br />
** do_install<br />
** do_package<br />
** do_stage<br />
<br />
* Don't use ''cp'' to put files into staging or destination directories, use ''install'' instead.<br />
* Don't use ''mkdir'' to create destination directories, use ''install -d'' instead.<br />
<br />
* There is a standard set of variables often found in a .bb file and the preferred order (to make the file easily readable to seasoned developers) is<br />
** DESCRIPTION<br />
** AUTHOR<br />
** HOMEPAGE<br />
** SECTION<br />
** PRIORITY<br />
** LICENSE<br />
** DEPENDS<br />
** RDEPENDS<br />
** RRECOMMENDS<br />
** RSUGGESTS<br />
** PROVIDES<br />
** RPROVIDES<br />
** RCONFLICTS<br />
** SRCDATE<br />
** PV<br />
** PR<br />
** SRC_URI<br />
** S<br />
** inherit ...<br />
** build class specific variables, i.e. EXTRA_QMAKEVARS_POST<br />
** task overrides, i.e. do_configure<br />
** PACKAGE_ARCH<br />
** PACKAGES<br />
** FILES<br />
<br />
= Example Recipe =<br />
<br />
<pre><br />
DESCRIPTION = "X11 Code Viewer"<br />
AUTHOR = "John Bazz <john.bazz@example.org>"<br />
HOMEPAGE = "http://www.example.org/xcv/"<br />
SECTION = "x11/applications"<br />
PRIORITY = "optional"<br />
LICENSE = "GPLv2"<br />
DEPENDS = "libsm libx11 libxext libxaw"<br />
RDEPENDS = "shared-mime-info"<br />
RRECOMMENDS = "ctags"<br />
RCONFLICTS = "xcv2"<br />
SRCDATE = "20060815"<br />
PV = "0.0+cvs${SRCDATE}"<br />
PR = "r5"<br />
<br />
# upstream does not yet publish any release so we have to fetch last working version from CVS<br />
SRC_URI = "cvs://anonymous@xcv.example.org/cvsroot/xcv;module=xcv \<br />
file://toolbar-resize-fix.patch;patch=1"<br />
<br />
S = "${WORKDIR}/xcv/"<br />
<br />
inherit autotools<br />
<br />
do_configure_prepend() {<br />
rm ${S}/aclocal.m4<br />
}<br />
<br />
do_install() {<br />
install -d ${D}${bindir}<br />
install -d ${D}${mandir}/man1<br />
<br />
install -m 0755 xcv ${D}${bindir}/ <br />
install -m 0644 xcv.1.gz ${D}${mandir}/man1/<br />
}<br />
</pre><br />
<br />
= PR variables with recipes that use INC files = <br />
When recipe include files are used, the PR handling gets kind of messy. Its a pain to have to audit the PR in all the dependent recipes when you change something in an INC file. We usually use the following solution:<br />
<br />
<pre><br />
recipe: PR = "${INC_PR}.1"<br />
<br />
inc file: INC_PR = "r1"<br />
</pre><br />
<br />
When converting existing recipes to use INC_PR, set the initial INC_PR to the maximum of the current PRs.<br />
[[Category:Policy]]</div>Laibschhttps://www.openembedded.org/index.php?title=Sources_mirror&diff=2135Sources mirror2010-01-15T21:59:51Z<p>Laibsch: </p>
<hr />
<div>'''What is the OE sources mirror network?'''<br />
<br />
Openembedded uses a large number of upstream sources for compilation. Quite naturally, given the sheer number, at any point in time, one can usually expect at least a few of them to be either temporarily or permanently unavailable. This leads to avoidable user frustration and lost time. The solution is for the Openembedded project to provide a mirror of all the sources used in the recipes as a fallback of last resort. This is done in the OE sources mirror network which has two components.<br />
<br />
* sources.openembedded.org: the main mirror is currently hosted on melo. It aims to have a complete copy of free-to-publish sources used by the current org.oe.dev branch (the stable branch may be added later)<br />
* mirrors.openembedded.org: a swarm of possibly incomplete source mirrors provided by the community and load-balanced via DNS round robin. They act as a first line of defense and lower bandwidth for the main mirror.<br />
<br />
Fetching from these mirrors is transparent to the user and [http://git.openembedded.org/cgit.cgi/openembedded/commit/?id=ad0ba478018ac64598b6701df5a79b1f71f9b58f enabled by default] in the dev branch.<br />
<br />
'''How can I become a member in the mirrors.openembedded.org network?'''<br />
<br />
tbd. right now, ask Laibsch in IRC if you want to help<br />
<br />
[[Category:FAQ]]</div>Laibschhttps://www.openembedded.org/index.php?title=Sources_mirror&diff=2134Sources mirror2010-01-15T21:58:52Z<p>Laibsch: </p>
<hr />
<div>'''What is the OE sources mirror network?'''<br />
<br />
Openembedded uses a large number of upstream sources for compilation. Quite naturally, given the sheer number, at any point in time, one can usually expect at least a few of them to be either temporarily or permanently unavailable. This leads to avoidable user frustration and lost time. The solution is for the Openembedded project to provide a mirror of all the sources used in the recipes as a fallback of last resort. This is done in the OE sources mirror network which has two components.<br />
<br />
* sources.openembedded.org: the main mirror is currently hosted on melo. It aims to have a complete copy of free-to-publish sources used by the current org.oe.dev branch (the stable branch may be added later)<br />
* mirrors.openembedded.org: a swarm of possibly incomplete source mirrors provided by the community and load-balanced via DNS round robin. They act as a first line of defense and lower bandwidth for the main mirror.<br />
<br />
Fetching from these mirrors is transparent to the user and enabled by default in the dev branch.<br />
<br />
'''How can I become a member in the mirrors.openembedded.org network?'''<br />
<br />
tbd. right now, ask Laibsch in IRC if you want to help<br />
<br />
[[Category:FAQ]]</div>Laibschhttps://www.openembedded.org/index.php?title=Push_patches_upstream&diff=2133Push patches upstream2010-01-15T18:51:23Z<p>Laibsch: /* Outline */</p>
<hr />
<div>= Outline =<br />
<br />
OE has quite many patches that are just too valuable to keep to<br />
ourselves. OE encourages the following soft policy for adding patches<br />
to the repository.<br />
<br />
By the way, [http://patch-tracker.debian.org/ Debian], [http://patches.ubuntu.com/ Ubuntu], [http://sources.gentoo.org/viewcvs.py/gentoo-x86/ Gentoo] as well as [http://cvs.fedoraproject.org/viewvc/rpms/ Fedora] are of course always a great source for grabbing high-quality patches to include in OE.<br />
<br />
= Policy =<br />
<br />
1) first line in a patch starts with '''upstream:''' and goes on to list the<br />
URL where the bug has been reported upstream or "OE-only" if the patch <br />
is just a hack or applicable only to OE.<br />
2) further information can optionally be listed in the following fields.<br />
Adding them is strongly encouraged where appropriate.<br />
<br />
* status: pending, accepted in XXX, rejected (upstream)<br />
* origin: where the patch has been stolen ;-) <br />
* comment: any further detail such as description or reason for<br />
application of the patch<br />
<br />
Take a look at [http://cgit.openembedded.org/cgit.cgi?url=openembedded/tree/recipes/busybox/busybox-1.9.2/adduser-longops.patch an example]<br />
<br />
= Push'em-weekends =<br />
<br />
These are sprints in the spirit of our [[bug days|bug-squashing weekends]] when we try to <br />
push our patches to the upstream projects. The first such sprint was held <br />
on short notice from Friday, February 15th 2008 to Monday, the 18th. A few <br />
patches were already pushed upstream. Second sprint is scheduled for first weekend in August.<br />
<br />
Pushing our bugs upstream is beneficial for us (easier maintainability) and<br />
them (we give back our work). The following two commands can give you a <br />
list of patches still in need of being documented in line with above policy.<br />
<br />
find recipes/ \( -name '*.patch' -or -name '*.diff' \) -print0 | xargs -0 egrep -L \^upstream\:<br />
<br />
You can push those patches upstream even if you are only a normal user of <br />
OE. Let us know via the [http://bugs.openembedded.net bug tracker] if you have reported one of our patches<br />
upstream. Please be sure to test if the patch is still being applied<br />
to the most recent version of the package in OE.<br />
<br />
= sample text for upstream reports =<br />
<br />
Hi,<br />
<br />
thank you for sharing your work in $project. Openembedded.org includes<br />
recipes to cross-compile $project for a large number of target devices.<br />
<br />
I would like to make you aware of some of the changes that we at the <br />
openembedded.org project did to the sources you publish.<br />
<br />
Patch: http://cgit.openembedded.org/cgit.cgi?url=openembedded/tree/recipes/$project/$patch-url<br />
Comment: $explanation<br />
<br />
You can find all our patches for $project at <br />
http://cgit.openembedded.org/cgit.cgi?url=openembedded/tree/recipes/$project/<br />
<br />
Thank you again for your work.<br />
<br />
Regards<br />
<br />
$name<br />
<br />
[[Category:Policy]]</div>Laibschhttps://www.openembedded.org/index.php?title=Push_patches_upstream&diff=2132Push patches upstream2010-01-15T18:51:04Z<p>Laibsch: </p>
<hr />
<div>= Outline =<br />
<br />
OE has quite many patches that are just too valuable to keep to<br />
ourselves. OE encourages the following soft policy for adding patches<br />
to the repository.<br />
<br />
By the way, [http://patch-tracker.debian.org/ Debian], [[http://patches.ubuntu.com/ Ubuntu]], [http://sources.gentoo.org/viewcvs.py/gentoo-x86/ Gentoo] as well as [http://cvs.fedoraproject.org/viewvc/rpms/ Fedora] are of course always a great source for grabbing high-quality patches to include in OE.<br />
<br />
= Policy =<br />
<br />
1) first line in a patch starts with '''upstream:''' and goes on to list the<br />
URL where the bug has been reported upstream or "OE-only" if the patch <br />
is just a hack or applicable only to OE.<br />
2) further information can optionally be listed in the following fields.<br />
Adding them is strongly encouraged where appropriate.<br />
<br />
* status: pending, accepted in XXX, rejected (upstream)<br />
* origin: where the patch has been stolen ;-) <br />
* comment: any further detail such as description or reason for<br />
application of the patch<br />
<br />
Take a look at [http://cgit.openembedded.org/cgit.cgi?url=openembedded/tree/recipes/busybox/busybox-1.9.2/adduser-longops.patch an example]<br />
<br />
= Push'em-weekends =<br />
<br />
These are sprints in the spirit of our [[bug days|bug-squashing weekends]] when we try to <br />
push our patches to the upstream projects. The first such sprint was held <br />
on short notice from Friday, February 15th 2008 to Monday, the 18th. A few <br />
patches were already pushed upstream. Second sprint is scheduled for first weekend in August.<br />
<br />
Pushing our bugs upstream is beneficial for us (easier maintainability) and<br />
them (we give back our work). The following two commands can give you a <br />
list of patches still in need of being documented in line with above policy.<br />
<br />
find recipes/ \( -name '*.patch' -or -name '*.diff' \) -print0 | xargs -0 egrep -L \^upstream\:<br />
<br />
You can push those patches upstream even if you are only a normal user of <br />
OE. Let us know via the [http://bugs.openembedded.net bug tracker] if you have reported one of our patches<br />
upstream. Please be sure to test if the patch is still being applied<br />
to the most recent version of the package in OE.<br />
<br />
= sample text for upstream reports =<br />
<br />
Hi,<br />
<br />
thank you for sharing your work in $project. Openembedded.org includes<br />
recipes to cross-compile $project for a large number of target devices.<br />
<br />
I would like to make you aware of some of the changes that we at the <br />
openembedded.org project did to the sources you publish.<br />
<br />
Patch: http://cgit.openembedded.org/cgit.cgi?url=openembedded/tree/recipes/$project/$patch-url<br />
Comment: $explanation<br />
<br />
You can find all our patches for $project at <br />
http://cgit.openembedded.org/cgit.cgi?url=openembedded/tree/recipes/$project/<br />
<br />
Thank you again for your work.<br />
<br />
Regards<br />
<br />
$name<br />
<br />
[[Category:Policy]]</div>Laibschhttps://www.openembedded.org/index.php?title=Push_patches_upstream&diff=2131Push patches upstream2010-01-15T13:18:02Z<p>Laibsch: /* Policy */</p>
<hr />
<div>= Outline =<br />
<br />
OE has quite many patches that are just too valuable to keep to<br />
ourselves. OE encourages the following soft policy for adding patches<br />
to the repository.<br />
<br />
By the way, [http://patch-tracker.debian.org/ Debian], [http://sources.gentoo.org/viewcvs.py/gentoo-x86/ Gentoo] as well as [http://cvs.fedoraproject.org/viewvc/rpms/ Fedora] are of course always a great source for grabbing high-quality patches to include in OE.<br />
<br />
= Policy =<br />
<br />
1) first line in a patch starts with '''upstream:''' and goes on to list the<br />
URL where the bug has been reported upstream or "OE-only" if the patch <br />
is just a hack or applicable only to OE.<br />
2) further information can optionally be listed in the following fields.<br />
Adding them is strongly encouraged where appropriate.<br />
<br />
* status: pending, accepted in XXX, rejected (upstream)<br />
* origin: where the patch has been stolen ;-) <br />
* comment: any further detail such as description or reason for<br />
application of the patch<br />
<br />
Take a look at [http://cgit.openembedded.org/cgit.cgi?url=openembedded/tree/recipes/busybox/busybox-1.9.2/adduser-longops.patch an example]<br />
<br />
= Push'em-weekends =<br />
<br />
These are sprints in the spirit of our [[bug days|bug-squashing weekends]] when we try to <br />
push our patches to the upstream projects. The first such sprint was held <br />
on short notice from Friday, February 15th 2008 to Monday, the 18th. A few <br />
patches were already pushed upstream. Second sprint is scheduled for first weekend in August.<br />
<br />
Pushing our bugs upstream is beneficial for us (easier maintainability) and<br />
them (we give back our work). The following two commands can give you a <br />
list of patches still in need of being documented in line with above policy.<br />
<br />
find recipes/ \( -name '*.patch' -or -name '*.diff' \) -print0 | xargs -0 egrep -L \^upstream\:<br />
<br />
You can push those patches upstream even if you are only a normal user of <br />
OE. Let us know via the [http://bugs.openembedded.net bug tracker] if you have reported one of our patches<br />
upstream. Please be sure to test if the patch is still being applied<br />
to the most recent version of the package in OE.<br />
<br />
= sample text for upstream reports =<br />
<br />
Hi,<br />
<br />
thank you for sharing your work in $project. Openembedded.org includes<br />
recipes to cross-compile $project for a large number of target devices.<br />
<br />
I would like to make you aware of some of the changes that we at the <br />
openembedded.org project did to the sources you publish.<br />
<br />
Patch: http://cgit.openembedded.org/cgit.cgi?url=openembedded/tree/recipes/$project/$patch-url<br />
Comment: $explanation<br />
<br />
You can find all our patches for $project at <br />
http://cgit.openembedded.org/cgit.cgi?url=openembedded/tree/recipes/$project/<br />
<br />
Thank you again for your work.<br />
<br />
Regards<br />
<br />
$name<br />
<br />
[[Category:Policy]]</div>Laibschhttps://www.openembedded.org/index.php?title=Talk:Push_patches_upstream&diff=2130Talk:Push patches upstream2010-01-14T15:31:24Z<p>Laibsch: New page: As always, Debian has some very clever blueprints for this kind of thing: http://dep.debian.net/deps/dep3/</p>
<hr />
<div>As always, Debian has some very clever blueprints for this kind of thing: http://dep.debian.net/deps/dep3/</div>Laibschhttps://www.openembedded.org/index.php?title=Push_patches_upstream&diff=2129Push patches upstream2010-01-13T20:46:50Z<p>Laibsch: /* Outline */</p>
<hr />
<div>= Outline =<br />
<br />
OE has quite many patches that are just too valuable to keep to<br />
ourselves. OE encourages the following soft policy for adding patches<br />
to the repository.<br />
<br />
By the way, [http://patch-tracker.debian.org/ Debian], [http://sources.gentoo.org/viewcvs.py/gentoo-x86/ Gentoo] as well as [http://cvs.fedoraproject.org/viewvc/rpms/ Fedora] are of course always a great source for grabbing high-quality patches to include in OE.<br />
<br />
= Policy =<br />
<br />
1) first line in a patch starts with upstream: and goes on to list the<br />
URL where the bug has been reported upstream or "OE-only" if the patch <br />
is just a hack or applicable only to OE.<br />
2) further information can optionally be listed in the following fields.<br />
Adding them is strongly encouraged where appropriate.<br />
<br />
* status: pending, accepted in XXX, rejected (upstream)<br />
* origin: where the patch has been stolen ;-) <br />
* comment: any further detail such as description or reason for<br />
application of the patch<br />
<br />
Take a look at [http://cgit.openembedded.org/cgit.cgi?url=openembedded/tree/recipes/busybox/busybox-1.9.2/adduser-longops.patch an example]<br />
<br />
= Push'em-weekends =<br />
<br />
These are sprints in the spirit of our [[bug days|bug-squashing weekends]] when we try to <br />
push our patches to the upstream projects. The first such sprint was held <br />
on short notice from Friday, February 15th 2008 to Monday, the 18th. A few <br />
patches were already pushed upstream. Second sprint is scheduled for first weekend in August.<br />
<br />
Pushing our bugs upstream is beneficial for us (easier maintainability) and<br />
them (we give back our work). The following two commands can give you a <br />
list of patches still in need of being documented in line with above policy.<br />
<br />
find recipes/ \( -name '*.patch' -or -name '*.diff' \) -print0 | xargs -0 egrep -L \^upstream\:<br />
<br />
You can push those patches upstream even if you are only a normal user of <br />
OE. Let us know via the [http://bugs.openembedded.net bug tracker] if you have reported one of our patches<br />
upstream. Please be sure to test if the patch is still being applied<br />
to the most recent version of the package in OE.<br />
<br />
= sample text for upstream reports =<br />
<br />
Hi,<br />
<br />
thank you for sharing your work in $project. Openembedded.org includes<br />
recipes to cross-compile $project for a large number of target devices.<br />
<br />
I would like to make you aware of some of the changes that we at the <br />
openembedded.org project did to the sources you publish.<br />
<br />
Patch: http://cgit.openembedded.org/cgit.cgi?url=openembedded/tree/recipes/$project/$patch-url<br />
Comment: $explanation<br />
<br />
You can find all our patches for $project at <br />
http://cgit.openembedded.org/cgit.cgi?url=openembedded/tree/recipes/$project/<br />
<br />
Thank you again for your work.<br />
<br />
Regards<br />
<br />
$name<br />
<br />
[[Category:Policy]]</div>Laibschhttps://www.openembedded.org/index.php?title=Zaurus&diff=2127Zaurus2010-01-13T03:57:38Z<p>Laibsch: </p>
<hr />
<div>'''Technical information from [http://linuxtogo.org/gowiki/LinuxDevices LinuxDevices]'''<br />
<br />
* [http://linuxtogo.org/gowiki/ZaurusCollie collie]<br />
* [http://linuxtogo.org/gowiki/ZaurusPoodle poodle]<br />
* [http://linuxtogo.org/gowiki/ZaurusC7x0 c7x0] (corgi, shepherd, husky, boxer)<br />
* [http://linuxtogo.org/gowiki/ZaurusAkita akita]<br />
* [http://linuxtogo.org/gowiki/ZaurusSpitz spitz] (borzoi, terrier)<br />
* [http://linuxtogo.org/gowiki/ZaurusTosa tosa]<br />
<br />
'''kexecboot'''<br />
<br />
For the Zaurus a [http://projects.linuxtogo.org/mediawiki/index.php/Kexecboot special kernel+initramfs] has been developed.<br />
This special-purpose kernel is small enough to be flashed on NAND and features a framebuffer graphical menu for the selection of boot media containing the kernel to be kexec'ed in the second phase.<br />
<br />
Multi-partition cards and lots of filesystems are supported.<br />
The kernels to be launched are searched for in /boot of each available partition.<br />
There is a also a configuration file (/boot/boot.cfg) which allows selection of other kernels, custom kernel command lines, and specifies the label and the icon for each instance.<br />
<br />
'''How to install:'''<br />
<br />
Just unpack zaurus-installer-YOURMACHINE.tar.gz on a free (FAT or EXT2/3 formatted) partition: the package contains the kexecboot-kernel and the updater.sh utility. Then proceed as usual for flashing (switch off, pull battery out, insert battery again, before inserting AC plug press OK+Power On. In the Japanese Menu select 4 and finally 3 for SD card or 4 for CF).<br />
[http://downloads.conics.net/pda/zaurus-sl-c700/service-menus/maint-menu.jpg Screenshot]<br />
<br />
For the SL-5500 (collie) and optionally for other Zaurus too, flashing is possible just using the routines of the original firmware: <br />
reset the unit, Press C and D button during restart.<br />
See: [http://linuxtogo.org/gowiki/CollieInstall Flashing-collie]<br />
<br />
'''NOTE:'''<br />
<br />
If you want a rootfs in nand, this must be in the .jffs2 format. Just rename your-image-rootfs.jffs2 to initrd.bin and copy it on the card with updater.sh. The image will be flashed on mtd2.<br />
<br />
[[Category:Machine]]<br />
[[Category:User]]<br />
[[Category:FAQ]]</div>Laibschhttps://www.openembedded.org/index.php?title=Zaurus&diff=2126Zaurus2010-01-13T03:56:58Z<p>Laibsch: </p>
<hr />
<div>'''Technical information from [http://linuxtogo.org/gowiki/LinuxDevices LinuxDevices]'''<br />
<br />
* [http://linuxtogo.org/gowiki/ZaurusCollie collie]<br />
* [http://linuxtogo.org/gowiki/ZaurusPoodle poodle]<br />
* [http://linuxtogo.org/gowiki/ZaurusC7x0 c7x0] (corgi, shepherd, husky, boxer)<br />
* [http://linuxtogo.org/gowiki/ZaurusAkita akita]<br />
* [http://linuxtogo.org/gowiki/ZaurusSpitz spitz] (borzoi, terrier)<br />
* [http://linuxtogo.org/gowiki/ZaurusTosa tosa]<br />
<br />
'''kexecboot'''<br />
<br />
For the Zaurus a [http://wiki.openembedded.net/index.php/Push_patches_upstream special kernel+initramfs] has been developed.<br />
This special-purpose kernel is small enough to be flashed on NAND and features a framebuffer graphical menu for the selection of boot media containing the kernel to be kexec'ed in the second phase.<br />
<br />
Multi-partition cards and lots of filesystems are supported.<br />
The kernels to be launched are searched for in /boot of each available partition.<br />
There is a also a configuration file (/boot/boot.cfg) which allows selection of other kernels, custom kernel command lines, and specifies the label and the icon for each instance.<br />
<br />
'''How to install:'''<br />
<br />
Just unpack zaurus-installer-YOURMACHINE.tar.gz on a free (FAT or EXT2/3 formatted) partition: the package contains the kexecboot-kernel and the updater.sh utility. Then proceed as usual for flashing (switch off, pull battery out, insert battery again, before inserting AC plug press OK+Power On. In the Japanese Menu select 4 and finally 3 for SD card or 4 for CF).<br />
[http://downloads.conics.net/pda/zaurus-sl-c700/service-menus/maint-menu.jpg Screenshot]<br />
<br />
For the SL-5500 (collie) and optionally for other Zaurus too, flashing is possible just using the routines of the original firmware: <br />
reset the unit, Press C and D button during restart.<br />
See: [http://linuxtogo.org/gowiki/CollieInstall Flashing-collie]<br />
<br />
'''NOTE:'''<br />
<br />
If you want a rootfs in nand, this must be in the .jffs2 format. Just rename your-image-rootfs.jffs2 to initrd.bin and copy it on the card with updater.sh. The image will be flashed on mtd2.<br />
<br />
[[Category:Machine]]<br />
[[Category:User]]<br />
[[Category:FAQ]]</div>Laibschhttps://www.openembedded.org/index.php?title=Zaurus&diff=2125Zaurus2010-01-13T03:56:43Z<p>Laibsch: </p>
<hr />
<div>'''Technical information from [http://linuxtogo.org/gowiki/LinuxDevices LinuxDevices]'''<br />
<br />
* [http://linuxtogo.org/gowiki/ZaurusCollie collie]<br />
* [http://linuxtogo.org/gowiki/ZaurusPoodle poodle]<br />
* [http://linuxtogo.org/gowiki/ZaurusC7x0 c7x0] (corgi, shepherd, husky, boxer)<br />
* [http://linuxtogo.org/gowiki/ZaurusAkita akita]<br />
* [http://linuxtogo.org/gowiki/ZaurusSpitz spitz] (borzoi, terrier)<br />
* [http://linuxtogo.org/gowiki/ZaurusTosa tosa]<br />
<br />
'''kexecboot'''<br />
<br />
For the Zaurus a [[http://wiki.openembedded.net/index.php/Push_patches_upstream special kernel+initramfs]] has been developed.<br />
This special-purpose kernel is small enough to be flashed on NAND and features a framebuffer graphical menu for the selection of boot media containing the kernel to be kexec'ed in the second phase.<br />
<br />
Multi-partition cards and lots of filesystems are supported.<br />
The kernels to be launched are searched for in /boot of each available partition.<br />
There is a also a configuration file (/boot/boot.cfg) which allows selection of other kernels, custom kernel command lines, and specifies the label and the icon for each instance.<br />
<br />
'''How to install:'''<br />
<br />
Just unpack zaurus-installer-YOURMACHINE.tar.gz on a free (FAT or EXT2/3 formatted) partition: the package contains the kexecboot-kernel and the updater.sh utility. Then proceed as usual for flashing (switch off, pull battery out, insert battery again, before inserting AC plug press OK+Power On. In the Japanese Menu select 4 and finally 3 for SD card or 4 for CF).<br />
[http://downloads.conics.net/pda/zaurus-sl-c700/service-menus/maint-menu.jpg Screenshot]<br />
<br />
For the SL-5500 (collie) and optionally for other Zaurus too, flashing is possible just using the routines of the original firmware: <br />
reset the unit, Press C and D button during restart.<br />
See: [http://linuxtogo.org/gowiki/CollieInstall Flashing-collie]<br />
<br />
'''NOTE:'''<br />
<br />
If you want a rootfs in nand, this must be in the .jffs2 format. Just rename your-image-rootfs.jffs2 to initrd.bin and copy it on the card with updater.sh. The image will be flashed on mtd2.<br />
<br />
[[Category:Machine]]<br />
[[Category:User]]<br />
[[Category:FAQ]]</div>Laibschhttps://www.openembedded.org/index.php?title=Zaurus&diff=2124Zaurus2010-01-13T03:39:42Z<p>Laibsch: </p>
<hr />
<div>'''Technical information from [http://linuxtogo.org/gowiki/LinuxDevices LinuxDevices]'''<br />
<br />
* [http://linuxtogo.org/gowiki/ZaurusCollie collie]<br />
* [http://linuxtogo.org/gowiki/ZaurusPoodle poodle]<br />
* [http://linuxtogo.org/gowiki/ZaurusC7x0 c7x0] (corgi, shepherd, husky, boxer)<br />
* [http://linuxtogo.org/gowiki/ZaurusAkita akita]<br />
* [http://linuxtogo.org/gowiki/ZaurusSpitz spitz] (borzoi, terrier)<br />
* [http://linuxtogo.org/gowiki/ZaurusTosa tosa]<br />
<br />
'''kexecboot'''<br />
<br />
For the Zaurus a special kernel+initramfs has been developed.<br />
This special-purpose kernel is small enough to be flashed on NAND and features a framebuffer graphical menu for the selection of boot media containing the kernel to be kexec'ed in the second phase.<br />
<br />
Multi-partition cards and lots of filesystems are supported.<br />
The kernels to be launched are searched for in /boot of each available partition.<br />
There is a also a configuration file (/boot/boot.cfg) which allows selection of other kernels, custom kernel command lines, and specifies the label and the icon for each instance.<br />
<br />
'''How to install:'''<br />
<br />
Just unpack zaurus-installer-YOURMACHINE.tar.gz on a free (FAT or EXT2/3 formatted) partition: the package contains the kexecboot-kernel and the updater.sh utility. Then proceed as usual for flashing (switch off, pull battery out, insert battery again, before inserting AC plug press OK+Power On. In the Japanese Menu select 4 and finally 3 for SD card or 4 for CF).<br />
[http://downloads.conics.net/pda/zaurus-sl-c700/service-menus/maint-menu.jpg Screenshot]<br />
<br />
For the SL-5500 (collie) and optionally for other Zaurus too, flashing is possible just using the routines of the original firmware: <br />
reset the unit, Press C and D button during restart.<br />
See: [http://linuxtogo.org/gowiki/CollieInstall Flashing-collie]<br />
<br />
'''NOTE:'''<br />
<br />
If you want a rootfs in nand, this must be in the .jffs2 format. Just rename your-image-rootfs.jffs2 to initrd.bin and copy it on the card with updater.sh. The image will be flashed on mtd2.<br />
<br />
[[Category:Machine]]<br />
[[Category:User]]<br />
[[Category:FAQ]]</div>Laibschhttps://www.openembedded.org/index.php?title=Zaurus&diff=2123Zaurus2010-01-13T02:42:05Z<p>Laibsch: </p>
<hr />
<div>'''Technical information from [http://linuxtogo.org/gowiki/LinuxDevices LinuxDevices]'''<br />
<br />
* [http://linuxtogo.org/gowiki/ZaurusCollie collie]<br />
* [http://linuxtogo.org/gowiki/ZaurusPoodle poodle]<br />
* [http://linuxtogo.org/gowiki/ZaurusC7x0 c7x0] (corgi, shepherd, husky, boxer)<br />
* [http://linuxtogo.org/gowiki/ZaurusAkita akita]<br />
* [http://linuxtogo.org/gowiki/ZaurusSpitz spitz] (borzoi, terrier)<br />
* [http://linuxtogo.org/gowiki/ZaurusTosa tosa]<br />
<br />
'''kexecboot'''<br />
<br />
For the Zaurus a special kernel+initramfs has been developed.<br />
This special-purpose kernel is small enough to be flashed on NAND and features a framebuffer graphical menu for the selection of boot media containing the kernel to be kexec'ed ub the second phase.<br />
<br />
Multi-partition cards and lots of filesystems are supported.<br />
The kernels to be launched are searched for in /boot of each available partition.<br />
There is a also a configuration file (/boot/boot.cfg) which allows selection of other kernels, custom kernel command lines, and specifies the label and the icon for each instance.<br />
<br />
'''How to install:'''<br />
<br />
Just unpack zaurus-installer-YOURMACHINE.tar.gz on a free (FAT or EXT2/3 formatted) partition: the package contains the kexecboot-kernel and the updater.sh utility. Then proceed as usual for flashing (switch off, pull battery out, insert battery again, before inserting AC plug press OK+Power On. In the Japanese Menu select 4 and finally 3 for SD card or 4 for CF).<br />
[http://downloads.conics.net/pda/zaurus-sl-c700/service-menus/maint-menu.jpg Screenshot]<br />
<br />
For the SL-5500 (collie) and optionally for other Zaurus too, flashing is possible just using the routines of the original firmware: <br />
reset the unit, Press C and D button during restart.<br />
See: [http://linuxtogo.org/gowiki/CollieInstall Flashing-collie]<br />
<br />
'''NOTE:'''<br />
<br />
If you want a rootfs in nand, this must be in the .jffs2 format. Just rename your-image-rootfs.jffs2 to initrd.bin and copy it on the card with updater.sh. The image will be flashed on mtd2.<br />
<br />
[[Category:Machine]]<br />
[[Category:User]]<br />
[[Category:FAQ]]</div>Laibschhttps://www.openembedded.org/index.php?title=Zaurus&diff=2122Zaurus2010-01-13T02:40:55Z<p>Laibsch: </p>
<hr />
<div>'''Technical information from [http://linuxtogo.org/gowiki/LinuxDevices LinuxDevices]'''<br />
<br />
* [http://linuxtogo.org/gowiki/ZaurusCollie collie]<br />
* [http://linuxtogo.org/gowiki/ZaurusPoodle poodle]<br />
* [http://linuxtogo.org/gowiki/ZaurusC7x0 c7x0] (corgi, shepherd, husky, boxer)<br />
* [http://linuxtogo.org/gowiki/ZaurusAkita akita]<br />
* [http://linuxtogo.org/gowiki/ZaurusSpitz spitz] (borzoi, terrier)<br />
* [http://linuxtogo.org/gowiki/ZaurusTosa tosa]<br />
<br />
'''kexecboot'''<br />
<br />
For the Zaurus a special kernel+initramfs has been developed.<br />
This special-purpose kernel is small enough to be flashed on NAND and features a framebuffer graphical menu for the selection of boot media containing the kernel to be kexec'ed ub the second phase.<br />
<br />
Multi-partition cards and lots of filesystems are supported.<br />
The kernels to be launched are searched for in /boot of each available partition.<br />
There is a also a configuration file (/boot/boot.cfg) which allows selection of other kernels, custom kernel command lines, and specifies the label and the icon for each instance.<br />
<br />
'''How to install:'''<br />
<br />
Just unpack zaurus-installer-YOURMACHINE.tar.gz on a free (FAT or EXT2/3 formatted) partition: the package contains the kexecboot-kernel and the updater.sh utility. Then proceed as usual for flashing (switch off, pull battery out, insert battery again, before inserting AC plug press OK+Power On. In the Japanese Menu select 4 and finally 3 for SD card or 4 for CF).<br />
[http://downloads.conics.net/pda/zaurus-sl-c700/service-menus/maint-menu.jpg Screenshot]<br />
<br />
For the SL-5500 (collie) and optionally for other Zaurus too, flashing is possible just using the routines of the original firmware: <br />
reset the unit, Press C and D button during restart.<br />
See: [http://linuxtogo.org/gowiki/CollieInstall Flashing-collie]<br />
<br />
'''NOTE:'''<br />
<br />
If you want a rootfs in nand, this must be in the .jffs2 format. Just rename your-image-rootfs.jffs2 to initrd.bin and copy it on the card with updater.sh. The image will be flashed on mtd2.<br />
<br />
[[Category:Machine]]</div>Laibschhttps://www.openembedded.org/index.php?title=Category:OEDEM&diff=2119Category:OEDEM2010-01-11T15:48:54Z<p>Laibsch: Reverted edits by Glenn (Talk); changed back to last version by Laibsch</p>
<hr />
<div>OE Developper meetings - see you in the real world<br />
<br />
planning and documentation</div>Laibschhttps://www.openembedded.org/index.php?title=Oedem/2009_TSC_election&diff=2117Oedem/2009 TSC election2010-01-10T16:56:43Z<p>Laibsch: </p>
<hr />
<div>At Oedem/2009 the following people have been proposed for the TSC, but that has nothing to do with the proper proposing protocol, so you can safely ignore this page.<br />
<br />
* '''Phil Blundell'''<br />
<br />
: ''(Nominated by Stefan Schmidt)''<br />
<br />
: Both Holger an Phil have an deep understanding on how OE and bitbake work and was designed to work. Both are thinking about ways to further improve the current situation and contribute code and ideas to reach the goals. Maybe even more important are the way they deal with people who want to contribute. They listen, workout the underlying problems and then helping these people to reach their goals.<br />
<br />
* '''Holger Freyther'''<br />
<br />
: ''(Nominated by Stefan Schmidt)''<br />
<br />
: Both Holger an Phil have an deep understanding on how OE and bitbake work and was designed to work. Both are thinking about ways to furtehr improve the current situation and contribute code and ideas to reach the goals. Maybe even more important are the way they deal with people who want to contribute. They listen, workout the underlying problems and then helping these people to reach their goals.<br />
<br />
* '''Chris Larson'''<br />
<br />
: ''(Nominated by Phil Blundell)''<br />
<br />
* '''Mickey Lauer'''<br />
<br />
: As one of the founders of the OE project I have lots of experience with all parts of the system, including the BitBake core, the build classes, and the recipes. In fact, I have contributed a major part of all that.<br />
<br />
: I have left the former core team since this failed to provide any transparency to the growing OE community about how decisions were made.<br />
<br />
: I have also used OE in commercial projects, hence I know about the different -- and sometimes contradicting -- requirements non-commercial and commercial projects have. I have always tried to improve OE in a way that suits as much stakeholders as possible, trying to prevent isolated solutions. As such, I'd love to serve on the TSC helping to facilitate further OE development. <br />
<br />
* '''Richard Purdie'''<br />
<br />
: I'm a long standing OE developer and member of the community who has extensive experience with the core elements of the system having successfully developed and handled many significant OE architectural improvements. My role as the lead developer and maintainer of bitbake gives me insight into the core workings of the project and as the architect of Poky, I also understand the needs of derived projects. As part of the former 'core team' I've also experience in mediation and in guiding the project. I'd like to use this experience for the benefit of the TSC.<br />
<br />
: ''(Richard was also nominated by Stefan Schmidt.)''<br />
<br />
* '''Khem Raj'''<br />
<br />
: I would like to nominate myself. Over the last couple of years I have got good understanding of OE's internals and From my experience in past I understand needs of embedded systems and embedded Linux in particularly well. I think I understand the core pieces of OE well now which will help me make right decisions and suggestions in the TSC especially in the areas of toolchain and system libraries.<br />
<br />
[[Category:OEDEM]]</div>Laibschhttps://www.openembedded.org/index.php?title=Oedem/2010&diff=2116Oedem/20102010-01-10T16:56:31Z<p>Laibsch: </p>
<hr />
<div>OpenEmbedded Developers' Meeting 2010 will be in XXX, YY on the weekend of ZZZ.<br />
<br />
All developers and other interested parties are welcome.<br />
<br />
== Location ==<br />
<br />
Call ... if you get hopelessly lost.<br />
<br />
== Registration ==<br />
<br />
Due to restricted space at the venue, the number of attendees is strictly limited.<br />
<br />
== Agenda ==<br />
<br />
=== Friday ===<br />
<br />
...<br />
<br />
=== Saturday ===<br />
<br />
...<br />
<br />
=== Sunday ===<br />
<br />
...<br />
<br />
==Travel==<br />
<br />
...<br />
<br />
<br />
==Accommodation==<br />
<br />
The nearest full-service hotel is ...<br />
<br />
Cheapest accomodation is ...<br />
<br />
==Food and drink==<br />
<br />
...<br />
<br />
==Attending for sure==<br />
<br />
...<br />
<br />
[[Category:OEDEM]]</div>Laibschhttps://www.openembedded.org/index.php?title=ToolingUseCases&diff=2115ToolingUseCases2010-01-10T16:56:05Z<p>Laibsch: </p>
<hr />
<div>= Overview =<br />
<br />
This page defines primary user-roles in using OpenEmbedded. The material resulted from some discussions at OEDEM that were truncated due to time restrictions.<br />
<br />
= Goals =<br />
<br />
The goal of identifying user-roles is to be able to categorize different tooling scenarios, and what types of users will be interested in specific features. Tools designed for role type may not be appropriate for other roles. For example, a GUI for recipe editing may not be helpful for an application developer that's looking to remote debug their application on a target. On the other hand, a simple press-button build GUI may not be interesting for a seasoned OE hacker.<br />
<br />
= Role Types =<br />
<br />
== Application Developer ==<br />
<br />
The application developer's main concern is developing and testing any given application on a target system. This person does not care nor want to learn much about the internal details of the build system or package metadata. The best possible case is that these systems are transparent and the developer is able to easily build and deploy applications to the target device.<br />
<br />
=== Primary Tooling Requirements ===<br />
<br />
* Build Application for Target<br />
* Debug Application on Target<br />
* Generate build system artifacts for Application (recipes)<br />
<br />
=== Ideas ===<br />
<br />
* Develop an Eclipse plugin to "Export project as Recipe"<br />
** For CDT (C/C++) projects make, automake recipes are generated<br />
** For Java projects java-library based recipies are generated<br />
** Python?<br />
** Initially wizard can just create a tarball of project sources<br />
** Integration with SCM plugins?<br />
** How to capture project dependencies?<br />
** How to define export target? OTE, cloud, etc.?<br />
<br />
== Distro Developer ==<br />
<br />
Distro developer's concern is to compose packages and configurations into a working system. The distro developer has deep knowledge of packages available in Linux, and how sets of packages work well together. Additionally the distro developer is not afraid to work deeply within the build system to make it better, and to produce better, more maintainable package metadata and target systems.<br />
<br />
=== Primary Tooling Requirements ===<br />
<br />
* Build system image <br />
* Create/edit distro definitions<br />
* Debug build problems<br />
* Visualize package dependencies<br />
<br />
== Package Developer ==<br />
<br />
The package developer is often a mix of the previous two role types. Often they have some knowledge of the build system and applications and build tools used to create those applications. They typically act as a bridge between pure application developers and the resulting target system that's produced. Package developers write recipes, debug applications, and debug build problems.<br />
<br />
=== Primary Tooling Requirements ===<br />
<br />
* Create and edit package metadata<br />
* Easily integrate package metadata into build system<br />
* Debug build issues<br />
* Visualize Package Dependencies<br />
<br />
=== Notes ===<br />
<br />
* OpenEmbedded Tools for Eclipse (OTE) was designed for this role type.<br />
<br />
== Target System User ==<br />
<br />
This role type typically is not exposed to package metadata, cross compilers, or build systems. They are system users, and as such, at times want to:<br />
<br />
* Generate system<br />
* Update system<br />
* Install packages<br />
* Configure package metadata<br />
<br />
=== Primary Tooling Requirements ===<br />
<br />
* install binary package on target<br />
* find new packages and package updates for target<br />
* resolve package dependencies<br />
<br />
=== Ideas ===<br />
<br />
* A GUI application that runs with a local install of OE that can<br />
** present a wizard style interface that allows users to build system images<br />
** download overlays and other non-default artifacts<br />
** select images, packages, distros, machines, etc.<br />
** have a simple 'installer' that does not require knowledge of bitbake/OE internals<br />
<br />
[[Category:OEDEM]]</div>Laibschhttps://www.openembedded.org/index.php?title=Online_Voting_Policy&diff=2114Online Voting Policy2010-01-10T16:50:09Z<p>Laibsch: </p>
<hr />
<div>Rules of Procedures for Online Voting<br />
<br />
The articles of association of the OpenEmbedded e.V. provide that certain decisions can be taken by online voting. This includes voting about new members and deciding about certain rules of procedures. In addition the OpenEmbedded e.V. allows to use online voting for decisions which aren't covered in the articles of association. There are several different types of votes which slightly differ in procedure and method to calculate results. These rules regulate the procedure of online votes and how results are calculated. The intention of these rules is to provide a fair and pragmatic way to let the OpenEmbedded e.V. take decisions by online voting.<br />
<br />
=Voting Administrators=<br />
<br />
The board of the OpenEmbedded e.V. assigns one or more voting administrators which are responsible for technically performing the voting. This includes sending out the ballots, receiving the votes, calculating and publishing the results.<br />
<br />
The voting administrators must not disclose any information about the identity of the voters or any other information which isn't contained in the published voting results.<br />
<br />
=General procedure for online voting=<br />
<br />
An online voting is initiated by a voting proposal followed by a discussion period. After the discussion period the voting period is started. The voting is finished by calculating and publishing the voting results.<br />
<br />
Results of online votes are effective immediately following publication of the results unless otherwise stated in the voting proposal.<br />
<br />
==Voting Proposal==<br />
<br />
An online voting is initiated by a proposal for voting which states the subject of the voting. The proposal is sent by email to the membership mailing list and has to include exact and complete information what is voted upon. Only the information which is directly included in the mail sent as voting proposal is subject of the voting.<br />
<br />
The voting proposal email has to explicitly be marked as voting proposal by starting the email subject line with the string "Voting Proposal:".<br />
<br />
Any active member can initiate a voting by sending a voting proposal.<br />
<br />
The member who has initiated a vote can retract the voting proposal by sending an email to the membership list stating the intention to retract the proposal.<br />
<br />
A proposal can only be retracted within the discussion period.<br />
<br />
==Discussion Period==<br />
<br />
The discussion period begins on the date the membership mailing list receives the voting proposal. Unless specified otherwise in the procedures for the specific type of vote (see: Types of Votes), the discussion period lasts for two weeks. The discussion period should be used to discuss the voting and form opinions about the options which are available for voting.<br />
<br />
==Start of Voting==<br />
<br />
When the discussion period has finished the voting is started by sending ballots to all active members. The ballots should include the text of the proposal which is voted about.<br />
<br />
==Voting Period==<br />
<br />
The voting period is started by sending out the ballots. Unless specified otherwise in the procedures for the specific type of vote (see: Types of Votes), the voting period lasts for two weeks. During the voting period the active members cast their votes. Only votes cast within the voting period are considered for the results of the voting.<br />
<br />
==End of Voting==<br />
<br />
After the voting period all cast votes are counted and the results of the voting are published.<br />
<br />
The results of a vote are published to the OpenEmbedded e.V. membership by sending them to the membership mailing list. They have to include the number of persons permitted to vote, the total number of votes, and the number of votes for each available voting option. The results should also include a statement, if the voting was valid according to section 5.<br />
<br />
=Types of Votes=<br />
<br />
There are three types of votes: Votes about new members (3.1), elections of groups of people (3.2), votes for decision (3.3).<br />
<br />
==Voting about new members==<br />
<br />
The discussion period is started by sending a new member proposal to the membership mailing list. Within the discussion period at least two other members have to declare their support for the vote, otherwise the proposal is considered to be rejected. If two members declare their support the voting is started after the discussion period.<br />
<br />
The discussion period has a duration of one week and is extended to two weeks, if requested by a member.<br />
<br />
The voting period has a duration of one week.<br />
<br />
For new member votes there are three options: "Yes", "No", "Abstention". The new member is accepted, if there are more "Yes" than "No" votes and the vote isn't invalid according to section 5.<br />
<br />
==Electing groups of persons==<br />
<br />
For elections of groups of people there is an additional candidacy period before the voting proposal is sent. The person responsible for the execution of the voting sends a call for candidates to the membership mailing list which starts the candidacy period. If there is no explicit rule about who is responsible for execution of the voting, the board of the e.V. is responsible.<br />
<br />
The candidacy period lasts two weeks. All members who declare their candidacy in a statement sent to the membership list become candidates for the election.<br />
<br />
After the candidacy period the list of candidates is sent as voting proposal. This starts the two-weeks discussion period.<br />
<br />
The candidates are voted on as options according to section 3.4.<br />
<br />
==Voting about decisions==<br />
<br />
The OpenEmbedded e.V. can officially take decisions or decide about official statements on request of at least three active member. One member has to send the voting proposal to the membership mailing list. This starts the discussion period. Within the discussion period at least two other members have to declare their support for the vote, otherwise the proposal is considered to be rejected. If two members declare their support the voting is started after the discussion period.<br />
<br />
The responsible party for execution of the voting sends the voting proposal which includes all options. This starts the discussion period.<br />
<br />
After the discussion period the voting is started. The options are voted on according to section 3.4.<br />
<br />
==Voting System==<br />
===Multiple options===<br />
<br />
If there are more than two options (excluding abstention), the following voting system shall be used:<br />
<br />
The members are asked to rank the options in terms of their preference into a ballot. A ballot may contain two options of the same rank. All options must be ranked. Each member may make up to one ballot.<br />
<br />
The winners are found by:<br />
<br />
1. Given two options A and B, V(A,B) is the number of voters who prefer option A over option B.<br />
2. From the list of options, we generate a list of pairwise defeats.<br />
* An option A defeats an option B, if V(A,B) is strictly greater than V(B,A).<br />
3. From the list of pairwise defeats, we generate a set of transitive defeats.<br />
* An option A transitively defeats an option C if A defeats C or if there is some other option B where A defeats B AND B transitively defeats C.<br />
4. We construct the Schwartz set from the set of transitive defeats.<br />
* An option A is in the Schwartz set if for all options B, either A transitively defeats B, or B does not transitively defeat A.<br />
5. If there are defeats between options in the Schwartz set, we drop the weakest such defeats from the list of pairwise defeats, and return to step (iii).<br />
* A defeat (A,X) is weaker than a defeat (B,Y) if V(A,X) is less than V(B,Y). Also, (A,X) is weaker than (B,Y) if V(A,X) is equal to V(B,Y) and V(X,A) is greater than V(Y,B).<br />
* A weakest defeat is a defeat that has no other defeat weaker than it. There may be more than one such defeat.<br />
6. If the number of options in the Schwartz set does not exceed the number of required winners, then the winners are the Schwartz set. If the number of members of the Schwartz set exceeds the number of required winners, the board chooses which of the members of the Schwartz set wins.<br />
7. If this results in an insufficient number of winners, then the candidates which have already won according to step (vi) should be removed from the list of options, and then this procedure is repeated from step (i).<br />
<br />
Parts of this section are copied from the Constitution for the Debian Project (v1.4), http://www.debian.org/devel/constitution<br />
<br />
===Two options===<br />
<br />
If the number of options is exactly two (excluding abstension), then:<br />
<br />
* Each active member can vote with "Yes", "No" or "Abstain".<br />
* If there are more "Yes" than "No" votes and the vote isn't invalid according to section 5, the decision is accepted.<br />
<br />
=Right to vote=<br />
<br />
All members of the OpenEmbedded e.V. which are active members at the time the voting period is started have the right to cast a vote. The prerequisite for taking part in online votes is a valid email address in the member database. The member is solely responsible for initially setting and updating his email address in the member database.<br />
<br />
=Quorum=<br />
<br />
The result of a voting only becomes effective when the number of votes which have chosen an option different from "Abstention" is greater than 20 percent of the number of active members. If this quorum isn't reached the voting is considered invalid. An invalid voting can be repeated, but not before a period of four weeks has passed between publishing the results of the invalid vote and the proposal for the repeated voting.<br />
<br />
=Anonymity=<br />
<br />
Online votes are anonymous. The information which members participated in the vote and for which option they voted aren't disclosed. The voting administrators are allowed to track this information for technically executing the vote. The information mustn't be used for other purposes and mustn't be made available to any other people.<br />
<br />
=Publication of voting results=<br />
<br />
All voting results except for rejected votes about new members are published on the OpenEmbedded e.V. web site, excluding the exact numbers of votes.<br />
<br />
=Modification of voting procedure=<br />
<br />
The board may modify the voting procedures for individual votes upon request of the e.V. membership if good reason for the change, as determined by the good judgment of the board, is provided.<br />
<br />
[[Category:Verein]]</div>Laibschhttps://www.openembedded.org/index.php?title=Online_Voting_Policy&diff=2113Online Voting Policy2010-01-10T16:49:43Z<p>Laibsch: Reverted edits by Glenn (Talk); changed back to last version by XorA</p>
<hr />
<div>Rules of Procedures for Online Voting<br />
<br />
The articles of association of the OpenEmbedded e.V. provide that certain decisions can be taken by online voting. This includes voting about new members and deciding about certain rules of procedures. In addition the OpenEmbedded e.V. allows to use online voting for decisions which aren't covered in the articles of association. There are several different types of votes which slightly differ in procedure and method to calculate results. These rules regulate the procedure of online votes and how results are calculated. The intention of these rules is to provide a fair and pragmatic way to let the OpenEmbedded e.V. take decisions by online voting.<br />
<br />
=Voting Administrators=<br />
<br />
The board of the OpenEmbedded e.V. assigns one or more voting administrators which are responsible for technically performing the voting. This includes sending out the ballots, receiving the votes, calculating and publishing the results.<br />
<br />
The voting administrators must not disclose any information about the identity of the voters or any other information which isn't contained in the published voting results.<br />
<br />
=General procedure for online voting=<br />
<br />
An online voting is initiated by a voting proposal followed by a discussion period. After the discussion period the voting period is started. The voting is finished by calculating and publishing the voting results.<br />
<br />
Results of online votes are effective immediately following publication of the results unless otherwise stated in the voting proposal.<br />
<br />
==Voting Proposal==<br />
<br />
An online voting is initiated by a proposal for voting which states the subject of the voting. The proposal is sent by email to the membership mailing list and has to include exact and complete information what is voted upon. Only the information which is directly included in the mail sent as voting proposal is subject of the voting.<br />
<br />
The voting proposal email has to explicitly be marked as voting proposal by starting the email subject line with the string "Voting Proposal:".<br />
<br />
Any active member can initiate a voting by sending a voting proposal.<br />
<br />
The member who has initiated a vote can retract the voting proposal by sending an email to the membership list stating the intention to retract the proposal.<br />
<br />
A proposal can only be retracted within the discussion period.<br />
<br />
==Discussion Period==<br />
<br />
The discussion period begins on the date the membership mailing list receives the voting proposal. Unless specified otherwise in the procedures for the specific type of vote (see: Types of Votes), the discussion period lasts for two weeks. The discussion period should be used to discuss the voting and form opinions about the options which are available for voting.<br />
<br />
==Start of Voting==<br />
<br />
When the discussion period has finished the voting is started by sending ballots to all active members. The ballots should include the text of the proposal which is voted about.<br />
<br />
==Voting Period==<br />
<br />
The voting period is started by sending out the ballots. Unless specified otherwise in the procedures for the specific type of vote (see: Types of Votes), the voting period lasts for two weeks. During the voting period the active members cast their votes. Only votes cast within the voting period are considered for the results of the voting.<br />
<br />
==End of Voting==<br />
<br />
After the voting period all cast votes are counted and the results of the voting are published.<br />
<br />
The results of a vote are published to the OpenEmbedded e.V. membership by sending them to the membership mailing list. They have to include the number of persons permitted to vote, the total number of votes, and the number of votes for each available voting option. The results should also include a statement, if the voting was valid according to section 5.<br />
<br />
=Types of Votes=<br />
<br />
There are three types of votes: Votes about new members (3.1), elections of groups of people (3.2), votes for decision (3.3).<br />
<br />
==Voting about new members==<br />
<br />
The discussion period is started by sending a new member proposal to the membership mailing list. Within the discussion period at least two other members have to declare their support for the vote, otherwise the proposal is considered to be rejected. If two members declare their support the voting is started after the discussion period.<br />
<br />
The discussion period has a duration of one week and is extended to two weeks, if requested by a member.<br />
<br />
The voting period has a duration of one week.<br />
<br />
For new member votes there are three options: "Yes", "No", "Abstention". The new member is accepted, if there are more "Yes" than "No" votes and the vote isn't invalid according to section 5.<br />
<br />
==Electing groups of persons==<br />
<br />
For elections of groups of people there is an additional candidacy period before the voting proposal is sent. The person responsible for the execution of the voting sends a call for candidates to the membership mailing list which starts the candidacy period. If there is no explicit rule about who is responsible for execution of the voting, the board of the e.V. is responsible.<br />
<br />
The candidacy period lasts two weeks. All members who declare their candidacy in a statement sent to the membership list become candidates for the election.<br />
<br />
After the candidacy period the list of candidates is sent as voting proposal. This starts the two-weeks discussion period.<br />
<br />
The candidates are voted on as options according to section 3.4.<br />
<br />
==Voting about decisions==<br />
<br />
The OpenEmbedded e.V. can officially take decisions or decide about official statements on request of at least three active member. One member has to send the voting proposal to the membership mailing list. This starts the discussion period. Within the discussion period at least two other members have to declare their support for the vote, otherwise the proposal is considered to be rejected. If two members declare their support the voting is started after the discussion period.<br />
<br />
The responsible party for execution of the voting sends the voting proposal which includes all options. This starts the discussion period.<br />
<br />
After the discussion period the voting is started. The options are voted on according to section 3.4.<br />
<br />
==Voting System==<br />
===Multiple options===<br />
<br />
If there are more than two options (excluding abstention), the following voting system shall be used:<br />
<br />
The members are asked to rank the options in terms of their preference into a ballot. A ballot may contain two options of the same rank. All options must be ranked. Each member may make up to one ballot.<br />
<br />
The winners are found by:<br />
<br />
1. Given two options A and B, V(A,B) is the number of voters who prefer option A over option B.<br />
2. From the list of options, we generate a list of pairwise defeats.<br />
* An option A defeats an option B, if V(A,B) is strictly greater than V(B,A).<br />
3. From the list of pairwise defeats, we generate a set of transitive defeats.<br />
* An option A transitively defeats an option C if A defeats C or if there is some other option B where A defeats B AND B transitively defeats C.<br />
4. We construct the Schwartz set from the set of transitive defeats.<br />
* An option A is in the Schwartz set if for all options B, either A transitively defeats B, or B does not transitively defeat A.<br />
5. If there are defeats between options in the Schwartz set, we drop the weakest such defeats from the list of pairwise defeats, and return to step (iii).<br />
* A defeat (A,X) is weaker than a defeat (B,Y) if V(A,X) is less than V(B,Y). Also, (A,X) is weaker than (B,Y) if V(A,X) is equal to V(B,Y) and V(X,A) is greater than V(Y,B).<br />
* A weakest defeat is a defeat that has no other defeat weaker than it. There may be more than one such defeat.<br />
6. If the number of options in the Schwartz set does not exceed the number of required winners, then the winners are the Schwartz set. If the number of members of the Schwartz set exceeds the number of required winners, the board chooses which of the members of the Schwartz set wins.<br />
7. If this results in an insufficient number of winners, then the candidates which have already won according to step (vi) should be removed from the list of options, and then this procedure is repeated from step (i).<br />
<br />
Parts of this section are copied from the Constitution for the Debian Project (v1.4), http://www.debian.org/devel/constitution<br />
<br />
===Two options===<br />
<br />
If the number of options is exactly two (excluding abstension), then:<br />
<br />
* Each active member can vote with "Yes", "No" or "Abstain".<br />
* If there are more "Yes" than "No" votes and the vote isn't invalid according to section 5, the decision is accepted.<br />
<br />
=Right to vote=<br />
<br />
All members of the OpenEmbedded e.V. which are active members at the time the voting period is started have the right to cast a vote. The prerequisite for taking part in online votes is a valid email address in the member database. The member is solely responsible for initially setting and updating his email address in the member database.<br />
<br />
=Quorum=<br />
<br />
The result of a voting only becomes effective when the number of votes which have chosen an option different from "Abstention" is greater than 20 percent of the number of active members. If this quorum isn't reached the voting is considered invalid. An invalid voting can be repeated, but not before a period of four weeks has passed between publishing the results of the invalid vote and the proposal for the repeated voting.<br />
<br />
=Anonymity=<br />
<br />
Online votes are anonymous. The information which members participated in the vote and for which option they voted aren't disclosed. The voting administrators are allowed to track this information for technically executing the vote. The information mustn't be used for other purposes and mustn't be made available to any other people.<br />
<br />
=Publication of voting results=<br />
<br />
All voting results except for rejected votes about new members are published on the OpenEmbedded e.V. web site, excluding the exact numbers of votes.<br />
<br />
=Modification of voting procedure=<br />
<br />
The board may modify the voting procedures for individual votes upon request of the e.V. membership if good reason for the change, as determined by the good judgment of the board, is provided.</div>Laibschhttps://www.openembedded.org/index.php?title=Oedem2007&diff=2112Oedem20072010-01-10T16:49:20Z<p>Laibsch: </p>
<hr />
<div>==Venue==<br />
<br />
GMIT GmbH Novalisstrasse 10 10115 Berlin Germany<br />
<br />
==Schedule==<br />
<br />
time: Oct 6th - Oct 10th<br />
* arrivals / coding sprint: Oct 6th - Oct 7th<br />
* technical discussions / presentations: Oct 8th - Oct 9th<br />
* departures / coding sprint: Oct 10th <br />
<br />
==List of people==<br />
<br />
* Holger 'zecke' Freyther<br />
* Rolf 'Laibsch' Leggewie<br />
* Richard Purdie [Oct 7 - Oct 10] - Honigmond RH - Flight arrives 19:30<br />
* PHilipp Zabel * Rodrigo Vivi [Oct 5 - Oct 10] - Honigmond RH - Flight arrives 12:45<br />
* Gerwin van der Kruis * Michael 'Mickey' Lauer [Oct 8 - Oct 10]<br />
* Marcin 'hrw' Juszkiewicz - [Oct 6 - Oct 10] - Casa Holger - Bus arrives ~12 at Alexanderplatz - I will go to the office directly.<br />
* Stelios S. Koroneos [Oct 7 - Oct 10] - Flight arrives 10:10<br />
* Koen Kooi - [Oct 5 - Oct 10] - Casa Holger - Train arrives 13:18<br />
* Henning Heinold (woglinde) <br />
* Florian Boor [Oct 7 - Oct 10] - Flight arrives 21:10<br />
* Graeme (XorA) Gregory [Oct 5 - Oct 11]- Honigmond RH - Flight Arrives 12:45 - Flight Leaves 13:30<br />
* Daniel Willmann (alphaone)<br />
* Philip Balister (Crofton) [Oct 5 - Oct 10] - Hotel * Gästehaus Berlin Mitte * - Flight arrives 10 AM<br />
* Jonas Hurrelmann (jott) * Uli Luckas [Oct 9]<br />
* Jan Lübbe (shoragan)<br />
* Henryk Plötz<br />
* please drop zecke an email if you plan to come<br />
<br />
==Quartiers== <br />
<br />
inks for rooms in walking distance (same street as the office)<br />
* zecke's flat. I think I can host four of you (5-10 minutes walk to the office)<br />
* [http://www.honigmond-berlin.de]<br />
* [http://www.eastener-hostel.de] further away (a longer walk)<br />
* [http://www.gaestehaus-berlin-mitte.de/]<br />
<br />
== Agenda == <br />
<br />
=== Top Level Items ===<br />
<br />
* Creating a Foundation. Who is goint to prepare the paper work? zecke and florian could do that<br />
* Should we hold a sprint? Should we do user presentations?<br />
* Reconsider changing SCM<br />
<br />
=== 2007.10.08 === <br />
====[09:55] Assign note taker to collect and publish minutes====<br />
====[10:00] Welcome Branch ==== <br />
====[11:00] Review of last years work ==== <br />
====[11:30] Discuss and adjust agenda ==== <br />
====[12:00] OE Foundation, what was done, what is needed, how to proceed and where to create it====<br />
====[13:30] Lunch ====<br />
====[15:30] OpenEmbedded User Presentations====<br />
=====OpenMoko=====<br />
=====Indt/Mamona=====<br />
=====Tarent=====<br />
=====DigitalOpsis=====<br />
====[17:30] Solutions for vendor discussion====<br />
=====Stable release=====<br />
=====SDK=====<br />
=====Distro's=====<br />
=====Target Hardware issues=====<br />
=== 2007.10.09 ===<br />
====[10:00] Technology====<br />
=====update-alternatives of ipkg=====<br />
=====distro generic=====<br />
=====clean staging(?)=====<br />
=====getting image in-between task-base and task-boot?=====<br />
=====General strategy how to get things smaller=====<br />
=====Features tied to boards on e.g. gumstix=====<br />
=====Quality Issues=====<br />
====[13:30] Lunch ====<br />
====Infrastructure====<br />
=====Autobuilder=====<br />
=====Maintainers=====<br />
=====How to deal with the wiki=====<br />
== To Be Done ==<br />
* Prepare paper-work for an e.V. <br />
* Plan one day for the general assembly of the e.V. <br />
* Decide on the Agenda. <br />
* Should we hold a sprint? What would be the topic? QA, Angstrom polishing, doing our first stable release, creating a GUI for BitBake/OE? <br />
* Sprint: merge .dreambox, get llvm to build, get llvm-cross working, pycurses angstrom setup gui<br />
<br />
[[Category:OEDEM]]</div>Laibschhttps://www.openembedded.org/index.php?title=Oedem2007&diff=2111Oedem20072010-01-10T16:48:55Z<p>Laibsch: Reverted edits by Glenn (Talk); changed back to last version by Mickey</p>
<hr />
<div>==Venue==<br />
<br />
GMIT GmbH Novalisstrasse 10 10115 Berlin Germany<br />
<br />
==Schedule==<br />
<br />
time: Oct 6th - Oct 10th<br />
* arrivals / coding sprint: Oct 6th - Oct 7th<br />
* technical discussions / presentations: Oct 8th - Oct 9th<br />
* departures / coding sprint: Oct 10th <br />
<br />
==List of people==<br />
<br />
* Holger 'zecke' Freyther<br />
* Rolf 'Laibsch' Leggewie<br />
* Richard Purdie [Oct 7 - Oct 10] - Honigmond RH - Flight arrives 19:30<br />
* PHilipp Zabel * Rodrigo Vivi [Oct 5 - Oct 10] - Honigmond RH - Flight arrives 12:45<br />
* Gerwin van der Kruis * Michael 'Mickey' Lauer [Oct 8 - Oct 10]<br />
* Marcin 'hrw' Juszkiewicz - [Oct 6 - Oct 10] - Casa Holger - Bus arrives ~12 at Alexanderplatz - I will go to the office directly.<br />
* Stelios S. Koroneos [Oct 7 - Oct 10] - Flight arrives 10:10<br />
* Koen Kooi - [Oct 5 - Oct 10] - Casa Holger - Train arrives 13:18<br />
* Henning Heinold (woglinde) <br />
* Florian Boor [Oct 7 - Oct 10] - Flight arrives 21:10<br />
* Graeme (XorA) Gregory [Oct 5 - Oct 11]- Honigmond RH - Flight Arrives 12:45 - Flight Leaves 13:30<br />
* Daniel Willmann (alphaone)<br />
* Philip Balister (Crofton) [Oct 5 - Oct 10] - Hotel * Gästehaus Berlin Mitte * - Flight arrives 10 AM<br />
* Jonas Hurrelmann (jott) * Uli Luckas [Oct 9]<br />
* Jan Lübbe (shoragan)<br />
* Henryk Plötz<br />
* please drop zecke an email if you plan to come<br />
<br />
==Quartiers== <br />
<br />
inks for rooms in walking distance (same street as the office)<br />
* zecke's flat. I think I can host four of you (5-10 minutes walk to the office)<br />
* [http://www.honigmond-berlin.de]<br />
* [http://www.eastener-hostel.de] further away (a longer walk)<br />
* [http://www.gaestehaus-berlin-mitte.de/]<br />
<br />
== Agenda == <br />
<br />
=== Top Level Items ===<br />
<br />
* Creating a Foundation. Who is goint to prepare the paper work? zecke and florian could do that<br />
* Should we hold a sprint? Should we do user presentations?<br />
* Reconsider changing SCM<br />
<br />
=== 2007.10.08 === <br />
====[09:55] Assign note taker to collect and publish minutes====<br />
====[10:00] Welcome Branch ==== <br />
====[11:00] Review of last years work ==== <br />
====[11:30] Discuss and adjust agenda ==== <br />
====[12:00] OE Foundation, what was done, what is needed, how to proceed and where to create it====<br />
====[13:30] Lunch ====<br />
====[15:30] OpenEmbedded User Presentations====<br />
=====OpenMoko=====<br />
=====Indt/Mamona=====<br />
=====Tarent=====<br />
=====DigitalOpsis=====<br />
====[17:30] Solutions for vendor discussion====<br />
=====Stable release=====<br />
=====SDK=====<br />
=====Distro's=====<br />
=====Target Hardware issues=====<br />
=== 2007.10.09 ===<br />
====[10:00] Technology====<br />
=====update-alternatives of ipkg=====<br />
=====distro generic=====<br />
=====clean staging(?)=====<br />
=====getting image in-between task-base and task-boot?=====<br />
=====General strategy how to get things smaller=====<br />
=====Features tied to boards on e.g. gumstix=====<br />
=====Quality Issues=====<br />
====[13:30] Lunch ====<br />
====Infrastructure====<br />
=====Autobuilder=====<br />
=====Maintainers=====<br />
=====How to deal with the wiki=====<br />
== To Be Done ==<br />
* Prepare paper-work for an e.V. <br />
* Plan one day for the general assembly of the e.V. <br />
* Decide on the Agenda. <br />
* Should we hold a sprint? What would be the topic? QA, Angstrom polishing, doing our first stable release, creating a GUI for BitBake/OE? <br />
* Sprint: merge .dreambox, get llvm to build, get llvm-cross working, pycurses angstrom setup gui</div>Laibschhttps://www.openembedded.org/index.php?title=Become_Sponsor&diff=2110Become Sponsor2010-01-10T16:46:39Z<p>Laibsch: </p>
<hr />
<div>= Overview =<br />
<br />
This page describes how an organization can help OpenEmbedded.<br />
<br />
= Sponsorship =<br />
<br />
The OpenEmbedded project encourages organizations that benefit and use OE to become a sponsor. There are three levels of sponsorship, Gold, Silver, and Bronze.<br />
<br />
== Gold Sponsorship ==<br />
<br />
Annual Cost: EUR 25000<br />
<br />
== Silver Sponsorship ==<br />
<br />
Annual Cost: EUR 5000<br />
<br />
== Bronze Sponsorship ==<br />
Annual Cost: EUR 500<br />
<br />
= Project Contribution =<br />
<br />
OE is always interested in getting help to improve the project and software. Anyone that has identified problems is encouraged to pitch in and help out. Additionally, help with specifics such as technical writing, design, testing, and other specialized skills would be valued.<br />
<br />
[[Category:Verein]]</div>Laibschhttps://www.openembedded.org/index.php?title=OpenEmbedded_eV_Statutes&diff=2109OpenEmbedded eV Statutes2010-01-10T16:46:16Z<p>Laibsch: </p>
<hr />
<div>The following is a Babelfish translation of http://docs.openembedded.org/organization/2008-11-22_statutes-de.pdf<br />
<br />
Please clean this up if you speak German.<br />
<br />
== Statute of the OpenEmbedded registered association ==<br />
(conditions 22.11.2008)<br />
<br />
=== explanation by terms ===<br />
# free software, also “open SOURCE software” mentioned, in the sense of this statute are computer programmes, which are made available free of charge by the author in not backgetable way of the public. The author grants third the freedom to be allowed to use the program for each purpose; examine to be allowed, how the program functions and it to the own needs to adapt; To be allowed to make copies for others; to be allowed to improve and the program and make accessible these improvements general well-being.<br />
# Development of free software in the sense of this statute covers the research and elaboration of the theoretical bases and concepts as well as their testing by programming and test of free software, which realizes these concepts and bases.<br />
# “OpenEmbedded (OE)” is a computer-assisted tool, which contains both infrastructure for programs and user programs of inclusive tones, pictures, documents and translations. As free software is developed and put to the public free of charge at the disposal.<br />
<br />
=== 1. Name, seat and financial year ===<br />
# the name of the association OpenEmbedded registered association reads, shortened OE registered association<br />
# the association has its seat in Berlin, Federal Republic of Germany. If no firm office is furnished, the administration follows the residence of the respective member of the board, who notices the management.<br />
# An entry is aimed at into the register of associations of the district court Berlin Charlottenburg.<br />
# Financial year is the calendar year.<br />
<br />
=== 2. Association purpose ===<br />
# the purpose of the association is the promotion and spreading of free software in the sense suitor software with special consideration of the program complex “OpenEmbedded”, in order to support the free knowledge exchange and the equal chances with the entrance to software as well as national education, science and research.<br />
# The association purpose in particular realised by<br />
#* a.die promotion of the education, the exchange of views and the co-operation of users, developers and researchers<br />
#* b.Forschung and discussion over the effects of free software and the thought suitor software on society and science<br />
#* c.die advancement and research at free software, as well as their their integration within the home range<br />
#* d.die supply of free software, supporting pictures, tones, to make for data and documentation as well as promotion their availability and the production and spreading of documentation accessible over it<br />
#* e.Beiträge the adept information of the public in the field of activity of the association and participation at fairs and congresses around the information a broader spectrum of users f.Organisation from congresses and generally accessible lectures to the further training of the project participants and User g.das retaining the free rights of the project participants to the protection from commercial interests third<br />
# a change of the association purpose may only in the framework in § 3 (1) of given framework to take place.<br />
<br />
=== 3. Non-profit character ===<br />
# the association pursues directly non-profit purposes in the sense of the section tax-privileged purposes of the tax code in the context of its activity in accordance with § 2 of the statute exclusively and (§§ 51ff. AO). It is selbstlos active and pursued not primarily self-economical purposes<br />
# the means of the association is excluding for statutory purposes to be used. The members receive excluding reimbursements of developed costs, but no direct allowances from means association.<br />
# Nobody may by expenditures for association, which are strange to the association purpose or are favoured by disproportionately high remuneration. For the replacement of expenditures, as far as different legal regulations are not to be used, the federal travel expenses law is determining.<br />
<br />
=== 4. Kinds of the membership and members of the association ===<br />
# members of the association can become natural and legal entities, who want to carry and support the goals of the association. In order to become fair the international character of the association, in addition, over members the possibility to give of withdrawing itself from the active support of the advancement from OpenEmbedded without giving the membership up, thereby the following kinds are intended by memberships:<br />
#* A) Active members are natural persons, who support the association purpose and the implementation of the association goals by cooperation and the full obligations of a club member take over. In particular cooperation from them, which and the practice of the right to vote expects, becomes participation in the meetings of the members.<br />
#* b) Extraordinary members are natural and legal entities, who explain the support of the association purpose and the association goals by their membership in the association, but do without the practice of the rights of the active members, here the practice of the right to vote. Legal entities designate a natural person as representatives for practice remaining rights and obligations.<br />
#* C) Promoting members are extraordinary members, that promote the association purpose and the association goals in particular by a financial or a special contribution. They are published on own desire on the web page of the association and to have the right to the participation in the meeting of the members, without acquiring thereby a right to vote.<br />
# The active membership is acquired on proposal of an active member with agreement of two of other active members by resolution of the meeting of the members or the active members by Internet choice with simple majority. Main decision criterion for the admission should be the commitment shown by the photograph candidates during a longer period and the contribution made thereby in the sense of the association goals. An active member can change on own request at the executive committee into the extraordinary membership. During default of the obligations of an active member over two following each other tidy meetings of the members, indicated above, the membership changes automatically into an extraordinary. An extraordinary however not promoting member can request the active membership at the executive committee. On the admission of promoting members the executive committee decides.<br />
# The membership ends by withdrawal, exclusion or death, with legal entities also by loss of the juridical personality. The withdrawal of a member is possible only to 31 December of each yearly. It takes place via written explanation opposite the executive committee under adherence to one period from 4 weeks.<br />
# The instrument of the association exclusion is critical situations reserved, whereby in principle to the quality the priority is to be granted clarifying. The exclusion takes place on resolution of the executive committee with immediate effect. Reasons for an exclusion can be<br />
#* a) a heavy offence of a member against the regulations as well as goals and purposes of the association specified in this statute after a unsuccessful attempt of clarifying, as well as<br />
#* b) despite repeated reminder existing arrears at payments of dues during one period of 12 months. Opportunity must be given to the member to the justification and/or statement before the adoption of resolutions. Against the exclusion contradiction can be inserted within four weeks at the executive committee, on which the next meeting of the members decides. Up to the decision of the meeting of the members the rights and obligations of the member rest.<br />
# With separating a member from the association or during dissolution of association no requirement on Rückerstattung of brought in net assets exists.<br />
<br />
=== 5. Organs of the association ===<br />
of organs of the association are:<br />
* the meeting of the members as well as<br />
* the executive committee.<br />
<br />
=== 6. Meeting of the members ===<br />
# All club members can attend meeting of the members. Only active members receive one voice each.<br />
# The meeting of the members takes place at least once a year. It will call up in writing from the executive committee by post office or email under indication of the provisional agenda. The invitation period amounts to six weeks. The period begins with the day following on the sending off of the invitation letter. It is valid the date of the postmark or the sending off of the email. The invitation letter is considered as happened, if it is addressed to the last address announced by the member of the association in writing. The members can in writing or electronically address further requests for items on the agenda until 2 weeks before the meeting to the executive committee. It is valid the date of the post office and/or email entrance. The executive committee publishes the final agenda in the Internet, the address is in the written invitation to be communicated.<br />
# An extraordinary meeting of the members is to be called up, if it requires the interest of association. On written demand of at least 20% of all club members the executive committee has to call up an extraordinary meeting of the members within six weeks. The desired item on the agenda must have to be inferred from the request of the members.<br />
# The meeting of the members is resolutionable during normal invitation without consideration for the number of appearances. She selects from her center a Versammlungsleiter. Resolutions are met, if the meeting does not determine something else, openly by show of hands with a simple majority of votes. With equality of votes a request is valid as rejected.<br />
# To amendments of the by-laws and to resolutions over the dissolution of the association are deviating from (4) 3/4 of the voices delivered in the meeting of the members, at least however half of the voices of all active club members necessarily.<br />
# An active member, that appears not personal for meeting of the members, can leave itself represented by another member personally present during the meeting of the members. The representative notices the right to vote of the represented member beside his own. The representative legitimizes itself at the beginning of the meeting of the members by presenting a written authority in the original opposite the executive committee. A representative can represent maximally two members.<br />
<br />
=== 7. Tasks of the meeting of the members ===<br />
# the meeting of the members as the highest resolution-seizing representative body of the association is in principle responsible for all tasks, if certain tasks did not become to transfer another representative body of the association in accordance with this statute. The meeting of the members selects from the number of the active members the executive committee. The persons, who unite most voices on itself, are selected. The choice secretly takes place with voting cards.<br />
# The meeting of the members can vote members out of the executive committee. For this it needs in deviation from (1) the majority of the voices of all active club members.<br />
# The meeting of the members decides on contradictions of members, whom the executive committee intends to exclude.<br />
# The meeting of the members receives the business report of the executive committee which can be submitted annually and the examination report of the invoice controller and gives the executive committee discharge.<br />
# It is reserved the meeting of the members to decide on amendments of the by-laws and dissolutions of association.<br />
# You are to be submitted in particular the annual account and the annual report for adoption of resolutions over permission and the discharge of the executive committee in writing. She orders two invoice controllers, that belong neither to the executive committee still another committee appointed by the executive committee and are not also employees of the association, in order to examine and report on the result before the meeting of the members record keeping including end-of-year procedure. The invoice controllers have entrance to all reservation and calculation documents of the association.<br />
# the right of representation of the executive committee it is opposite the way limited third that for the following legal transactions the agreement of the meeting of the members is necessary: more<br />
#* a.über on and sale as well as the load of landed property,<br />
#* b.die financial participation in societies as well as<br />
#* c.die admission of loans starting from EURO 10,000, -, to decide.<br />
# She can decide over further affairs, which by the executive committee or from the member shank is submitted to it.<br />
<br />
=== 8. Executive committee ===<br />
# the executive committee consists only natural persons of 4 persons, it can belong. The term of office amounts to 3 years. Re-election is permissible. The members of the board officiating in each case remain at expiration of the term of office in the office, until successors are selected<br />
# the executive committee select from his center one chairman and two deputies. One the deputy is a treasurer. Re-election is permissible.<br />
# The executive committee work, in particular regulations for the summoning of board meetings, whose expiration and the execution of votes, regulated by an agenda of the executive committee, which decides the executive committee unanimously.<br />
# The executive committee decides over all association affairs, as far as they do not require a resolution of the meeting of the members. It implements the resolutions of the meeting of the members.<br />
# The members of the executive committee are everyone for itself alone in the name of the association outward entitled to act as substitute.<br />
# In case of separating a member of the board during the term of office the executive committee determines a kommissarisches member of the board according to Internet choice of the active members. The kommissarische member of the board remains up to the next meeting of the members in the office. On a final follow-up in the executive committee the meeting of the members decides.<br />
# The executive committee can order a full-time managing director, who leads the current business of the administration of the association by resolution as special representatives in accordance with §30 BGB and superior of the full-time association coworkers is. Decisions over work contracts, notices as well as admissions of members and member exclusions remain reserving the executive committee.<br />
# The managing director has to participate the obligation to the participation in the meetings of the members and the right as well as on demands of the executive committee the obligation in the board meetings. It has speech right on all meetings and is the representative bodies of the association opposite accountable.<br />
# The executive committee on its part can make amendments of the by-laws, which are required by supervision, court or fiscal authorities for formal reasons. The amendments of the by-laws must be communicated to the next meeting of the members.<br />
<br />
=== 9. Agenda ===<br />
the agenda regulates going out details of the association work over the frameworks of the statute. The executive committee puts the agenda into force after the agreement by the members. The agreement of the members takes place via Internet choice with simple majority of the active members.<br />
<br />
=== 10. Minutes ===<br />
the resolutions of the executive committee and the meetings of the members are laid down in writing and stand for the members to the insight for order.<br />
<br />
=== 11. Collective agreements ===<br />
before the employment full-time persons employed regulates the executive committee their payment in the agenda.<br />
<br />
=== 13. Association financing ===<br />
# the necessary financial means of the association constituted by<br />
#* A) of membership dues,<br />
#* b) of subsidies of the country, the municipalities and other public places,<br />
#* C) donations,<br />
#* D) other allowances third,<br />
#* e) repay for activities of the association in the context of the non-profit character, among other things for lectures.<br />
# The members pay contributions in accordance with condition of a resolution of the meeting of the members or the active members by Internet choice with simple majority. The regulation for the height of membership dues becomes a component of the agenda.<br />
# In the case of dissolution of the association or with omission of tax-privileged purposes the fortune of the association falls at the German Unesco Kommision registered association, Colmantstraße 15, 53115 Bonn, which has to use it directly excluding and for non-profit purposes. Resolutions over the future use of the property of the association may be implemented in this case only after consent of the tax office.<br />
<br />
=== 14. The entry into force ===<br />
managing statute contents was decided by the founders' meeting to ............. in Brussels, Belgium.<br />
<br />
The initial members of the association draw as follows:<br />
<br />
[[Category:Verein]]</div>Laibschhttps://www.openembedded.org/index.php?title=Become_Sponsor&diff=2108Become Sponsor2010-01-10T16:45:59Z<p>Laibsch: </p>
<hr />
<div>= Overview =<br />
<br />
This page describes how an organization can help OpenEmbedded.<br />
<br />
= Sponsorship =<br />
<br />
The OpenEmbedded project encourages organizations that benefit and use OE to become a sponsor. There are three levels of sponsorship, Gold, Silver, and Bronze.<br />
<br />
== Gold Sponsorship ==<br />
<br />
Annual Cost: EUR 25000<br />
<br />
== Silver Sponsorship ==<br />
<br />
Annual Cost: EUR 5000<br />
<br />
== Bronze Sponsorship ==<br />
Annual Cost: EUR 500<br />
<br />
= Project Contribution =<br />
<br />
OE is always interested in getting help to improve the project and software. Anyone that has identified problems is encouraged to pitch in and help out. Additionally, help with specifics such as technical writing, design, testing, and other specialized skills would be valued.<br />
<br />
[[Catgegory:Verein]]</div>Laibschhttps://www.openembedded.org/index.php?title=Category:Verein&diff=2106Category:Verein2010-01-10T16:43:54Z<p>Laibsch: </p>
<hr />
<div>information about the eV or "eingetragener Verein"<br />
<br />
[[Category:Governance]]</div>Laibschhttps://www.openembedded.org/index.php?title=Checklist_for_the_General_Assembly&diff=2105Checklist for the General Assembly2010-01-10T16:43:33Z<p>Laibsch: </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 />
# Change the proxy form to refer to the correct assembly. You will find the ODT in the [http://websvn.kde.org/trunk/www/sites/kde-ev/resources/proxy_instructions.odt?view=log KDE SVN]<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]]</div>Laibschhttps://www.openembedded.org/index.php?title=Category:OEDEM&diff=2104Category:OEDEM2010-01-10T16:43:02Z<p>Laibsch: New page: OE Developper meetings - see you in the real world planning and documentation</p>
<hr />
<div>OE Developper meetings - see you in the real world<br />
<br />
planning and documentation</div>Laibschhttps://www.openembedded.org/index.php?title=Oedem/2009&diff=2103Oedem/20092010-01-10T16:42:18Z<p>Laibsch: </p>
<hr />
<div>OpenEmbedded developers' meeting 2009 will be in Cambridge, UK on the weekend of November 7/8.<br />
<br />
All developers and other interested parties are welcome.<br />
<br />
==Location==<br />
<br />
Reciva Ltd have generously offered to host the meeting at their offices: 509 Coldhams Lane, Cambridge, CB1 3JS.<br />
<br />
The Reciva offices are on the east side of the city, about 2km from the centre of town. See below for detailed travel information.<br />
<br />
Call Phil on +44 7973 869202 if you get hopelessly lost and cannot find the venue.<br />
<br />
==Registration==<br />
<br />
Due to restricted space at the venue, the number of attendees is strictly limited.<br />
<br />
Pre-registration is now closed, although it is possible that more spaces may become available if previously-registered attendees drop out. Send mail to Phil if you wish to attend but missed the deadline for initial registration.<br />
<br />
==Agenda==<br />
<br />
===Friday 2009-11-06===<br />
<br />
20:00 (approx) Pre-meeting beer session at the Red Lion, Histon, CB24 9BD<br />
<br />
http://maps.google.co.uk/maps?f=q&source=s_q&hl=en&geocode=&q=cb24+9jd&sll=53.800651,-4.064941&sspn=11.25,27.905273&ie=UTF8&ll=52.253684,0.105486&spn=0.011375,0.027251&t=h&z=15&iwloc=A<br />
<br />
From the city centre, ride the [http://www.stagecoachbus.com/timetables/Citi7Jan09%5B3%5D.pdf Citi 7] bus towards Cottenham. Pass Histon village green (pond with ducks) on your right, the Boot and Barley Mow pubs on your left, then alight at the next stop and you will be almost directly outside the Red Lion. Travel time from the city is approximately 25 minutes and a return ticket costs about £3. Other travel options include taxi (10-15 minutes, about £10 each way) or walking (50-60 minutes, no charge). <br />
<br />
===Saturday 2009-11-07===<br />
<br />
10:00-10:15 Welcome + Agenda<br />
<br />
: Introductions and discussion/confirmation of agenda<br />
: some entries will need to be moved as few of us will have to leave earlier on Sunday (Henning, Marcin and Marco have train at 17:10)<br />
<br />
10:15-12:00 OE e.V. meeting (Mickey Lauer / e.V. board)<br />
<br />
: '''e.V. Membership Fees'''<br />
<br />
: As per our statutes, members can chose their membership fees. We should create recommendations for corporate entities (also indicate what they would gain by that).<br />
: '''Travel reimbursement policy'''<br />
: '''Financial status'''<br />
: '''Sponsors: announcement, website and memberships'''<br />
: '''Public relations committee'''<br />
<br />
12:00-13:00 Establishment of technical steering committee (Phil Blundell)<br />
<br />
13:00-14:00 Break for lunch / hacking session<br />
<br />
14:00-15:00 OE and Poky (Mickey Lauer)<br />
<br />
15:00-16:00 Software development for OE derived distributions<br />
<br />
* Quick presentation of KOBE (Eclipse plugin by KOAN for recipe creation and more)<br />
<br />
People always want to develop software for the target hardware, what can we do to make developers lives easier? The answer is not always use bitbake. How do we supply toolchains, libraries etc? How are people solving this today?<br />
<br />
16:00-16:30 Learning to love USE flags, or, What's a distro for? (Phil Blundell)<br />
<br />
16:30-17:00 State of the art in package management (Phil Blundell)<br />
<br />
* Why is opkg so bad?<br />
* What alternatives are there?<br />
* What can we do to improve the situation?<br />
<br />
17:00-18:00 Hacking session<br />
<br />
18:00 Venue closes<br />
<br />
===Sunday 2009-11-08===<br />
<br />
10:00-11:00 Splitting the recipes tree (Mickey Lauer)<br />
<br />
: Many of us feel we should split the recipes up into a couple of smaller categories to be able to handle them in a more efficient way (parsing, switching on/off, etc.), but also to indicate which packages are critical / very well maintained / not maintained at all / ...<br />
<br />
11:00-12:00 Future plans for stable branch(es)<br />
<br />
* Why stable branch is actually not so stable?<br />
* Creation of long term support branch?<br />
<br />
12:00-13:00 Bugtracker Discussion, what to do with the current bugzilla, replace/enhance/abandon. (Graeme 'XorA' Gregory)<br />
<br />
13:00-14:00 Break for lunch/hacking<br />
<br />
14:00-15:00 Hosting arrangements (Mickey Lauer) (see [[Infrastructure]])<br />
<br />
: There are still services on amethyst, although former-admin Mickey has requested them to be moved. Obviously some one needs to take the wheel here.<br />
<br />
: Services on Amethyst:<br />
<br />
* patchwork.openembedded.org<br />
* wiki.openembedded.org<br />
* www.openembedded.org<br />
<br />
: Git repository management issues:<br />
<br />
* Clearly identify user branches with a namespace?<br />
* Rename org.openembedded.dev to master?<br />
* CIA commit hook should only report dev branch changes?<br />
<br />
15:00-16:00 Death to checksums.ini? (Phil Blundell)<br />
<br />
: The current method of tracking and verifying checksums on source tarballs has various drawbacks and, due to a combination of technical and social issues, seems to bring few benefits. Can we do any better?<br />
<br />
16:00-17:00 BitBake Future Roadmap (Richard Purdie)<br />
<br />
17:00-18:00 OE Core Changes (Richard Purdie)<br />
<br />
: Discuss various possible core changes to OE such as those to the do_stage process, layout variable changes, Candian SDK Generation. Any others planned?<br />
<br />
18:00 Go home<br />
<br />
==Travel==<br />
<br />
London Stansted airport is the nearest to Cambridge with regular service. <br />
(There is a small airport in Cambridge itself but I don't think any scheduled<br />
airlines operate from there anymore.)<br />
<br />
For those travelling from Europe, Stansted is about a 30-minute train ride from Cambridge city centre and is served by Air Berlin, Ryanair and Germanwings among others. Luton airport is about 1 hour away by bus and is served by Easyjet.<br />
<br />
For those travelling from further away, most long-haul flights arrive at Heathrow or Gatwick airports (although there is some transatlantic service into Stansted). Both Heathrow and Gatwick are about 2 hours from Cambridge by train or bus: the train is quicker but involves several changes in London, whereas the bus is slow but cheaper and less complicated.<br />
<br />
If arriving at LHR airport, take the [http://thetube.com Piccadilly line] from the Underground station and ride it all the way to Kings Cross St Pancras. Ascend to street level, follow signs to Kings Cross mainline station (not St Pancras: the two stations are different although they share a subway stop) and then look for trains to Cambridge or Kings Lynn on the departure board. There are usually two fast services and two slow services to Cambridge per hour: the slow trains are often overtaken by the fast ones en route so it may be best to wait for a fast service even if this is not the next to depart.<br />
<br />
If arriving at LCY, take the [http://www.tfl.gov.uk/gettingaround/2558.aspx#London_City_Airport DLR] to Bank, then change to the Northern Line northbound. From Kings Cross St Pancras, proceed as for LHR, above.<br />
<br />
http://nationalrail.co.uk<br />
<br />
http://nationalexpress.co.uk/<br />
<br />
Alternatively you can take the Eurostar to London St Pancras, which is 50 minutes from Cambridge by train.<br />
<br />
=== Directions from Cambridge rail station to Reciva HQ ===<br />
<br />
'''By bus''' (approximate travel time 30 minutes)<br />
<br />
- take Citi 1 bus towards Fulbourn, alight at St Andrews church in Cherry Hinton, then walk down Coldhams Lane for about 500 metres. Our building will be on your right and has a large sign on the front reading "Semitool". The Citi 1 route runs 7 days a week, about every ten minutes during the daytime, less often (but still fairly frequent) in the evenings.<br />
<br />
- alternatively, take any bus to the city centre and then catch service 16 going out of town (the city centre is a terminus on this route). Alight at the first stop after the Rosemary Branch pub on Coldhams Lane and you will be directly outside the office. Note that bus #16 only runs once per hour so check departure times before choosing this route.<br />
<br />
http://www.cambridgeshire.gov.uk/transport<br />
<br />
http://www.stagecoachbus.com/cambridge<br />
<br />
'''On foot''' (approximate travel time 45 minutes) or bike (approx 15 minutes)<br />
<br />
- Turn right immediately in front of the station and cross the car park, passing the hotel and cycle shop on your left.<br />
<br />
- Upon exiting the car park, go up the steps to the cycle/footbridge and cross to the other side of the railway line.<br />
<br />
- Exit the bridge and turn left, then immediately right into Greville Road.<br />
<br />
- At the end of Greville Road, go left on Coleridge Road. Cross at the pedestrian crossing and go through the chicane onto the footpath opposite.<br />
<br />
- Proceed down Marmora Road. Cross Hobart Road and proceed down the footpath.<br />
<br />
- Go left into Montreal Road, then right into Natal Road.<br />
<br />
- Go left on Perne Road. At the lights, cross to the other side and go down Brookside.<br />
<br />
- When the road bends to the right, do not follow the curve but instead take the footpath directly ahead (across a small bridge). Follow the path until you arrive at the Holiday Inn Express.<br />
<br />
- Bear left onto Norman Way. Ascend out of the pit to the traffic lights next to the car dealership.<br />
<br />
- Turn right onto Coldhams Lane, then cross to the other side of the street. Pass the yellow self-storage depot, then Reciva HQ is the next building on your left.<br />
<br />
See [http://walkit.com walkit.com] for other route suggestions. The train station is at postcode CB1 2JB. The meeting venue is at CB1 3JS, although walkit (and most map sites, including google) place this about 500 metres too far southeast.<br />
<br />
===Directions to venue by car===<br />
<br />
'''From all points north and west'''<br />
<br />
From the A1 or A10, take the A14 eastbound. Proceed along the Cambridge northern bypass. Leave at junction 35 (for Quy, Newmarket) and take the A1303 towards Cambridge, following signs towards the airport. Turn left at the next roundabout (by the corner of the airport) towards Cherry Hinton. At the next roundabout, go straight ahead into the traffic calmed area. Cross one mini-roundabout, then two in quick succession, then turn right at the traffic lights. Look for a building on your right labelled "SEMITOOL"; this is the meeting venue. If you reach the Rosemary Branch pub and Toyota dealership, you have gone too far.<br />
<br />
==Accommodation==<br />
<br />
The nearest full-service hotel is Holiday Inn Express, http://www.expresscambridge.co.uk/<br />
<br />
Cheapest accomodation is probably the YHA hostel, http://www.yha.org.uk/find-accommodation/east-of-england/hostels/Cambridge/index.aspx<br />
<br />
There are various bed-and-breakfast establishments nearby, prices start at approx £35/night<br />
<br />
Some other hotels in Cambridge: <br />
<br />
http://www.crowneplaza.co.uk/ <br />
<br />
http://www.devere.co.uk/our-locations/university-arms <br />
<br />
http://www.hilton.co.uk/cambridgegardenhouse<br />
<br />
http://www.arundelhousehotels.co.uk/<br />
<br />
==Food and drink==<br />
<br />
There are no catering facilities on site at the meeting venue. Coffee, tea and water are provided, but bringing your own snack/lunch is recommended. There are shops within about 15 minutes' walk where provisions can be purchased.<br />
<br />
==Attending for sure==<br />
<br />
* Philip Balister<br />
* Michael Lauer<br />
* Marco Cavallini<br />
* Richard Purdie<br />
* Marcin Juszkiewicz<br />
* Henning Heinold<br />
* Robert Schuster<br />
* Florian Boor<br />
* Denys Dmytriyenko<br />
* Ken Gilmer<br />
* Esben Haabendal<br />
* Jonathan Cameron<br />
<br />
[[Category:OEDEM]]</div>Laibschhttps://www.openembedded.org/index.php?title=Category:Governance&diff=2102Category:Governance2010-01-10T16:40:46Z<p>Laibsch: New page: roles and decision making</p>
<hr />
<div>roles and decision making</div>Laibschhttps://www.openembedded.org/index.php?title=Category:Verein&diff=2101Category:Verein2010-01-10T16:39:39Z<p>Laibsch: New page: information about the eV or "eingetragener Verein"</p>
<hr />
<div>information about the eV or "eingetragener Verein"</div>Laibschhttps://www.openembedded.org/index.php?title=OpenEmbedded_eV_Statutes&diff=2100OpenEmbedded eV Statutes2010-01-10T16:37:46Z<p>Laibsch: Reverted edits by Glenn (Talk); changed back to last version by PH5</p>
<hr />
<div>The following is a Babelfish translation of http://docs.openembedded.org/organization/2008-11-22_statutes-de.pdf<br />
<br />
Please clean this up if you speak German.<br />
<br />
== Statute of the OpenEmbedded registered association ==<br />
(conditions 22.11.2008)<br />
<br />
=== explanation by terms ===<br />
# free software, also “open SOURCE software” mentioned, in the sense of this statute are computer programmes, which are made available free of charge by the author in not backgetable way of the public. The author grants third the freedom to be allowed to use the program for each purpose; examine to be allowed, how the program functions and it to the own needs to adapt; To be allowed to make copies for others; to be allowed to improve and the program and make accessible these improvements general well-being.<br />
# Development of free software in the sense of this statute covers the research and elaboration of the theoretical bases and concepts as well as their testing by programming and test of free software, which realizes these concepts and bases.<br />
# “OpenEmbedded (OE)” is a computer-assisted tool, which contains both infrastructure for programs and user programs of inclusive tones, pictures, documents and translations. As free software is developed and put to the public free of charge at the disposal.<br />
<br />
=== 1. Name, seat and financial year ===<br />
# the name of the association OpenEmbedded registered association reads, shortened OE registered association<br />
# the association has its seat in Berlin, Federal Republic of Germany. If no firm office is furnished, the administration follows the residence of the respective member of the board, who notices the management.<br />
# An entry is aimed at into the register of associations of the district court Berlin Charlottenburg.<br />
# Financial year is the calendar year.<br />
<br />
=== 2. Association purpose ===<br />
# the purpose of the association is the promotion and spreading of free software in the sense suitor software with special consideration of the program complex “OpenEmbedded”, in order to support the free knowledge exchange and the equal chances with the entrance to software as well as national education, science and research.<br />
# The association purpose in particular realised by<br />
#* a.die promotion of the education, the exchange of views and the co-operation of users, developers and researchers<br />
#* b.Forschung and discussion over the effects of free software and the thought suitor software on society and science<br />
#* c.die advancement and research at free software, as well as their their integration within the home range<br />
#* d.die supply of free software, supporting pictures, tones, to make for data and documentation as well as promotion their availability and the production and spreading of documentation accessible over it<br />
#* e.Beiträge the adept information of the public in the field of activity of the association and participation at fairs and congresses around the information a broader spectrum of users f.Organisation from congresses and generally accessible lectures to the further training of the project participants and User g.das retaining the free rights of the project participants to the protection from commercial interests third<br />
# a change of the association purpose may only in the framework in § 3 (1) of given framework to take place.<br />
<br />
=== 3. Non-profit character ===<br />
# the association pursues directly non-profit purposes in the sense of the section tax-privileged purposes of the tax code in the context of its activity in accordance with § 2 of the statute exclusively and (§§ 51ff. AO). It is selbstlos active and pursued not primarily self-economical purposes<br />
# the means of the association is excluding for statutory purposes to be used. The members receive excluding reimbursements of developed costs, but no direct allowances from means association.<br />
# Nobody may by expenditures for association, which are strange to the association purpose or are favoured by disproportionately high remuneration. For the replacement of expenditures, as far as different legal regulations are not to be used, the federal travel expenses law is determining.<br />
<br />
=== 4. Kinds of the membership and members of the association ===<br />
# members of the association can become natural and legal entities, who want to carry and support the goals of the association. In order to become fair the international character of the association, in addition, over members the possibility to give of withdrawing itself from the active support of the advancement from OpenEmbedded without giving the membership up, thereby the following kinds are intended by memberships:<br />
#* A) Active members are natural persons, who support the association purpose and the implementation of the association goals by cooperation and the full obligations of a club member take over. In particular cooperation from them, which and the practice of the right to vote expects, becomes participation in the meetings of the members.<br />
#* b) Extraordinary members are natural and legal entities, who explain the support of the association purpose and the association goals by their membership in the association, but do without the practice of the rights of the active members, here the practice of the right to vote. Legal entities designate a natural person as representatives for practice remaining rights and obligations.<br />
#* C) Promoting members are extraordinary members, that promote the association purpose and the association goals in particular by a financial or a special contribution. They are published on own desire on the web page of the association and to have the right to the participation in the meeting of the members, without acquiring thereby a right to vote.<br />
# The active membership is acquired on proposal of an active member with agreement of two of other active members by resolution of the meeting of the members or the active members by Internet choice with simple majority. Main decision criterion for the admission should be the commitment shown by the photograph candidates during a longer period and the contribution made thereby in the sense of the association goals. An active member can change on own request at the executive committee into the extraordinary membership. During default of the obligations of an active member over two following each other tidy meetings of the members, indicated above, the membership changes automatically into an extraordinary. An extraordinary however not promoting member can request the active membership at the executive committee. On the admission of promoting members the executive committee decides.<br />
# The membership ends by withdrawal, exclusion or death, with legal entities also by loss of the juridical personality. The withdrawal of a member is possible only to 31 December of each yearly. It takes place via written explanation opposite the executive committee under adherence to one period from 4 weeks.<br />
# The instrument of the association exclusion is critical situations reserved, whereby in principle to the quality the priority is to be granted clarifying. The exclusion takes place on resolution of the executive committee with immediate effect. Reasons for an exclusion can be<br />
#* a) a heavy offence of a member against the regulations as well as goals and purposes of the association specified in this statute after a unsuccessful attempt of clarifying, as well as<br />
#* b) despite repeated reminder existing arrears at payments of dues during one period of 12 months. Opportunity must be given to the member to the justification and/or statement before the adoption of resolutions. Against the exclusion contradiction can be inserted within four weeks at the executive committee, on which the next meeting of the members decides. Up to the decision of the meeting of the members the rights and obligations of the member rest.<br />
# With separating a member from the association or during dissolution of association no requirement on Rückerstattung of brought in net assets exists.<br />
<br />
=== 5. Organs of the association ===<br />
of organs of the association are:<br />
* the meeting of the members as well as<br />
* the executive committee.<br />
<br />
=== 6. Meeting of the members ===<br />
# All club members can attend meeting of the members. Only active members receive one voice each.<br />
# The meeting of the members takes place at least once a year. It will call up in writing from the executive committee by post office or email under indication of the provisional agenda. The invitation period amounts to six weeks. The period begins with the day following on the sending off of the invitation letter. It is valid the date of the postmark or the sending off of the email. The invitation letter is considered as happened, if it is addressed to the last address announced by the member of the association in writing. The members can in writing or electronically address further requests for items on the agenda until 2 weeks before the meeting to the executive committee. It is valid the date of the post office and/or email entrance. The executive committee publishes the final agenda in the Internet, the address is in the written invitation to be communicated.<br />
# An extraordinary meeting of the members is to be called up, if it requires the interest of association. On written demand of at least 20% of all club members the executive committee has to call up an extraordinary meeting of the members within six weeks. The desired item on the agenda must have to be inferred from the request of the members.<br />
# The meeting of the members is resolutionable during normal invitation without consideration for the number of appearances. She selects from her center a Versammlungsleiter. Resolutions are met, if the meeting does not determine something else, openly by show of hands with a simple majority of votes. With equality of votes a request is valid as rejected.<br />
# To amendments of the by-laws and to resolutions over the dissolution of the association are deviating from (4) 3/4 of the voices delivered in the meeting of the members, at least however half of the voices of all active club members necessarily.<br />
# An active member, that appears not personal for meeting of the members, can leave itself represented by another member personally present during the meeting of the members. The representative notices the right to vote of the represented member beside his own. The representative legitimizes itself at the beginning of the meeting of the members by presenting a written authority in the original opposite the executive committee. A representative can represent maximally two members.<br />
<br />
=== 7. Tasks of the meeting of the members ===<br />
# the meeting of the members as the highest resolution-seizing representative body of the association is in principle responsible for all tasks, if certain tasks did not become to transfer another representative body of the association in accordance with this statute. The meeting of the members selects from the number of the active members the executive committee. The persons, who unite most voices on itself, are selected. The choice secretly takes place with voting cards.<br />
# The meeting of the members can vote members out of the executive committee. For this it needs in deviation from (1) the majority of the voices of all active club members.<br />
# The meeting of the members decides on contradictions of members, whom the executive committee intends to exclude.<br />
# The meeting of the members receives the business report of the executive committee which can be submitted annually and the examination report of the invoice controller and gives the executive committee discharge.<br />
# It is reserved the meeting of the members to decide on amendments of the by-laws and dissolutions of association.<br />
# You are to be submitted in particular the annual account and the annual report for adoption of resolutions over permission and the discharge of the executive committee in writing. She orders two invoice controllers, that belong neither to the executive committee still another committee appointed by the executive committee and are not also employees of the association, in order to examine and report on the result before the meeting of the members record keeping including end-of-year procedure. The invoice controllers have entrance to all reservation and calculation documents of the association.<br />
# the right of representation of the executive committee it is opposite the way limited third that for the following legal transactions the agreement of the meeting of the members is necessary: more<br />
#* a.über on and sale as well as the load of landed property,<br />
#* b.die financial participation in societies as well as<br />
#* c.die admission of loans starting from EURO 10,000, -, to decide.<br />
# She can decide over further affairs, which by the executive committee or from the member shank is submitted to it.<br />
<br />
=== 8. Executive committee ===<br />
# the executive committee consists only natural persons of 4 persons, it can belong. The term of office amounts to 3 years. Re-election is permissible. The members of the board officiating in each case remain at expiration of the term of office in the office, until successors are selected<br />
# the executive committee select from his center one chairman and two deputies. One the deputy is a treasurer. Re-election is permissible.<br />
# The executive committee work, in particular regulations for the summoning of board meetings, whose expiration and the execution of votes, regulated by an agenda of the executive committee, which decides the executive committee unanimously.<br />
# The executive committee decides over all association affairs, as far as they do not require a resolution of the meeting of the members. It implements the resolutions of the meeting of the members.<br />
# The members of the executive committee are everyone for itself alone in the name of the association outward entitled to act as substitute.<br />
# In case of separating a member of the board during the term of office the executive committee determines a kommissarisches member of the board according to Internet choice of the active members. The kommissarische member of the board remains up to the next meeting of the members in the office. On a final follow-up in the executive committee the meeting of the members decides.<br />
# The executive committee can order a full-time managing director, who leads the current business of the administration of the association by resolution as special representatives in accordance with §30 BGB and superior of the full-time association coworkers is. Decisions over work contracts, notices as well as admissions of members and member exclusions remain reserving the executive committee.<br />
# The managing director has to participate the obligation to the participation in the meetings of the members and the right as well as on demands of the executive committee the obligation in the board meetings. It has speech right on all meetings and is the representative bodies of the association opposite accountable.<br />
# The executive committee on its part can make amendments of the by-laws, which are required by supervision, court or fiscal authorities for formal reasons. The amendments of the by-laws must be communicated to the next meeting of the members.<br />
<br />
=== 9. Agenda ===<br />
the agenda regulates going out details of the association work over the frameworks of the statute. The executive committee puts the agenda into force after the agreement by the members. The agreement of the members takes place via Internet choice with simple majority of the active members.<br />
<br />
=== 10. Minutes ===<br />
the resolutions of the executive committee and the meetings of the members are laid down in writing and stand for the members to the insight for order.<br />
<br />
=== 11. Collective agreements ===<br />
before the employment full-time persons employed regulates the executive committee their payment in the agenda.<br />
<br />
=== 13. Association financing ===<br />
# the necessary financial means of the association constituted by<br />
#* A) of membership dues,<br />
#* b) of subsidies of the country, the municipalities and other public places,<br />
#* C) donations,<br />
#* D) other allowances third,<br />
#* e) repay for activities of the association in the context of the non-profit character, among other things for lectures.<br />
# The members pay contributions in accordance with condition of a resolution of the meeting of the members or the active members by Internet choice with simple majority. The regulation for the height of membership dues becomes a component of the agenda.<br />
# In the case of dissolution of the association or with omission of tax-privileged purposes the fortune of the association falls at the German Unesco Kommision registered association, Colmantstraße 15, 53115 Bonn, which has to use it directly excluding and for non-profit purposes. Resolutions over the future use of the property of the association may be implemented in this case only after consent of the tax office.<br />
<br />
=== 14. The entry into force ===<br />
managing statute contents was decided by the founders' meeting to ............. in Brussels, Belgium.<br />
<br />
The initial members of the association draw as follows:</div>Laibschhttps://www.openembedded.org/index.php?title=Using_IceCC&diff=2099Using IceCC2010-01-10T16:37:23Z<p>Laibsch: </p>
<hr />
<div>== IceCC and OE ==<br />
It is possible to compile on a cluster of machines with OE, and quite easily so. This code is still somewhat experimental, but should rapidly stabilize thanks to the work that Ifaistos has put into it recently and previous work from likewise and zecke (I hope I did not forget anyone). You need to take the following steps to prepare for compilation with icecc. How to set up icecc itself is beyond this intro.<br />
<br />
* Put ''INHERIT += "icecc"'' in your local.conf<br />
* copy the customized [http://bugs.openembedded.org/attachment.cgi?id=1032&action=view create-icecc-env.sh] script to /path/to/your/oe/root/tmp/ and make it executable.<br />
* set ''ICECC_ENV_EXEC = /path/to/your/oe/root/tmp/create-icecc-env.sh'' in your local.conf<br />
* set ''ICECC_PATH = /usr/bin/icecc'' in your local.conf (be sure this matches the output of 'which icecc')<br />
<br />
User now can specify if certain packages or packages belonging to class should not use icecc to distribute compile jobs to remote machines, but handled localy, by defining ICECC_USER_CLASS_BL and ICECC_USER_PACKAGE_BL with the appropriate values in local.conf<br />
<br />
<br />
=== ICECC config ===<br />
<br />
<br />
#<br />
# Nice level of running compilers<br />
#<br />
# ICECC_NICE_LEVEL="5"<br />
ICECC_NICE_LEVEL="5"<br />
#<br />
# icecc daemon log file<br />
#<br />
# ICECC_LOG_FILE="/var/log/iceccd.log"<br />
ICECC_LOG_FILE="/var/log/iceccd.log"<br />
#<br />
# Identification for the network the scheduler and daemon run on. <br />
# You can have several distinct icecc networks in the same LAN<br />
# for whatever reason.<br />
#<br />
# ICECC_NETNAME=""<br />
ICECC_NETNAME="oe"<br />
# <br />
# You can overwrite here the number of jobs to run in parallel. Per<br />
# default this depends on the number of (virtual) CPUs installed. <br />
#<br />
# ICECC_MAX_JOBS=""<br />
ICECC_MAX_JOBS="3"<br />
#<br />
# This is the directory where the icecc daemon stores the environments<br />
# it compiles in. In a big network this can grow quite a bit, so use some<br />
# path if your /tmp is small - but the user icecc has to write to it.<br />
# <br />
# ICECC_BASEDIR="/var/cache/icecc"<br />
ICECC_BASEDIR="/var/cache/icecc"<br />
#<br />
# icecc scheduler log file<br />
#<br />
# ICECC_SCHEDULER_LOG_FILE="/var/log/icecc_scheduler.log"<br />
ICECC_SCHEDULER_LOG_FILE="/var/log/icecc_scheduler.log"<br />
#<br />
# If the daemon can't find the scheduler by broadcast (e.g. because <br />
# of a firewall) you can specify it.<br />
#<br />
# ICECC_SCHEDULER_HOST=""<br />
ICECC_SCHEDULER_HOST=""<br />
<br />
<br />
=== Local Configuration ===<br />
<br />
A sample local.conf entry for icecc that does not distribute compiles jobs for native packages looks like this.<br />
Change the paths to match your setup<br />
<br />
PARALLEL_MAKE = "-j 10"<br />
ICECC_PATH = "/usr/bin/icecc"<br />
ICECC_ENV_EXEC = "/proj/oplinux-0.2/op-linux/branches/oplinux-0.2/tmp/icecc-create-env"<br />
ICECC_USER_CLASS_BL = " native"<br />
INHERIT += "icecc"<br />
<br />
<br />
<br />
=== Successes and Failures ===<br />
<br />
This whole explanation is probably highly dependent on the icecc version used. Please do add success reports here. Also note that a lot of packages turn PARALLEL_MAKE off, as they break if compiled on a single machine, although i have noticed that they do not fail under icecc. Any feedback on this would be helpful<br />
<br />
* mixing versions of the icecc package can create problems. For example the icecc package from dapper and edgy are incompatible.<br />
* I (Laibsch) have a working setup between two edgy machines now. I had trouble until I set ICECC_NETNAME and ICECC_SCHEDULER_HOST to the respective, pingable hostnames of the machines. This is weird since I am on a LAN (192.168.1.x) for both machines and there is no firewall.<br />
<br />
[[Category:User]]<br />
[[Category:FAQ]]</div>Laibschhttps://www.openembedded.org/index.php?title=ToolingUseCases&diff=2098ToolingUseCases2010-01-10T16:33:06Z<p>Laibsch: remove categorization</p>
<hr />
<div>= Overview =<br />
<br />
This page defines primary user-roles in using OpenEmbedded. The material resulted from some discussions at OEDEM that were truncated due to time restrictions.<br />
<br />
= Goals =<br />
<br />
The goal of identifying user-roles is to be able to categorize different tooling scenarios, and what types of users will be interested in specific features. Tools designed for role type may not be appropriate for other roles. For example, a GUI for recipe editing may not be helpful for an application developer that's looking to remote debug their application on a target. On the other hand, a simple press-button build GUI may not be interesting for a seasoned OE hacker.<br />
<br />
= Role Types =<br />
<br />
== Application Developer ==<br />
<br />
The application developer's main concern is developing and testing any given application on a target system. This person does not care nor want to learn much about the internal details of the build system or package metadata. The best possible case is that these systems are transparent and the developer is able to easily build and deploy applications to the target device.<br />
<br />
=== Primary Tooling Requirements ===<br />
<br />
* Build Application for Target<br />
* Debug Application on Target<br />
* Generate build system artifacts for Application (recipes)<br />
<br />
=== Ideas ===<br />
<br />
* Develop an Eclipse plugin to "Export project as Recipe"<br />
** For CDT (C/C++) projects make, automake recipes are generated<br />
** For Java projects java-library based recipies are generated<br />
** Python?<br />
** Initially wizard can just create a tarball of project sources<br />
** Integration with SCM plugins?<br />
** How to capture project dependencies?<br />
** How to define export target? OTE, cloud, etc.?<br />
<br />
== Distro Developer ==<br />
<br />
Distro developer's concern is to compose packages and configurations into a working system. The distro developer has deep knowledge of packages available in Linux, and how sets of packages work well together. Additionally the distro developer is not afraid to work deeply within the build system to make it better, and to produce better, more maintainable package metadata and target systems.<br />
<br />
=== Primary Tooling Requirements ===<br />
<br />
* Build system image <br />
* Create/edit distro definitions<br />
* Debug build problems<br />
* Visualize package dependencies<br />
<br />
== Package Developer ==<br />
<br />
The package developer is often a mix of the previous two role types. Often they have some knowledge of the build system and applications and build tools used to create those applications. They typically act as a bridge between pure application developers and the resulting target system that's produced. Package developers write recipes, debug applications, and debug build problems.<br />
<br />
=== Primary Tooling Requirements ===<br />
<br />
* Create and edit package metadata<br />
* Easily integrate package metadata into build system<br />
* Debug build issues<br />
* Visualize Package Dependencies<br />
<br />
=== Notes ===<br />
<br />
* OpenEmbedded Tools for Eclipse (OTE) was designed for this role type.<br />
<br />
== Target System User ==<br />
<br />
This role type typically is not exposed to package metadata, cross compilers, or build systems. They are system users, and as such, at times want to:<br />
<br />
* Generate system<br />
* Update system<br />
* Install packages<br />
* Configure package metadata<br />
<br />
=== Primary Tooling Requirements ===<br />
<br />
* install binary package on target<br />
* find new packages and package updates for target<br />
* resolve package dependencies<br />
<br />
=== Ideas ===<br />
<br />
* A GUI application that runs with a local install of OE that can<br />
** present a wizard style interface that allows users to build system images<br />
** download overlays and other non-default artifacts<br />
** select images, packages, distros, machines, etc.<br />
** have a simple 'installer' that does not require knowledge of bitbake/OE internals</div>Laibsch