>>when populate_sdk gives you an SDK I dont understand why this is a requirement Now i remember.. This link was the reason that I was not using populate_sdk to build SDK for me..

Hi Daniel, On 07/10/2014 15:05, Daniel C. A (NESTIT) wrote: Have you asked over at the meta-freescale list? As you know, driver support is likely to be closely linked to

anyone?

However, a new problem occurs. Now when I tries run HelloWorld binary, after "Hello World" is printed, the terminal also prints "Segmentation fault". It seems that some memory problems occurs. I guess

Problem solved! It turns out it is the mismatch of ld-linux.so. I referred to this post

That's how I roll - after I lost few SSD drives by constantly building and rebuilding stuff, I ended up shoving 64GB of RAM into my gear and building into RAM-based tmpfs. Of course, there are size

i suspect this is an armv7 soft-float vs hard-float mismatch. Either your prebuilt OE system is configured with soft-float and the toolchain you use compiled for hard-float by default, or the other

whats running on board ? make sure that it has ldso in same directory and name as encoded in binary. it seems there is a mismatch. Try /lib/ld-linux.so.XXX ./a.out does that run ?

Attendees: Stephen, Belen, Paul, Armin, Joe, Richard, Tom, Saul, Sona, Mark, Michael, Alin, Matthew, Ross, Cristian, * Opens collection - 5 min (Stephen) * Yocto Project status - 5 min

Hi all, I would like to bring up following security issue in this meeting if there is interest for it in the group: - Collaboration within Yocto project when a critical vulnerability like

I've raised the bug in bugzilla. https://bugzilla.yoctoproject.org/show_bug.cgi?id=6816 Chris

Hi, Presently im working on i.mx6 EVK for Automotive application. I have used ‘fsl-image-gui’ which was Bitbaked using Yocto-dora release. Since I’m worked on CAN interfaces, I

Hi Chris, Presumably lm_sensors (recipe lmsensors in meta-oe) would work for this? Cheers, Paul -- Paul Eggleton Intel Open Source Technology Centre

Hi, I am new to Yocto Project and learning to develop software on Atmel SAMA5D3 Xplained board, on which Yocto 1.5.1 is pre-built. I followed the instructions and got the 1.6.1 toolchain

Hi, I am unable to understand how toolchain decides libraries and header files deployment into SDK path. Which factors of recipe decides about the path to deploy header file, libraries or binary

<chris.carr@...> wrote: So we're found a difference in behaviour between the rpm and opkg backends. Can you file a bug for the opkg backend in bugzilla? (oe-core->deployment). Ross

I've switched over to the RPM package manager and rebuilt the deploy image. From the list that I had in BAD_RECOMMENDATIONS, none of the packages appear in the deploy image. Chris

Tuesday, October 7, 2014 8:00 AM US Pacific Time Agenda: * Opens collection - 5 min (Stephen) * Yocto Project status - 5 min

If you are asking about BeagleBone Black specifically, then meta-ti does provide accelerated GLES 3D graphics for SGX over HDMI. On other devices, built-in LCD is also supported, but not LCD cape,

Which, if any, of these choices is suitable for accelerated graphics? Which device(s) will that choice support? HDMI, LCD cape, ??? Can accelerated graphics, e.g. SGX, be supported by QT5? If so,