It looks like OE is building x-load and u-boot, but I'm not sure where to pick up the resulting files. Should I just grab them out of the working directory? I'd definitely have to keep an eye on this, since I can only afford to keep around one working directory at a time.
Hello,
It looks like OE is building x-load and u-boot, but I'm not sure where to pick
up the resulting files. Should I just grab them out of the working directory?
Typically, at the same level as the work dir, there is the deploy dir.
That's where the end results (typically bootloader, kernel and
filesystem images) get copied for deployment.
I'd definitely have to keep an eye on this, since I can only afford to keep
around one working directory at a time.
There is an OpenEmbedded BitBake class that cleans up the source and
build after each package has built. Something called rm_work or
similar. Look in classes/
Inherit that class from your local.conf. See the documentation on
this, I don't have time to look it up for you while typing this
currently.
Regards,
Leon Woestenberg wrote:
Typically, at the same level as the work dir, there is the deploy dir.
That's where the end results (typically bootloader, kernel and
filesystem images) get copied for deployment.
The only things I'm finding are dbg and dev ipks (empty), and pre-staging with build info.
# find|grep -v ipk
.
./glibc
./glibc/images
./glibc/images/beagleboard
./glibc/images/beagleboard/my-image-beagleboard.tar.gz
./glibc/images/beagleboard/uImage-2.6.26+2.6.27-rc7+r11+gite1c49d7d22af768188e2a54c167ed79919361e55-r11-beagleboard.bin
./glibc/images/beagleboard/modules-2.6.26+2.6.27-rc7+r11+gite1c49d7d22af768188e2a54c167ed79919361e55-r11-beagleboard.tgz
./glibc/images/beagleboard/uImage-beagleboard.bin
./glibc/addons
./glibc/addons/arm-angstrom-linux-gnueabi-angstrom-beagleboard-devshell
./glibc/pstage
./glibc/pstage/angstromglibc
./glibc/pstage/opkg.conf
./glibc/pstage/angstromglibc-home-jlove-oe-arm7
./glibc/pstage/stamp-cache-staging
./glibc/pstage/stamp-cache-cross
./glibc/pstage/pstaging_lists
# find|grep u-boot
./glibc/pstage/angstromglibc/staging-u-boot-beagleboard-angstrom-linux-gnueabi_git-r18_i686-linux.ipk
./glibc/pstage/angstromglibc-home-jlove-oe-arm7/staging-u-boot-mkimage-openmoko-native-i686-linux_1.2.0+git9912121f7ed804ea58fd62f3f230b5dcfc357d88svn2238-r1_i686-linux.ipk
./glibc/ipk/beagleboard/u-boot-dbg_git-r18_beagleboard.ipk
./glibc/ipk/beagleboard/u-boot-dev_git-r18_beagleboard.ipk
# find|grep x-load
./glibc/pstage/angstromglibc/staging-x-load-beagleboard-angstrom-linux-gnueabi_1.42+r7+git73eb0caf065b3b3f407d8af5c4836624e5cc7b69-r7_i686-linux.ipk
./glibc/ipk/beagleboard/x-load-dev_1.42+r7+git73eb0caf065b3b3f407d8af5c4836624e5cc7b69-r7_beagleboard.ipk
./glibc/ipk/beagleboard/x-load-dbg_1.42+r7+git73eb0caf065b3b3f407d8af5c4836624e5cc7b69-r7_beagleboard.ipk
There is an OpenEmbedded BitBake class that cleans up the source and
build after each package has built. Something called rm_work or
similar. Look in classes/
Good to know, but having the most recent build around is handy for debugging and hacking - I just don't have space for two of them.