Wiki seems dead. is openembedded wiki still active?
Hi,
After many years I wanted to play with ompenembedded again.
So I wanted to go to the wiki ( http://www.openembedded.org/ ) to get some info.
The wiki displays:
Quoted 5 lines
MediaWiki internal error.
Exception caught inside exception handler
Am I using the correct url? (it's at least the url also mentioned in wikipedia)
Is the Wiki just temporarily down and I was just unlucky enough to try to connect at the wromg time?
What I wanted to find out on the wiki:
- what branch / tag to checkout to have a consitant verison
- what to use as starting point for a minimalist x86 system being able to run under qemu (x86)
- How to add a gnu toolchain package to my minimalist target system
- what to use as starting point for a minimalist arm11 system being able to run under qemu (x86)
- what is the recommended way to run bitbake in a 64 bit environment (psyco is not working). Is pypy an option?
- what are the correct mailing lists for such questions
Thanks in advance for your answers
Quoted 5 lines · On Tuesday 23 August 2011 10:59:42 Klausfpga wrote:
Am I using the correct url? (it's at least the url also mentioned in wikipedia)
Is the Wiki just temporarily down and I was just unlucky enough to try to connect at the wromg time?
Yes that's the correct link, although the website is temporarily down; the appropriate people have apparently been informed and hopefully can fix it soon.
However the website/wiki can still be accessed under
http://wiki.openembedded.org.
Quoted 3 lines
What I wanted to find out on the wiki:
- what branch / tag to checkout to have a consitant verison
I'm not quite sure what you're asking here.
FYI OE is in the middle of a transition of sorts; we're moving to a more modular metadata structure based around a smaller common core (OE-Core). For more information please see this page:
http://wiki.openembedded.org/index.php/OpenEmbedded-Core
For new development work we would strongly recommend OE-core as a base, allowing you greater flexibility as well as avoiding some legacy cruft.
Quoted 2 lines
- what to use as starting point for a minimalist x86 system being able to run under qemu (x86)
"Minimalist" is somewhat subjective. OE-core alone provides a "qemux86" machine target, a distro-less basic configuration and a "core-image-minimal" image that provides a basic console-only system without package management.
Quoted 1 line
- How to add a gnu toolchain package to my minimalist target system
I think this is a case of adding "tools-sdk" to your IMAGE_FEATURES; someone else might be able to offer more help here.
Quoted 2 lines
- what to use as starting point for a minimalist arm11 system being able to run under qemu (x86)
Same as above except use "qemuarm" as the machine.
Quoted 2 lines
- what is the recommended way to run bitbake in a 64 bit environment (psyco is not working). Is pypy an option?
There's no specific recommended way; the psyco warning was just a warning and in any case if you're using a recent version of BitBake (as you need to for OE-core) then Psyco support has been removed and you won't get the warning.
Quoted 1 line
- what are the correct mailing lists for such questions
For OE-classic discussion as well as layers above OE-core, use the openembedded-devel mailing list. For OE-core use this list (openembedded- core). I suspect the openembedded-core list will merge into openembedded-devel at some point in the near future.
Cheers,
Paul
Signature · 2 lines
Paul Eggleton Intel Open Source Technology Centre
Quoted 3 lines · On Tuesday 23 August 2011 17:25:13 Paul Eggleton wrote:
Yes that's the correct link, although the website is temporarily down; the appropriate people have apparently been informed and hopefully can fix it soon.
FYI www.openembedded.org is now fixed.
Cheers,
Paul
Signature · 2 lines
Paul Eggleton Intel Open Source Technology Centre
Hi Paul,
Thanks for your detailed answer.
Quoted 5 lines · Paul Eggleton
Yes that's the correct link, although the website is temporarily down; the
appropriate people have apparently been informed and hopefully can fix it soon. Ok so just bad timing :-(
Quoted 8 lines
However the website/wiki can still be accessed under
http://wiki.openembedded.org.Quoted 5 lines
What I wanted to find out on the wiki:
- what branch / tag to checkout to have a consitant verison I'm not quite sure what you're asking here.
What I wanted to know was what to checkout best:
origin/master/ might not be a good idea, at least last time I tried
this I often
fell into inconsistent releases
origin/stable/2009 on the other hand had it's latest change in July 2010
Quoted 6 lines
Quoted 6 lines
FYI OE is in the middle of a transition of sorts; we're moving to a more modular metadata structure based around a smaller common core (OE-Core). For more information please see this page:
This looks interesting. Thanks for this info. I will read more on the wiki.
Quoted 6 lines
Quoted 2 lines
- what to use as starting point for a minimalist x86 system being able to run under qemu (x86)
"Minimalist" is somewhat subjective. OE-core alone provides a "qemux86" machine target, a distro-less basic configuration and a "core-image-minimal" image that provides a basic console-only system without package management.
Well with minimalist I meant kernel + base file system + busybox + package management
I will look at qemux86 and core-image-minimal
Quoted 6 lines
Quoted 1 line
- How to add a gnu toolchain package to my minimalist target system
I think this is a case of adding "tools-sdk" to your
IMAGE_FEATURES; someone else might be able to offer more help here.Quoted 2 lines
- what to use as starting point for a minimalist arm11 system being able to run under qemu (x86)
Quoted 8 lines
Same as above except use "qemuarm" as the machine.
Quoted 2 lines
- what is the recommended way to run bitbake in a 64 bit environment (psyco is not working). Is pypy an option?
There's no specific recommended way; the psyco warning was just a warning and in any case if you're using a recent version of BitBake (as you need to for OE-core) then Psyco support has been removed and you won't get the warning.
What I meant here is: Can pypy or somethign else be used in order to accelerate the
execution of BitBake.
Quoted 7 lines
Quoted 1 line
- what are the correct mailing lists for such questions
For OE-classic discussion as well as layers above OE-core, use the openembedded-devel mailing list. For OE-core use this list (openembedded- core). I suspect the openembedded-core list will merge into openembedded-devel at some point in the near future.
Thanks ance more
Quoted 3 lines · On Tuesday 23 August 2011 22:20:55 Klausfpga wrote:
What I wanted to know was what to checkout best:
origin/master/ might not be a good idea, at least last time I tried
this I often fell into inconsistent releases
If you mean the "openembedded" repository, there is the 2011.03-maintenance branch; however this is not the basis for future development. With the Yocto Project release coming up soon, OE-core should be fairly stable (or at least heading that way).
Quoted 2 lines
Well with minimalist I meant kernel + base file system + busybox + package management
Busybox is used by default and the rest is of course mandatory. I'm not entirely sure we have an image in OE-core that is just console with package management though; we really ought to sort that out if that's the case. Even so this is trivial to add, you just need "package-management" in the IMAGE_FEATURES for your image.
Quoted 2 lines
What I meant here is: Can pypy or somethign else be used in order to accelerate the execution of BitBake.
Not sure; I'm under the impression that Psyco made only a very small difference however. Most of the time taken running BitBake is in the tasks it runs (and the order it runs them); no generic Python tool is going to be able to improve that.
Cheers,
Paul
[1] http://www.yoctoproject.org
Signature · 2 lines
Paul Eggleton Intel Open Source Technology Centre
Quoted 7 lines · Paul Eggleton
On Tuesday 23 August 2011 10:59:42 Klausfpga wrote:
FYI OE is in the middle of a transition of sorts; we're moving to a more modular metadata structure based around a smaller common core (OE-Core). For more information please see this page:
The link to the Layer Index is broken on that page. I'd correct it, but that page is locked down to be only editable by admin.
Signature · 4 lines
Martyn Welch (Principal Software Engineer) | Registered in England and GE Intelligent Platforms | Wales (3828642) at 100 T +44(0)1327322748 | Barbirolli Square, Manchester, E [email protected] | M2 3AB VAT:GB 927559189
Quoted 11 lines · On Wednesday 24 August 2011 10:02:37 Martyn Welch wrote:
Quoted 7 lines · Paul Eggleton
On Tuesday 23 August 2011 10:59:42 Klausfpga wrote:
FYI OE is in the middle of a transition of sorts; we're moving to a more modular metadata structure based around a smaller common core (OE-Core). Formore information please see this page:
http://wiki.openembedded.org/index.php/OpenEmbedded-CoreThe link to the Layer Index is broken on that page. I'd correct it, but that page is locked down to be only editable by admin.
The link in the markup is fine, it seems to be some kind of server issue in how the real URL gets generated. Now that www.openembedded.org is back up you can just use that and it will work fine:
http://www.openembedded.org/wiki/OpenEmbedded-Core
Thanks for reporting this, I'll have a word with Tom K. and see if he can fix it so nobody else stumbles across this issue.
Cheers,
Paul
Signature · 2 lines
Paul Eggleton Intel Open Source Technology Centre
Hi Paul,
Quoted 15 lines · Paul Eggleton
Quoted 5 lines · On Tuesday 23 August 2011 10:59:42 Klausfpga wrote:
Am I using the correct url? (it's at least the url also mentioned in wikipedia)
Is the Wiki just temporarily down and I was just unlucky enough to try to connect at the wromg time?
Yes that's the correct link, although the website is temporarily down; the appropriate people have apparently been informed and hopefully can fix it soon.
However the website/wiki can still be accessed under
http://wiki.openembedded.org.Quoted 2 lines
What I wanted to find out on the wiki:
Quoted 7 lines
Quoted 1 line
- what branch / tag to checkout to have a consitant verison
I'm not quite sure what you're asking here.
FYI OE is in the middle of a transition of sorts; we're moving to a more modular metadata structure based around a smaller common core (OE-Core). For more information please see this page:
The wiki frontpage could be updated stating the current OE status at least stating the transition, I`m a newcomer and took some time trying the wiki howtos. I just figured out things after I read all the mailing list archives :)
Quoted 5 lines
http://wiki.openembedded.org/index.php/OpenEmbedded-Core
For new development work we would strongly recommend OE-core as a base, allowing you greater flexibility as well as avoiding some legacy cruft.
This is also important to highlight somewhere, maybe the wiki front page as well.
Regards,
Leandro Dorileo
Quoted 44 lines
Quoted 3 lines
- what to use as starting point for a minimalist x86 system being able to run under qemu (x86)
"Minimalist" is somewhat subjective. OE-core alone provides a "qemux86" machine target, a distro-less basic configuration and a "core-image-minimal" image that provides a basic console-only system without package management.
Quoted 1 line
- How to add a gnu toolchain package to my minimalist target system
I think this is a case of adding "tools-sdk" to your
IMAGE_FEATURES; someone else might be able to offer more help here.Quoted 2 lines
- what to use as starting point for a minimalist arm11 system being able to run under qemu (x86)
Same as above except use "qemuarm" as the machine.
Quoted 2 lines
- what is the recommended way to run bitbake in a 64 bit environment (psyco is not working). Is pypy an option?
There's no specific recommended way; the psyco warning was just a warning and in any case if you're using a recent version of BitBake (as you need to for OE-core) then Psyco support has been removed and you won't get the warning.
Quoted 1 line
- what are the correct mailing lists for such questions
For OE-classic discussion as well as layers above OE-core, use the openembedded-devel mailing list. For OE-core use this list (openembedded- core). I suspect the openembedded-core list will merge into openembedded-devel at some point in the near future.
Cheers,
PaulSignature · 7 lines
Paul Eggleton Intel Open Source Technology Centre _______________________________________________ Openembedded-core mailing list [email protected] http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core