Openembedded & Bitbake

[cstrand1]

I would like to develop for my Zaurus. (opie + 5600).  My frustration with getting going on it is, the development docs that are out there.  My current system that I have to work with is a HP Omnibook 6000 w/256mb ram and a 20GB HD (FC3).  Now, reading the docs about using Bitbake, there is no way my system could handle that.
*


Koen's reply...
Since a few weeks bitbake only uses 20MB for the package graph (instead of >1GB) and a typical build is about 6GB, so your laptop has a reasonable chance to build everything.

Okay, I followed the "Getting Started" steps and compiled nano.  It took a few hours, but it worked and I am psyched. I figured that would be a quick way to see if it works, no gui code.  It compiled and now I have a whole lot of .ipks.  I tried to install it (nano) and it fails on two dependencies.
"ERROR: Cannot satisfy the following dependencies for nano:
         libgcc1 (>= 3.4.4+csl-arm-20050603) libc6 (>= 2.3.5+cvs20050627)"
These were built when I ran bitbake to compile nano.

The question is then, do I need to install/update the dependencies that I just built?  Did I miss something in the configuration?  I would like to resolve this before building a gui app and ultimately, my own creation.

Thanks Chuck

[cstrand1]

What I did was to install it with "-force-depends".  It installed with warnings and nano runs.

[koen]

"ERROR: Cannot satisfy the following dependencies for nano:
         libgcc1 (>= 3.4.4+csl-arm-20050603) libc6 (>= 2.3.5+cvs20050627)"
These were built when I ran bitbake to compile nano.

The question is then, do I need to install/update the dependencies that I just built?  Did I miss something in the configuration?  I would like to resolve this before building a gui app and ultimately, my own creation.
[div align=\"right\"][{POST_SNAPBACK}][/a][/div]

You could try with -force-depends to see if it works, and if it doesn't, make a backup and install the new glibc and libgcc. It also depends on what type of image you are targeting (stock sharp, oz, pdaX, etc).

A lot of problems are covered in the OE mailinglist: [a href=\"http://thread.gmane.org/gmane.comp.handhelds.openembedded/]http://thread.gmane.org/gmane.comp.handhelds.openembedded/[/url] and in #oe at freenode.

[lardman]

Chuck,

This occurs because whenever you build something it updates all of the CVS packages - so if it depends on one of these it will then depend on a later version than you have on your Z.

One possibility it to set the CVSDATE in your local.conf, but I find that -force-depends works fine, and I may as well have the latest & greatest.

Were the docs clear enough, etc.? If not could you make (or suggest) corrections/clarifications to them to make others' progress smoother,

Thanks,


Si

[cstrand1]

Chuck,

This occurs because whenever you build something it updates all of the CVS packages - so if it depends on one of these it will then depend on a later version than you have on your Z.

One possibility it to set the CVSDATE in your local.conf, but I find that -force-depends works fine, and I may as well have the latest & greatest.

Were the docs clear enough, etc.? If not could you make (or suggest) corrections/clarifications to them to make others' progress smoother,

Thanks,


Si
[div align=\"right\"][a href=\"index.php?act=findpost&pid=86198\"][{POST_SNAPBACK}][/a][/div]

lardman or Simon, whatever moniker you prefer,

Thank you for your response.  Thinks are becoming clearer now as to how this all works.  The dependency thing makes sense and that is what I assumed it to be.

I will make/suggest anything that I can in the wiki to make it easier for others.

Now, this actually may go better in the thread that relates to "developers school", but anyway.  I think that I was originally looking for the easy way to get to this point.  When I originally got my Zaurus, I downloaded the four (4) rpm's for development.  Instant gratification.  Yesterday, I decided to be patient and follow the "Getting Started" directions, step by step.  Like I stated, I started with something minimal, nano.  What I ended up with was the toolchain, which is what I was looking for.  Now, based on what I have to develop on, I will never bitbake world/opie/gpe.  I will build indivdual packages as I like.  As I write this I am building opie-textedit.  I will take this experience and see if and what can be improved.

Chuck

[MB Zaurus]

lardman or Simon, whatever moniker you prefer,

Thank you for your response.  Thinks are becoming clearer now as to how this all works.  The dependency thing makes sense and that is what I assumed it to be.

I will make/suggest anything that I can in the wiki to make it easier for others.

Now, this actually may go better in the thread that relates to "developers school", but anyway.  I think that I was originally looking for the easy way to get to this point.  When I originally got my Zaurus, I downloaded the four (4) rpm's for development.  Instant gratification.  Yesterday, I decided to be patient and follow the "Getting Started" directions, step by step.  Like I stated, I started with something minimal, nano.  What I ended up with was the toolchain, which is what I was looking for.  Now, based on what I have to develop on, I will never bitbake world/opie/gpe.  I will build indivdual packages as I like.  As I write this I am building opie-textedit.  I will take this experience and see if and what can be improved.

Chuck
[div align=\"right\"][a href=\"index.php?act=findpost&pid=86209\"][{POST_SNAPBACK}][/a][/div]
[/quote]

Hmmm... What "four rpms" did you download? I'm really interested in building a cross-compilation environment, if I can't get development working on the Z itself (which is my preference).

I've looked at various "getting starting" guides, and they all seem prety involved, when my goal is to compile a single program (fxconv) to run under OE (3.5.3)/Opie.

Has anyone considered making an ISO snapshot of a complete, working toolchain environment, and putting it up for download?

Thanks,

Mark

[lardman]

Has anyone considered making an ISO snapshot of a complete, working toolchain environment, and putting it up for download?

We're discussing how to do this at the moment. There is already an opie test version on Mickeyl's web server btw (can't remember the URL off the top of my head though).

That said, if you could add fxconv to OE (the involved thing you were talking about  - though it's not all that involved to tell the truth) that would be good.


Si

[cstrand1]

Hmmm... What "four rpms" did you download? I'm really interested in building a cross-compilation environment, if I can't get development working on the Z itself (which is my preference).

The link to get the "four rpms" is ... https://www.oesf.org/index.php?title=Compiler_Setup.  This is/was for developing on the stock rom.

I will have to tell you, getting a cross compiling environment was not that painful.  As I previous;y stated, I did this on a HP 6000 laptop 256mb ram and a 20gb HD.  I followed the steps from "Getting Started", http://oe.handhelds.org/cgi-bin/moin.cgi/GettingStarted.  I had problems using the snapshot, so I followed the recommended setup.  It took a few hours and in the end I had a toolchain.  To get this, I ran bitbake nano.  Today, I ran bitbake opie-textedit and now I have the libraries I need to build a gui app.  All it took was  an hour or so.  The only thing left to fiqure out is how to create a .bb file.

I also found the docs in http://opie.handhelds.org quite helpful as well.  Somebody correct me if I am wrong, but I think one could take that toolchain and setup a cross-compiling environment to build their app outside of bitbake, following the docs in opie.handhelds.  I know this would bypass the openembedded build environment, but it could be accomplished.

Chuck