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.
This way I can do very quick edit-compile-run cycles until it's stable
enough to be integrated into openembedded.
I do this by pathing in the toolchain.
In fact, I just hack up my environment to add all the ~/.oe stuff in, but
the other thing I do is path in the toolchain.
I put my script in the following to my PATH.
/home/aland/src/setup-scripts/build/tmp-angstrom_v2012_05-eglibc/sysrootfs/x86_64-linux/usr/bin/armv7a-angstrom-linux-gnueabi
When I built a package and want to use it, then I do:
./configure --host=arm-angstrom-linux-gnueabi
It will give some warning as the following:
configure: WARNING: if you wanted to set the --build type, don't use
--host.
If a cross compiler is detected then cross compile mode will be used
And since openembedded has the ability (in theory at least ;-) to
create an SDK I thought I'd have a go at it. But now I'm at the point
where I concider dropping the "SDK" and just using the toolchain and
sysroot right from the build dir and be done with it.
Which is what I do above. ;-)
--
Regards,
Alan
_______________________________________________
Angstrom-distro-devel mailing list
Angstrom-distro-devel@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
