Hi Jessica,thank you for the info, I extracted the rootfs using
runqemy-extract-sdk and so now ADT global preferences (from
window->preferences) has the following info
-prebuilt standalone toolchain: /opt/poky/1.4.1/ (choosing the the toolchain
from the build directory and pointing to dir : /bu
Hi Jessica,thank you for the info, I extracted the rootfs using
runqemy-extract-sdk and so now ADT global preferences (from
window->preferences) has the following info
-prebuilt standalone toolchain: /opt/poky/1.4.1/ (choosing the the toolchain
from the build directory and pointing to dir : /bu
Hello everyone,I created a "hello world" ADT C application (basically following
the PDM
http://www.yoctoproject.org/docs/latest/dev-manual/dev-manual.html#application-development-workflow
)
The guide gives directions to run the built application in a qemu instance.
However, this fails. The rea
This mail was sent out by Package Report System.
It will list all the recipes which can't check upstream version by script, and
will show how long it is since their last mannual version check.
You can check the detail information at
http://packages.yoctoproject.org/manuallychkinfo
PackageName
This mail was sent out by Package Report System.
This message list those recipes which need to be upgraded. If maintainers
believe some of them needn't to upgrade this time, they can fill in
RECIPE_NO_UPDATE_REASON_pn-"xxx" in upstream_tracking files to ignore this
recipe remainder until newer u
I have followed the directions on this page:
https://github.com/gumstix/Gumstix-YoctoProject-Repo
The results are a failure in do_package for u-boot. It appears that the
u-boot tools have been built for the build host which don't match the
target architecture and that gets flagged as an error
