As of openembedded-core commit 2b3ae58f5eaecc8474761c543ff5347aa0e3c4c8 hardfp
is enabled by default.
Signed-off-by: Trevor Woerner
---
README | 16
1 file changed, 16 deletions(-)
diff --git a/README b/README
index b2e89f3..7f4a499 100644
--- a/README
+++ b/README
@@ -49,7 +49
A release candidate build for yocto-2.3.rc3 is now available at:
http://autobuilder.yoctoproject.org/pub/releases/yocto-2.3.rc3
Please begin QA on this build as soon as possible.
Build hash information:
meta-intel : 112643bbb731a6ccac7f4f5bde7f78d8fa2f9c15
meta-qt4 : e120a2193be3982d55
Hello,
I finally figured out what was messing my build, and it was a poor
mistake from my side... I am posting it here for anyone who could encounter a
similar issue.
I did let my custom layer in my bblayer.conf. I did not think it could
break the build, but I forgot about the bbappends there.
On Sat, Apr 29, 2017 at 2:39 AM, Luca Carlon wrote:
> Hello,
> thank you very much for your advice. It seems I can build both a minimal
> image and rpi-basic-image. I would like to test to see if the Pi is able to
> boot with these images but it seems that the images directory does not
> contain