[yocto] How to install kernel objects in /lib

Hi, I made a recipe to build and install a kernel object. See SUMMARY = "Kernel module for EPIX grabber" LICENSE = "CLOSED" inherit module SRC_URI = "file://Makefile \ file://pixcilnx_aarch64_4.4.a \ file://pixcipub.c \ file://pixcipub.h \ file://pixc

[yocto] LINUX_VERSION issue in recipe

Hi, This must be a stupid basic question. I have the following recipe append: keymaps_1.0.bbappend - FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}:" SRC_URI_append = " file://keymaps.service \ file://key

Re: [yocto] LINUX_VERSION issue in recipe

/2018 5:34 PM, Andre McCurdy wrote: > >> On Fri, Apr 27, 2018 at 3:44 AM, Damien LEFEVRE >> wrote: >> >>> Hi, >>> >>> This must be a stupid basic questi

[yocto] Splash screen using systemd

Hi, I'm working on an NVidia Jetson board with a TX2 module and I would like to have splash screen with a progress bar when booting and shutting down. The board boots to an application embedded style. There's no desktop and no user login. The configuration I use makes use of systemd. I gave a tr

[yocto] LIC_FILES_CHKSUM: spaces in file names

Hi, I have a base recipe generated with devtool. The package I build has several license files which contain space characters in the file names. LIC_FILES_CHKSUM = "file://COPYRIGHT.md;md5=b229ca0c79785e9e86311477e7bdd9ea \ file://LICENSES/MIT License.txt

Re: [yocto] LIC_FILES_CHKSUM: spaces in file names

Thanks Mark it works. -Damien On Tue, May 15, 2018, 17:29 Mark Hatle wrote: > On 5/15/18 7:25 AM, Damien LEFEVRE wrote: > > Hi, > > > > I have a base recipe generated with devtool. > > > > The package I build has several license files which contain space &

[yocto] native recipe question

Hi, I'm having to build a package (arrayfire) for Tegra. This package requires to first build a x86_64 utility (bin2cpp) which is then used for building the tegra arrayfire. Do I understand correctly that I should create: - arrayfire-native.bb: for compiling the x86_64 utility. If so how do I

Re: [yocto] native recipe question

22, 2018 at 12:19 PM, Burton, Ross wrote: > On 22 May 2018 at 08:43, Damien LEFEVRE wrote: > > I'm having to build a package (arrayfire) for Tegra. This package > requires > > to first build a x86_64 utility (bin2cpp) which is then used for building > > the tegra

Re: [yocto] native recipe question

OK I got it now. Thanks! On Tue, May 22, 2018 at 2:00 PM, Burton, Ross wrote: > On 22 May 2018 at 11:56, Damien LEFEVRE wrote: > > The recipe builds. When I try using with DEPENDS += "arrayfire-native" > in > > the arrayfire recipe I get this warning: >

[yocto] Image specific configuration files

Hi, For the same MACHINE I create the following images: - myimage-production - myimage-rnd - myimage-retail The production one has production assisted tools for flashing peripheral HW, testing vital HW components, writing some serial numbers, etc. The rnd one has more packages than the retail on

Re: [yocto] Image specific configuration files

Thanks a lot everyone, this is very helpful =) On Fri, Jun 1, 2018 at 2:14 PM, Iván Castell wrote: > > > 2018-06-01 11:24 GMT+02:00 Alexander Kanavin : > >> I have to say defining multiple distros and then tweaking recipes >> according to those definitions is not a good practice, as recipes shou

[yocto] bbappend extra SRC_URI ignored

HI, I'm working on meta-tegra layer and I'd like to append a recipe. The original recipe looks like this: https://github.com/madisongh/meta-tegra/blob/rocko-l4t-r28.2/recipes-bsp/tegra-binaries/tegra-tools_28.2.0.bb

Re: [yocto] bbappend extra SRC_URI ignored

_URI_prepend_tegra186 = "file://nvpmodel.conf " -Damien On Thu, Jun 14, 2018 at 3:24 PM, Robert P. J. Day wrote: > On Thu, 14 Jun 2018, Damien LEFEVRE wrote: > > > HI, > > I'm working on meta-tegra layer and I'd like to append a recipe. The > original recipe lo

Re: [yocto] bbappend extra SRC_URI ignored

