On 12/19/2012 02:06 AM, Bjørn Forsman wrote:
> On 19 December 2012 05:09, Peter Kurrasch wrote:
>> Previously...
>>
I only switched the branch of setup-scripts to
angstrom-v2012.12-yocto1.3. Because in master "bitbake systemd-image
-c populate_sdk" doesn't work at all (as the popula
On 19 December 2012 13:45, Philip Balister wrote:
[...]
> I am pretty sure populate_sdk is new to 1.3.
Agreed. When I wrote 1.2+ above I meant that it arrived *after* 1.2. I
should have been more clear.
But my problem is not populate_sdk in itself, but why (and how to fix)
"bitbake systemd-image
On Wed, 19 Dec 2012, Bjørn Forsman wrote:
Hehe :-)
Thankfully you have a sense of humor...:-)
Yes it works. But it's not what I want. I want to make the target
device mount its rootfs over NFS and have the toolchain that
openembedded built available for my out-of-openembedded application.
Th
On Wed, 19 Dec 2012, Bjørn Forsman wrote:
Yeah, TI has their own SDK(s) and I have no idea how that maps into
openembedded. I think TI often use the CodeSourcery (now Mentor)
toolchain for their SDKs.
I think Angstrom uses it indirectly, IOW, I think it is the one
incorporated into the build
