Bug 8949 - Build extensible SDK on autobuilder
Summary: Build extensible SDK on autobuilder
Status: RESOLVED FIXED
Alias: None
Product: AutoBuilder
Classification: Infrastructure
Component: autobuilder (show other bugs)
Version: unspecified
Hardware: x86 Multiple
: High enhancement
Target Milestone: 2.1 M2
Assignee: Beth Flanagan
QA Contact: Aníbal Limón
URL:
Whiteboard:
Depends on:
Blocks: 9091
  Show dependency tree
 
Reported: 2016-01-19 19:18 UTC by Paul Eggleton
Modified: 2016-02-10 18:11 UTC (History)
4 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: No (bug/feature does not impact docs)

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Paul Eggleton 2016-01-19 19:18:34 UTC 
We need to start building the extensible SDK on the autobuilder, as we are building the standard SDK. This can be acheived by running the following:

  bitbake -c populate_sdk_ext <imagename>

We can use core-image-minimal as the image for now.
Comment 1 Alexandru Georgescu 2016-02-02 11:11:32 UTC 
Hi Beth,
As I see now, we have the eSDK built on public AB for core-image-minimal.
Can you also build for the core-image-sato-sdk?

Thanks,
AlexG
Comment 2 Aníbal Limón 2016-02-02 14:18:35 UTC 
(In reply to comment #1)
> Hi Beth,
> As I see now, we have the eSDK built on public AB for core-image-minimal.
> Can you also build for the core-image-sato-sdk?
> 
> Thanks,
> AlexG

I guess it will be core-image-sato instead of core-image-sato-sdk... may be i'm wrong.
Comment 3 Paul Eggleton 2016-02-02 19:40:46 UTC 
What are you hoping to test in addition with an SDK produced from core-image-sato?
Comment 4 Beth Flanagan 2016-02-10 17:10:51 UTC 
I'm marking this resolved for now. If you'd like to do core-image-sato for this, please open an additional bug.