On 12/19/2012 02:06 AM, Bjørn Forsman wrote:
On 19 December 2012 05:09, Peter Kurrasch gtin...@hotmail.com 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
On 19 December 2012 13:45, Philip Balister phi...@balister.org 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)
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.
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
Hi,
I'm trying to generate an SDK to accompany a systemd-image, but I get
an error (see below).
I have asked on OE-core and was told that I needed yocto 1.2+ version
to get the generic populate_sdk task. So I switched from the master
branch (of the setup-scripts repo) to
On Tue, 18 Dec 2012, Bjørn Forsman wrote:
I have grepped for dropbear and openssh in sources/meta-angstrom,
but I haven't found anything yet.
Those are not in meta-angstrom, they are in
meta-openembedded/openembedded-core.
I can't explain why your systemd-image doesn't work.
Have you
On 18 December 2012 20:19, Alan DuBoff al...@softorchestra.com wrote:
On Tue, 18 Dec 2012, Bjørn Forsman wrote:
I have grepped for dropbear and openssh in sources/meta-angstrom,
but I haven't found anything yet.
Those are not in meta-angstrom, they are in
On Tue, 18 Dec 2012, Bjørn Forsman wrote:
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 populate_sdk thingy came
in yocto 1.2+).
Patient: Doctor, when I bang my head against the
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 populate_sdk thingy came
in yocto 1.2+).
...snip...
I pull the setup-scripts from github and execute the following:
$
On 19 December 2012 03:07, Alan DuBoff al...@softorchestra.com wrote:
On Tue, 18 Dec 2012, Bjørn Forsman wrote:
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 populate_sdk thingy
On 19 December 2012 05:09, Peter Kurrasch gtin...@hotmail.com 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 populate_sdk thingy came
in yocto 1.2+).
11 matches
Mail list logo
