OpenEmbedded requires some environment setup in order to function properly. If you would like this cache to be located elsewhere, now is the time to edit build/conf/nf and set DL_DIR as appropriate. By default this source code cache will be placed in overo-oe/sources. If you have installed the build system in a different location you will need to edit overo-oe/build/profile and change the definition of OVEROTOP as appropriate.Īs part of the build process OpenEmbedded downloads source code tarballs for the linux kernel, compiler, and other software packages. If you have followed the example installation and placed the build system in overo-oe in your home directory, you are now ready to proceed to the next step. To make this a somewhat easier task, there is a template for the required files in the openembedded installation we just did.Ĭopy these files to your overo-oe directory: We now will create a profile script and the configuration files required to tailor OE to our needs. $ git clone git:///bitbake bitbakeĬreating the OE configuration files and profile $ git checkout -track -b overo origin/overo $ git clone git:///gumstix-oe/mainline.git Then we will install the OE metatdata, and check out the overo branch (you can safely ignore the warnings you will get from the git commands): If you decide to put it elsewhere you will need to make appropriate alterations to the steps below.įirst we will create the “overo-oe” directory and cd into it: These instructions will assume that you are installing the build system in your home directory under “overo-oe”. You should have at least 10GB of free space on your hard drive in order to do a complete build of the kernel and root file system images. With a typical DSL connection this step should take less than 20 minutes. Afterwards run 'sudo sysctl -p'įirst you'll want to check out the source files for OE build system (roughly 250 MB). Note 2: If you are using Ubuntu 8.04 or later you will also need to edit /etc/nf and set 'vm.vdso_enabled = 0' and 'vm.mmap_min_addr = 0'. Neglecting to do this will cause target system init file corruption and your build image will not boot! Run “sudo dpkg-reconfigure dash” and answer no when asked whether you want to install dash as /bin/sh.

If this is the case, then you will need to change /bin/sh to link to /bin/bash. Note 1: If you are using an Ubuntu distribution, it is likely that /bin/sh is linked to /bin/dash.

Le collectionneur de recettes erreur