Re: [yocto] Procedure to build the xfce UI for ODROID XU3 board

I cloned the meta-openembedded layer and added inside the poky. then changed the conf/bblayers.conf as follow. I found that meta-xfce layer depends on openembedded core, oe , multimedia , gnome, and python. so i made the following changes in the bblayers.conf file. OKY_BBLAYERS_CONF_VERSION =

[yocto] [meta-rockchip][PATCH v2] recipes-graphics: Add recipe for rockchip-mali

* add this recipe to download rockchip mali drivers * support X11,gbm-only,wayland backend on rk3036,rk3288,rk3399 * provide egl,gles,gbm,opencl library * depend on mesa to provide dev-package Signed-off-by: Jacob Chen --- recipes-graphics/libgles/rockchip-mali_git.bb |

Re: [yocto] [layerindex-web][PATCH 1/2] views.py: Redirect to recipe details for single results

This should be using a reverse() call instead of a hardcoded URL path suffix. However, since that was a trivial fix I've done that and merged it - it'll appear in the layer index once we do the next upgrade (fairly soon). Cheers, Paul On Tuesday, 14 March 2017 9:35:16 AM NZDT Jose Lamego

[yocto] [layerindex-web][PATCH 3/3] layerindex: add "No update" status to LayerItem

Add a status for a layer indicating it should not be updated. I don't expect this to be widely used (and is only settable from the admin interface) but would be useful if you have a legacy sub-layer that you want to prevent from being visible on certain branches - it will prevent the update script

[yocto] [layerindex-web][PATCH 2/3] update_layer.py: use DISTRO_NAME as primary distro short description

