Chris Conroy wrote:
On Sun, 2009-11-22 at 15:45 +0100, Bernhard Kaindl wrote:
external-toolchain-generic,
external-toolchain:
* The current external-toolchain recipes which are documented to accept
toolchains built by meta-toolchain actually do not accept such because
they expect ${prefix}/package-status to exist which is provieded by
the poky toolchains but not the current OE meta-toolchain package.
Fix this by also looking for ${prefix}/usr/lib/opkg/status, which is the
package-status file of the OE meta-toolchain package.
* Also change the error message which is shown when neither file is found
more explicit.
What about changing the meta-toolchain to generate the environment-setup
script? While it's not important to have the script for normal building
of packages, I've found it helpful to be able to do a quick compile of a
test program here or there. Though, I understand that it might be
dangerous since some folks might think the environment-setup creates an
an entire cross building platform for them when they really want to stay
inside OE....
--Chris
meta-toolchain does generate environment-setup and so far as I am aware
it works fine as a stand-alone toolchain. Is there some reason why I
should not be using it as such?
Chris S.
_______________________________________________
Openembedded-devel mailing list
[email protected]
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
