Building the image

There are 2 ways to build the image, using make and by using bitbake directly. Using make all the build steps are automated, but there may be some steps not needed (like deleting kernel and U-Boot to force a rebuild). So, although easier, this may be a bit slower.

Manually running bitbake allows you to perform just the steps you want. And it allows running bitbake -k to continue the build even if the build of some recipes fail. So, if you know what you want to do and what not, this will be faster. For instance when you want to rebuild just some small recipes but not the kernel.

Build using make

From the same directory as make setup (my_Edison_Workspace):

    make image

make image has the advantage that it will always clean and rebuild kernel and U-Boot.

Manually build using bitbake

Change to the correct directory as instructed by the make setup script (see Setting up).

    cd /.../my_Edison_Workspace/test/out/linux64

    source poky/oe-init-build-env

Note: you need to source oe-init-build-env from every new konsole that you want to use to run bitbake.

    bitbake -k edison-image

Where did the build files go?

The results of bitbake will be found in out/current/build/tmp/deploy/images/edison/ which is what we will be using when installing manually to enable booting from SDHC or USB drive.

Postbuild

After make image has completed run make postbuild. This run the postbuild.sh script, which will create a complete image in out/current/build/toFlash/ ready for flashing using flashall or Flash Tool Lite. But before it does that it will also process the btrfs image and create a snapshot from that, see Automatically building and installing a btrfs snapshot.

If you have been building using bitbake directly and want to create the toFlash directory you need to run make postbuild from my_Edison_Workspace.