[yocto] How to compile and install a recipe natively

How can i instruct yocto to compile and install a package for example opencv natively and for the target. In my recipe I've added RDEPENDS += "opencv " and yocto installs the libraries in the target rootfs. But now i'd like the libraries compiled natively and installed to x86_x64-linux rootfs.

[yocto] [yocto-autobuilder][PATCH] /buildset-config.controller/eclipse-plugin-*

We are no longer supporting kepler or luna. Remove the build set for those and remove luna from yoctoAB.conf. Signed-off-by: Graydon, Tracy --- buildset-config.controller/eclipse-plugin-kepler.conf | 10 -- buildset-config.controller/eclipse-plugin-luna.conf |

[yocto] How to build an SDK toolchain for native x86_64

Hi folks, Here’s my current setup and current situation: Host: x86_64 Target: aarch64 Build core-image-base for aarch64 - OK populate_sdk for aarch64 - OK My application and it unit tests also gets compiled to aarch64. What I wanted now would be something like run populate_sdk for

[yocto] BBMASK does not work

Hello, Yocto. I am quite puzzled with this and spent a few hours today so far. In case you have any comment or suggestion, it would be a great help. I am trying to hide one of the .bbappend files from the tree, so that BB won't complain "ERROR: No recipes available for:" error. I did add

[yocto] [eclipse-poky][PATCH] Drop bc from build

[YOCTO #10032] BitBake Commander has been bit-rotting for years and it was decided to deprecated it in 2.1. Drop it from the build. Signed-off-by: Tim Orling --- features/org.yocto.sdk.site/category.xml | 4 features/org.yocto.sdk.site/site.xml | 2 ++

Re: [yocto] Cortex-M4 build support

On Tue 2016-09-13 @ 01:15:49 PM, Khem Raj wrote: > > > On Sep 13, 2016, at 10:31 AM, robert.berger@gmane > > wrote: > > > > Hi, > > > > Shouldn't it be possible to build a bare-metal Cortex-M4 compiler with the > > YP and build a small RTOS like FreeRTOS

Re: [yocto] [meta-raspberrypi] WiFi

I saw your *name* in this list and you do nice posts, but had *I* never 2016-09-15 11:59 GMT-03:00 Daniel. : > 2016-09-15 10:56 GMT-03:00 Gary Thomas : >> On 2016-09-15 15:32, Daniel. wrote: >>> >>> Garry, if you are facing problems posting and detailed

Re: [yocto] [meta-raspberrypi] WiFi

2016-09-15 10:56 GMT-03:00 Gary Thomas : > On 2016-09-15 15:32, Daniel. wrote: >> >> Garry, if you are facing problems posting and detailed description of >> your problem and by detailed I mean "I do X expecting Y but got Z" >> being Z errors, logs, outputs etc would help a lot

Re: [yocto] No /lib64 directory in yocto

On 15 September 2016 at 15:51, Nadikuda, Lavanya < lavanya.nadik...@us.fujitsu.com> wrote: > What if I want both the directories. > > So Set libdir to one, install a symlink for the other. Ross -- ___ yocto mailing list yocto@yoctoproject.org

Re: [yocto] No /lib64 directory in yocto

On 14 September 2016 at 22:44, Nadikuda, Lavanya < lavanya.nadik...@us.fujitsu.com> wrote: > Could you please let me know what the resolution is for /lib64 directory > not found in yocto. > > If you're bothered by this, you can change your base_libdir to be /lib64 instead of /lib. Ross --

Re: [yocto] No /lib64 directory in yocto

Hi Burton, Thank you for your reply. What if I want both the directories. I am looking at the following link too: http://lists.openembedded.org/pipermail/openembedded-core/2013-August/082241.html Lav From: Burton, Ross [mailto:ross.bur...@intel.com] Sent: Thursday, September 15, 2016 9:48 AM

[yocto] [prelink-cross] Support x32 libx32 directory

Cross-prelink's prelink-rtld is missing suport for the /libx32 directory used with the x86_64 x32 ABI. This patch adds such support. 2016-09-14 Joseph Myers * src/rtld/rtld.c (load_ld_so_conf): Add argument use_x32. (main): Update call to

[yocto] : warning creating a DT_TEXTREL in a shared object.

Hi All, I am now trying to build one recipe on Yocto 2.0 based environment. However, I am seeing following warning & stops the build.I wonder if this is a known problem and you already have workaround? arm-pokymllib32-linux-gnueabi/5.2.0/ld: warning: creating a DT_TEXTREL in a shared object.

Re: [yocto] No /lib64 directory in yocto

Hi Kishore, Could you please let me know what the resolution is for /lib64 directory not found in yocto. Thank You, Lavanya. -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [meta-raspberrypi] WiFi

On 2016-09-15 15:32, Daniel. wrote: Garry, if you are facing problems posting and detailed description of your problem and by detailed I mean "I do X expecting Y but got Z" being Z errors, logs, outputs etc would help a lot people to help you. A reasonable observation (although if you look

Re: [yocto] [meta-raspberrypi] WiFi

Garry, if you are facing problems posting and detailed description of your problem and by detailed I mean "I do X expecting Y but got Z" being Z errors, logs, outputs etc would help a lot people to help you. 2016-09-15 10:07 GMT-03:00 Gary Thomas : > Any hints on how to get the

[yocto] [meta-raspberrypi] WiFi

Any hints on how to get the WiFi to go on the RaspberryPi-3? -- Gary Thomas | Consulting for the MLB Associates |Embedded world --

Re: [yocto] Adding ntfs3g to image and mouting ntfs partitions!?

I Mathieu, Thanks for the advice, I never had "weird errors", to be honest I was thinking about "what I need to do to get distro X vallidated", but this is a topic for another question. The error is the same... I found that the meta-openembedded/meta-filesystems layer wasn't included in my

Re: [yocto] [meta-raspberrypi] Schizophrenic build

On Wed, Sep 14, 2016 at 2:02 AM, Gary Thomas wrote: > I just built for my shiny new RaspberryPi-3 and noticed this: > $ ls -l tmp/work > total 32 > drwxrwxr-x 13 gthomas gthomas 4096 Sep 13 05:40 all-amltd-linux > drwxrwxr-x 3 gthomas gthomas 4096 Sep 13 05:36

Re: [yocto] Adding ntfs3g to image and mouting ntfs partitions!?

Hi, it seems to me that the name of the recipe is ntfs-3g-ntfsprogs and not just ntfs-3g. PS: I'm not sure using arch linux is a good choice for yocto builds, you get a lot of updates and that will probably result in weird errors quite often. I would advise to use a supported distro, maybe in