[yocto] esdk without using Poky?
gary at mlbassoc.com
Tue Nov 1 05:36:57 PDT 2016
On 2016-10-31 23:06, Paul Eggleton wrote:
> Hi Gary,
> On Mon, 31 Oct 2016 13:19:18 Gary Thomas wrote:
>> I'm trying to build an extensible SDK (eSDK) for my target and running into
>> a few problems.
>> gthomas at zeus:~$
>> /work/tmp/mlb-glibc-x86_64-arm-toolchain-ext-2.2+snapshot.sh MLB
>> @SDK_TITLE@ Associates Embedded (Poky/Yocto Powered) Extensible SDK
>> installer version 2.2+snapshot
>> Enter target directory for SDK (default:
>> You are about to install the SDK to "/home/gthomas/mlb_sdk".
>> Proceed[Y/n]? y Extracting SDK.........................................done
>> Setting it up...
>> Extracting buildtools...
>> Preparing build system...
>> Error: 'meta-poky/conf' must be a directory containing local.conf &
>> The first thing I notice is the banner which should read:
>> MLB & Associates Embedded (Poky/Yocto Powered) Extensible SDK installer
>> version 2.2+snapshot
> Ah, I see what's going wrong here - we're doing a sed replacement and the
> ampersand is being interpreted as an "insert matched string" directive - my
> fault. I'll insert some escaping.
>> The second is that I use my own distribution (not poky). How can I
>> build an eSDK using my distribution?
> FYI the eSDK will use whatever you set in DISTRO - you have your own
> distribution, but I assume you are still referencing poky - perhaps as an
> include from your distro configuration? At least meta-poky must be in your
> bblayers.conf, otherwise I don't think you'd be getting this error.
> Regardless of that, there is a bug here somewhere. What do you have under
> layers/ in the generated SDK? Are you setting TEMPLATECONF anywhere?
I don't have meta-poky, nor any mention of poky, in any of my layers.
I'm still relying on the poky GIT tree, but that's for historical reasons
(started long before the OE-core split).
Perhaps you could try a build with a different distro (other than poky)
and see what happens? Or if you can recommend something I could try, I'm
more than happy to give it a go.
>> Once I ran into this error, I tried rebuilding using the [old] SDK.
>> I noticed that it seemed to rebuild [most] everything all over again.
>> Is there no shared state / reusable components between the eSDK and SDK?
> The extensible SDK and standard SDK are quite different - the host part of the
> extensible SDK is built out of -native rather than nativesdk- components
> (aside from buildtools-tarball, that is) so there are lots of things that need
> to be built if you subsequently build the standard SDK and you haven't done so
> already. It shouldn't be "almost everything", but I appreciate it's often hard
> to tell.
Fair enough and as you say, it's hard to tell what's rustling under the covers :-)
>> Finally, since I had to install SDK and not eSDK, I'm missing some tools
>> I was hoping to have. I want to build PRU programs for the BeagleBoneBlack
>> and I'm using meta-ti to import those tools and programs. I was expecting
>> the PRU tools which come from ti-cgt-pru-native to be included with my
>> eSDK/SDK, but they don't seem to be, at least not in the SDK. How can I
>> get these tools available so I can use the SDK to develop PRU code for the
> Not sure exactly, but for the standard SDK I would assume you'd need to append
> nativesdk-<something> to TOOLCHAIN_HOST_TASK so that those tools get included.
> Aside from the BSP setting that variable (which probably isn't a good idea)
> there isn't currently a means of host tools automatically getting pulled into
> the SDK based on the target, though it has been discussed .
OK, once I get past the 'meta-poky' issue, I can see what I need to do using
this nativesdk-XXX packaging.
>  https://bugzilla.yoctoproject.org/show_bug.cgi?id=5429
Thanks for your help
Gary Thomas | Consulting for the
MLB Associates | Embedded world
More information about the yocto