| Summary: | yocto-bsp error on 3.10 kernel | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Yocto Project Subprojects] Eclipse Plugin | Reporter: | Alexandru Georgescu <alexandru.c.georgescu> | ||||
| Component: | eclipse-plugin | Assignee: | Jessica <jessica.zhang> | ||||
| Status: | VERIFIED FIXED | QA Contact: | |||||
| Severity: | normal | ||||||
| Priority: | Medium | CC: | dvhart, ioanax.grigoropol, jessica.zhang, srifenbark, tom.zanussi, yp.ep.watcher, yp.watcher | ||||
| Version: | 1.5 | ||||||
| Target Milestone: | 1.5.1 | ||||||
| Hardware: | x86 | ||||||
| OS: | Multiple | ||||||
| Whiteboard: | 14 October 2013: Setting docs to not affected | ||||||
| OS type for building Yocto: | --- | Type of Regression: | --- | ||||
| Verified: | Documentation change: | No (bug/feature does not impact docs) | |||||
| Attachments: |
|
||||||
|
Description
Alexandru Georgescu
2013-10-09 14:12:25 UTC
I have the same behavior on different distros. After debugging the issue, it is due to latest changes in yocto-bsp tool. Eclipse plug-in relies on the following command format from yocto-bsp tool to return values:
export export BUILDDIR=/home/jzhang/poky/build;/home/jzhang/poky/scripts/yocto-bsp list karch
Architectures available:
powerpc
x86_64
arm
i386
mips
qemu
obviously, with the recent changes, now I'm getting
export BUILDDIR=/home/jzhang/poky/build;/home/jzhang/poky/scripts/yocto-bsp list qemu property \"linux-yocto_3.10\".new_kbranch
/bin/sh: bitbake: command not found
Couldn't get 'bitbake -e' output, exiting.
when trying to get kernel branches with the kernel selection.
Yes, this is expected - yocto-bsp has always expected the build environment sourced before use. i.e. from the bblayers parsing code: print "BUILDDIR not found, exiting. (Did you forget to source oe-init-build-env?)" So just source oe-init-build-env and you should be fine. Tom, Why we don't have to do the environment script before? Look at the bug report history, this is the change introduced lately, we have never change anything in our plugin code and before it used to work. Also, other command, e.g. export export BUILDDIR=/home/jzhang/poky/build;/home/jzhang/poky/scripts/yocto-bsp list karch still works without sourcing the environment file. (In reply to comment #4) > Tom, > > Why we don't have to do the environment script before? Look at the bug > report history, this is the change introduced lately, we have never change > anything in our plugin code and before it used to work. Also, other > command, e.g. export export > BUILDDIR=/home/jzhang/poky/build;/home/jzhang/poky/scripts/yocto-bsp list > karch still works without sourcing the environment file. You got lucky before - exporting BUILDDIR is only one of the things that oe-init-build-env does. And the karch code doesn't require bblayers to be parsed to accomplish. Basically being able to get bitbake -e output is the only way to fix bug 5106, which is what the fix for that does. It's never been expected that people would be running yocto-bsp without sourcing the environent first. https://bugzilla.yoctoproject.org/show_bug.cgi?id=5106 http://git.yoctoproject.org/cgit.cgi/eclipse-poky-kepler/commit/?id=a9bdd48af551f4b73d60cdab8a9fc357f8c4f737 http://git.yoctoproject.org/cgit.cgi/eclipse-poky-juno/commit/?id=69ed460f8eaeabc684a973d59be741b2f3f00bd7 This does not affect documentation. I am marking the doc field appropriately. Scott verified. |