Create New Image For Zaurus

[BerndS]

Hi,

I've successfully installed the OpenEmbedded development environment and compiled an image using "bitbake opie-image"

Now I want to create my own image with some more packages -- can anybody point me to a documentation about how to do that?

Thanks

Bernd

[utx]

Now I want to create my own image with some more packages -- can anybody point me to a documentation about how to do that?

Look at recipes/images. Most images consists from chain of tasks from recipes/tasks, ant these task recipes may contain another tasks or package recipes.

Why you need a special image? Isn't installation of a standard and installation of needed packages from feeds sufficient for you? Using standard image makes possible problems simpler to reproduce.

[BerndS]

Hi,

Look at recipes/images. Most images consists from chain of tasks from recipes/tasks, ant these task recipes may contain another tasks or package recipes.

Hmm, what I did until now is:

create a new description in the image directory

cp  packages/images/opie-image.bb  packages/images/my-opie-image.bb

In my-opie-image.bb I added "task-my-opie" to the IMAGE_INSTALL variable:

IMAGE_INSTALL = "task-base-extended task-opie-base task-opie-base-applets \
          task-opie-base-inputmethods task-opie-base-apps \
          task-opie-base-settings task-opie-base-decorations \
          task-opie-base-styles task-opie-base-pim \
          task-opie-extra-settings \
          task-opie-bluetooth task-opie-irda \
                    task-my-opie"

Then I created the task file task-my-opie.task:

$ cat packages/tasks/task-my-opie.bb
DESCRIPTION = "My Tasks for OPIE"
SECTION = "opie/base"
LICENSE = "MIT"

PR = "r12"

inherit task

PROVIDES = "task-my-opie"

PACKAGES = "opie-tetrix opie-solitaire opie-sheet opie-rdesktop \
            opie-notes opie-notesapplet opie-keypebble opie-ftp \
            opie-embeddedkonsole opie-calculator opie-write opie-zsafe \
            qpdf2 opie-wellenreiter zuc \
            screen \
            ldd \
            apache2 \
            cvs \
            e2fsprogs \
            dosfstools \
            bzip2 \
            gzip \
            grep \
            kexec-tools \
            less \
            lsof \
            mc \
            nfs-utils \
            procps \
            nmap \
            qpe-nmap \
            rsync \
            tar \
            tcpdump \
            glibc-localedata-de-de+euro \
            tzdata-europe \
            glibc-binary-localedata-de-de \
            file \
            util-linux-swaponoff"


RDEPENDS_task-opie-everything := "${PACKAGES}"

PACKAGES += "task-my-opie"

#
# Dependencies
#

# Recommend both landscape and portrait backgrounds
#RRECOMMENDS_task-my-opie = ""


And did a

 bitbake my-opie-iamge

The result was a working image --but without my added apps ...

Why you need a special image? Isn't installation of a standard and installation of needed packages from feeds sufficient for you? Using standard image makes possible problems simpler to reproduce.

In principle that would be enough : I've some scripts to customize my OPIE environment after the installation (e.g. change config files & and add packages).

But unfortunately kexec-boot does not find the image on the internal ram anymore if I install all packages in one go . It does find the image on the internal ram if I install a small number of packages (about 5); reboot the Zaurus, install the next 5 packages , etc.

I don't know the reason for this behaviour (I already asked on the openembbeded mailing list but did not get a solution for the problem).

That's why I want to have a image that already contains my customizations.

regards

Bernd

[utx]

In my-opie-image.bb I added "task-my-opie" to the IMAGE_INSTALL variable:

The result was a working image --but without my added apps ...

I guess that you need to to add task-my-opie to DEPENDS section as well. But I never customized the image.

Why you need a special image? Isn't installation of a standard and installation of needed packages from feeds sufficient for you? Using standard image makes possible problems simpler to reproduce.

But unfortunately kexec-boot does not find the image on the internal ram anymore if I install all packages in one go . It does find the image on the internal ram if I install a small number of packages (about 5); reboot the Zaurus, install the next 5 packages , etc.

I don't know the reason for this behaviour (I already asked on the openembbeded mailing list but did not get a solution for the problem).

It sounds like a problem either with JFFS2 filesystem or with kexecboot. But I know nothing about these two.

[agosine]

Hello Bernd.  Are you still working on compiling Opie?  I am trying to find a copy of 2008.1 and it seems compiling my own is the only way.  Any advice?

[Capn_Fish]

Build your own here (without OpenEmbedded):

http://amethyst.openembedded.net/~koen/narcissus/

[BerndS]

Hi,

Hello Bernd.  Are you still working on compiling Opie?  I am trying to find a copy of 2008.1 and it seems compiling my own is the only way.  Any advice?

yes, more or less ... Unfortunately I always get an error if I try to create a new image for 2007.12 or 2008.1. So from time to time I refresh my development tree and do a bitbake opie-image to see if it now works . Until now it did not work

But at this time I do not have the time to investigate why it does not work.

regards

Bernd

[agosine]

Build your own here (without OpenEmbedded):

http://amethyst.openembedded.net/~koen/narcissus/

I have tried it, but for some reason my Opie images always error out.  Have not spent enough time trying to figure out what I am missing.