When reading conf/distro/*.conf to create distro records, attempt to parse the config file and use DISTRO_NAME (if set) to populate the description field for the record. If that's not set then fall back to the less commonly used meta-comment that we supported previously. Signed-off-by: Paul

Re: [yocto] [layerindex-web][PATCH 2/2] views.py: Consider layer name in recipe search

Hi Jose, Sorry for the delay in responding to this. I'd prefer if this were implemented like the recently added "inherits:" where we have a special prefix e.g. "layer:" in order to search for things in a particular layer. Then it's much clearer as to what's going on. Cheers, Paul On Tuesday,

Re: [yocto] [Openembedded-architecture] Proposal: dealing with language-specific build tools/dependency management tools

Alex - thanks for kicking off the discussion here, this is something we definitely need to get a better handle on. My involvement with this is perhaps somewhat accidental - I ended up working on the fetcher that was implemented by someone else because I needed it to work for devtool

Re: [yocto] [layerindex-web][PATCH 2/2] views.py: Consider layer name in recipe search

Ping. On 01/18/2017 04:19 PM, Jose Lamego wrote: > From: Alex Franco > > Recipe search cannot be narrowed to a specific layer, producing > unnecessary results. > > This change allows including a layers name when searching for recipes to > narrow the yielded

Re: [yocto] [Openembedded-architecture] Proposal: dealing with language-specific build tools/dependency management tools

On Fri, 2017-03-10 at 17:10 +0200, Alexander Kanavin wrote: Thanks for raising this topic. The problems we hit in adding node.js support clearly shows we would benefit from a common approach to supporting languages with their own and runtime and packaging. > > npm fetcher for instance was a

Re: [yocto] Devtool: Script Not found

On Fri, Mar 03, 2017 at 10:06:21AM +0530, SatyaNarayana Sampangi wrote: > Hi Denys, > > I am using linux-ti-staging 4.4, > > zImage--4.4.41+git0+7c580a51af-r22a-beaglebone-20170302194632.bin > > Image: core-image-minimal > > Could you pls clarify where i am going wrong? Numerous people are

Re: [yocto] Autoload kernel module works only once

On Mon, 2017-03-13 at 14:36 +, Andrea Laini wrote: > Hi everybody, > > > > I’m getting some errors after building my Linux distro with the use of > KERNEL_MODULE_AUTOLOAD to allow autoloading 2 of my custom out-of-tree > device at boot time. We’ve a Poky 1.7 version. > > > > So, before

Re: [yocto] directory doesn't contain library

On Mon, 2017-03-13 at 10:32 +0100, Sven Schönfeld wrote: > Dear Yocto-Community > > > > I’m trying to create an image containing gnash_0.8.7.bb with yocto > morty (2.2.1) and bitbake 1.32.0. I added the folders to my > bblayers.conf and included the recipe for gnash in my local.conf file. > >

[yocto] directory doesn't contain library

Dear Yocto-Community I´m trying to create an image containing gnash_0.8.7.bb with yocto morty (2.2.1) and bitbake 1.32.0. I added the folders to my bblayers.conf and included the recipe for gnash in my local.conf file. In my bblayers.conf : ... BBLAYERS = " \     ...    

Re: [yocto] toaster

Hi Matthias, I am sorry I did not see your post sooner. The Toaster group generally follows the "toas...@yoctoproject.org" email list. We fully intend to support mariadb as a production level database, especially given its open source credentials, but we have not tried it yet. We understood

Re: [yocto] [Openembedded-architecture] Proposal: dealing with language-specific build tools/dependency management tools

On Fri, Mar 10, 2017 at 10:10 AM, Alexander Kanavin < alexander.kana...@linux.intel.com> wrote: > On 03/10/2017 04:58 PM, Otavio Salvador wrote: > >> I'd like to avoid generating entire separate recipes though, because that >>> implies your custom-written tool would be figuring out where the >>>

Re: [yocto] [Openembedded-architecture] Proposal: dealing with language-specific build tools/dependency management tools

On Fri, Mar 10, 2017 at 10:10 AM, Alexander Kanavin < alexander.kana...@linux.intel.com> wrote: > On 03/10/2017 04:58 PM, Otavio Salvador wrote: > >> I'd like to avoid generating entire separate recipes though, because that >>> implies your custom-written tool would be figuring out where the >>>

[yocto] heterogeneous processor

Hello all, I have some curious question on how to use heterogeneous processor when you have multi-core heterogeneous processor, How you do Yocto build for particular architecture ARM architecture? Actually how you distinguish what architecture you are build for? Thanks. Regards, Peter

[yocto] Procedure to build the xfce UI for ODROID XU3 board

I am able to build the bootloaders, linux kernel (zImage), modules and rootfs images for ODROID XU3 board using Yocto-poky. What is the procedure to build the xfce UI for ODROID XU3 board. -- ___ yocto mailing list yocto@yoctoproject.org

[yocto] GUI supported by Yocto project

what are all different GUI supported by the Yocto project ? -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] missing "whoami" command trying to build FIT image for mpc8315e-rdb ref board

On 2017-03-13 12:50, Robert P. J. Day wrote: trying for the first time to build a FIT image, so started with current poky checkout, configured and built for mpc8315e-rdb and core-image-minimal, everything worked fine (as it always does). now, as i read it, to generate a FIT image output

[yocto] missing "whoami" command trying to build FIT image for mpc8315e-rdb ref board

trying for the first time to build a FIT image, so started with current poky checkout, configured and built for mpc8315e-rdb and core-image-minimal, everything worked fine (as it always does). now, as i read it, to generate a FIT image output file, i need add only:

Re: [yocto] Yocto Jetro / ls1046 : SDK with toolchains for both 32 and 64 bits

Hi ARVIS. I have used the remotes/origin/Jethro branch to produce Arm SDK and test it. I didn’t meet the same problem with you, here is my stdout log: $ . /opt/poky/2.0.3/environment-setup-armv7a-vfp-neon-pokymllib32-linux-gnueabi $ $CC -bash: arm-pokymllib32-linux-gnueabi-gcc: command not found

Re: [yocto] [Openembedded-architecture] Proposal: dealing with language-specific build tools/dependency management tools

Hi Alexander, first of all thanks for the efforts. Some comments to add to the mix: 2017-03-10 16:10 GMT+01:00 Alexander Kanavin : > The lockdown files would list the versions of the dependencies (if it is > possible, which is not always true), so you can