work/aarch64_tegra186-poky-linux/tegra-tools/28.2.0-r0 in my case. Could some bitbake options disable this standard behavior? On Thu, Jun 14, 2018 at 3:33 PM, Martin Jansa wrote: > On Thu, Jun 14, 2018 at 03:16:00PM +0300, Damien LEFEVRE wrote: > > HI, > > > > I'm work

Re: [yocto] bbappend extra SRC_URI ignored

gra-tools). > > On Thu, Jun 14, 2018 at 3:22 PM Damien LEFEVRE > wrote: > >> >> Thanks >> >> Here are some interesting parts of bitbake -e. It seems my syntax is >> correct >> >> >> # $FILESEXTRAPATHS [3 operations] >> # set? /home/dami

[yocto] Adding new machine type with boot2qt

Hi, I have been working with the jetson reference board with a NVidia TX2 module. I have completed my image and everything runs as expected on the reference board. The final product will run on a different carrier, made by ConnectTech. http://connecttech.com/product/astro-carrier-for-nvidia-jetso

[yocto] preferred version 6.% of gcc-sanitizers not available

Hi, I have updated my stack to sumo and the platform image builds fine. Now I'm adding an application which builds against CUDA 9 and due to some bugs with gcc 7, gcc 6 is highest supported version. The issues has been fixed in CUDA 10, but I cannot upgrade at time point of time. So I went to my

[yocto] Replacing a configuration file from another recipe

Hi, In our base image we use nginx. I created a nginx.bbappend to add our PHP configuration in a separated layer. For a specific variant of the image I need to add an extra bit of nginx configuration. I though I could create a new recipe to overwrite nginx.conf and include that recipe in the var

[yocto] PR Service multibranch project

Hi, I'm looking at enabling PR Service to auto increment some recipe revision. On a build server I exposed sstate and downloads folder to use that server as a mirror. So I'm thinking of putting PR service there. Few things are unclear to me after reading the doc: We use repotool to manage our b

[yocto] Changing HOST_CC_ARCH temporarily in recipe

Hi, I have a package which requires to first build a x64 binary which is then used to compile the target platform binaries. The way I got away with it was to build that host binary from do_configure_prepend() and then continue with the build procedure. I recently upgraded to GCC7 + warrior and n

Re: [yocto] Changing HOST_CC_ARCH temporarily in recipe

Yeah that's true and that's how I fixed it =) Thanks, -Damien On Wed, Sep 18, 2019 at 11:44 AM wrote: > Hi, > > On Wed, Sep 18, 2019 at 11:26:29AM +0300, Damien LEFEVRE wrote: > > Hi, > > > > I have a package which requires to first build a x64 binary

[yocto] Nothing PROVIDES 'python3-dev'

Hi, Migrating from poky:pyro to poky:warrior. It looks like the python3-dev package is generated from python3-manifest.json: "dev": { "cached": [], "files": [ "${base_libdir}/*.a", "${base_libdir}/*.o", "${bindir}/python*-config",

Re: [yocto] Nothing PROVIDES 'python3-dev'

> On 24/09/2019 10:36, Damien LEFEVRE wrote: > > Hi, > > > > Migrating from poky:pyro to poky:warrior. > > > > It looks like the python3-dev package is generated from > > python3-manifest.json: > > > > ? ? "dev": { > > ? ? ? ? &q

Re: [yocto] Nothing PROVIDES 'python3-dev'

ep 25, 2019 at 10:00 AM Jussi Kukkonen wrote: > > > On Wed, 25 Sep 2019 at 09:16, Damien LEFEVRE wrote: > >> > On 24/09/2019 10:36, Damien LEFEVRE wrote: >> > > Hi, >> > > >> > > Migrating from poky:pyro to poky:warrior. >> > > &g

[yocto] do_fetch_append: syntax error

Hi, I have the following bbappend FILESEXTRAPATHS_prepend := "${THISDIR}/files:" SRC_URI += " \ file://tegra186_cti_defconfig \ " do_fetch_append(){ mv ${WORKDIR}/tegra186_cti_defconfig ${WORKDIR}/defconfig } For this I get an error: File "autogenerated", line 3 mv ${WORKDIR}/tegr

Re: [yocto] do_fetch_append: syntax error

OK understood! I'll find another way. Thanks, -Damien On Tue, Oct 1, 2019 at 12:13 PM Martin Jansa wrote: > On Tue, Oct 01, 2019 at 11:35:21AM +0300, Damien LEFEVRE wrote: > > Hi, > > > > I have the following bbappend > > > > FILESEXTRAPATHS_prep