Re: [yocto] Change in override behavior?

Hi Gary, On Fri, 29 Apr 2016 06:24:55 Gary Thomas wrote: > I used to be able to use something like this: >VARIABLE = "xyz" > and maybe in a .bbappend use >VARIABLE_mymachine = "xyzzy" > where 'mymachine' is in OVERRIDES, which resulted in >VARIABLE = "xyzzy" > > This doesn't seem to

[yocto] Change in override behavior?

I used to be able to use something like this: VARIABLE = "xyz" and maybe in a .bbappend use VARIABLE_mymachine = "xyzzy" where 'mymachine' is in OVERRIDES, which resulted in VARIABLE = "xyzzy" This doesn't seem to work the same today, what I get is VARIABLE = "xyz" VARIABLE_mymachine =

Re: [yocto] Error while buildng SGX

Hi all, Can you please help me to fix the issue Thanks and Regards, Harinath From: Harinath maddelal Sent: Thursday, April 28, 2016 7:04:29 PM To: yocto@yoctoproject.org Subject: Error while buildng SGX Hi all, When i build sgx using yocto, im getting

[yocto] [meta-raspberrypi][PATCH] sdcard_image-rpi.bbclass: Fix do_image_rpi_sdimg tashhash mismatch

IMAGE_CMD_rpi-sdimg() uses the IMAGEDATESTAMP variable, so the taskhash of the function keeps changing. This results in a taskhash mismatch error. Fix this by excluding the IMAGEDATESTAMP variable from the checksum. Change-Id: Ie6f30ad29e279d5312ec655ac4a3bf246c8a04de Signed-off-by: Jonathan Liu

Re: [linux-yocto] [yocto-kernel-cache][PATCH 0/6] Enable kernel configuration for Skylake

An overarching problem with this patch series is that the commit format isn't correct. The general commit format is: area/modified: What the commit does Explanation of why this commit is needed/wanted. Signed-off-by: Your Name One-line commit messages should be avoided, and

Re: [linux-yocto] [yocto-kernel-cache][PATCH 4/6] intel-common-drivers: enable EG20T platform controller hub

Minor nitpick: Including this in intel-common-drivers.scc means it will be included in both 32 and 64 bit BSPs, meaning we no longer need it in intel-common-drivers-32.scc. --- Cal On 04/27/2016 09:24 PM, chun.weng@intel.com wrote: > From: Ong Chun Weng > > --- >

Re: [linux-yocto] [yocto-kernel-cache][PATCH 1/6] features: soc: enable configurations for skylake

What is the rational for CONFIG_DRM_LOAD_EDID_FIRMWARE=y? From my understanding it is to manually load monitor information for monitors that don't provide it itself. If my understanding is correct this option shouldn't be necessary for general Skylake enabling. --- Cal On 04/27/2016 09:24 PM,

Re: [linux-yocto] [yocto-kernel-cache][PATCH 3/6] intel-common: add support for more driver features for 32-bit system

I don't think this patch is necessary, as other than sound these options are all in intel-common-drivers.scc. intel-common-drivers-32.scc should be limited to 32-bit specific features. --- Cal On 04/27/2016 09:24 PM, chun.weng@intel.com wrote: > From: Ong Chun Weng

Re: [yocto] [OE-core] [RFT] GCC 6 Recipes

On Thu, Apr 28, 2016 at 07:01:34AM -0700, Khem Raj wrote: > On Thu, Apr 28, 2016 at 5:14 AM, Tom Rini wrote: > > On Thu, Apr 28, 2016 at 12:08:46AM -0700, Khem Raj wrote: > >> > >> > On Apr 27, 2016, at 3:10 PM, Tom Rini wrote: > >> > > >> > On Wed, Apr

Re: [yocto] Antwort: Re: how to configure the build packages of a makefile based libary

Hi, Use INSANE_SKIP_${PN} = "installed-vs-shipped" in your recipe to avoid this error. Orelse, add FILES_${PN} += "/usr/local/" in your recipe. Thanks and Regards, Yukatharsani J. From: yocto-boun...@yoctoproject.org on

Re: [yocto] Antwort: Re: how to configure the build packages of a makefile based libary

On 28 April 2016 at 17:18, YUKATHARSANI JEYACHANDRA < yukatharsa...@tataelxsi.co.in> wrote: > Use INSANE_SKIP_${PN} = "installed-vs-shipped" in your recipe to avoid > this error. Orelse, add FILES_${PN} += "/usr/local/" in your recipe. > > No. *Only* use installed-vs-shipped if you're incapable

Re: [yocto] Antwort: Re: how to configure the build packages of a makefile based libary

I don't know why that won't work. Note, if you don't set the PREFIX, they will add /usr/local anyway. Perhaps that's the problem. Here's the relevant Makefile bits for the others to look at: # Installation related variables and target PREFIX?=/usr/local INCLUDE_PATH?=include/hiredis

Re: [yocto] how to configure the build packages of a makefile based libary

On 28 April 2016 at 17:09, wrote: > EXTRA_OEMAKE = "'CC=${CC}' 'RANLIB=${RANLIB}' 'AR=${AR}' 'CFLAGS=${CFLAGS} > -I${S}/include' 'BUILDDIR=${S}' 'DESTDIR=${D}'" > Neater to pass DESTDIR via do_install, so remove DESTDIR from here. However you want to tell it where

[yocto] Antwort: Re: how to configure the build packages of a makefile based libary

Hej sorry - that does not work. Maybe you can show me some working/common code. Do I have to create the FILE_${PV} or/and FILE_${PV}-dev, FILE_${PV}-static? The builded files go into the Git dir & the autotools-brokensep is generating the package dir. I repeat my question: What are the

Re: [yocto] how to configure the build packages of a makefile based libary

On 28 April 2016 at 16:25, Fred Ollinger wrote: > FILES_${PN} += "/usr/local" > Please don't do this unless that's actually what you want - nothing else in the image will be using those paths so eg libraries in there might not be found. Ross --

Re: [yocto] how to configure the build packages of a makefile based libary

Add to bb recipe: FILES_${PN} += "/usr/local" Section 9.2: https://www.yoctoproject.org/docs/1.8/ref-manual/ref-manual.html#qa-errors-and-warnings From: yocto-boun...@yoctoproject.org on behalf of Burton, Ross

Re: [yocto] [OE-core] [RFT] GCC 6 Recipes

> On Apr 28, 2016, at 8:19 AM, Mark Hatle wrote: > > On 4/28/16 2:10 AM, Khem Raj wrote: >> >>> On Apr 27, 2016, at 11:06 AM, Mark Hatle wrote: >>> >>> On 4/27/16 12:53 PM, Khem Raj wrote: thanks I think most of them come to these

Re: [yocto] [OE-core] [RFT] GCC 6 Recipes

On 4/28/16 2:10 AM, Khem Raj wrote: > >> On Apr 27, 2016, at 11:06 AM, Mark Hatle wrote: >> >> On 4/27/16 12:53 PM, Khem Raj wrote: >>> thanks I think most of them come to these categories. So any help in >>> fixing them is welcome. >>> >>> 1. kernel older than 4.4,

Re: [yocto] [OE-core] [RFT] GCC 6 Recipes

On Thu, Apr 28, 2016 at 5:14 AM, Tom Rini wrote: > On Thu, Apr 28, 2016 at 12:08:46AM -0700, Khem Raj wrote: >> >> > On Apr 27, 2016, at 3:10 PM, Tom Rini wrote: >> > >> > On Wed, Apr 27, 2016 at 10:53:52AM -0700, Khem Raj wrote: >> >> thanks I think most

Re: [yocto] Building with ltdl

Did you guys get any further with this? I am running into the same issue and would love to be able to use the graphviz recipe. Cheers, Dave. -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto

[yocto] Error while buildng SGX

Hi all, When i build sgx using yocto, im getting following errors. The same builds fine when i use my local gcc of version 4.8.3. I have used 1.8.1 Yocto its using 4.9.2 gcc. Can you please help me resolve the issue. Thanks in advance Following is the console build error log

[yocto] [matchbox-desktop-2][PATCH 16/16] Don't set the desktop fullscreen if MODE_DESKTOP

WM paints fullscreen windows over the panel: don't make the desktop fullscreen. Signed-off-by: Jussi Kukkonen --- src/desktop.c | 1 - 1 file changed, 1 deletion(-) diff --git a/src/desktop.c b/src/desktop.c index ddb2786..8234e8c 100644 --- a/src/desktop.c +++

[yocto] [matchbox-desktop-2][PATCH 14/16] build: update git.mk

From: Ross Burton --- Makefile.am | 10 ++ git.mk | 115 +++- 2 files changed, 93 insertions(+), 32 deletions(-) diff --git a/Makefile.am b/Makefile.am index 9f1df6e..6a2cec9 100644 --- a/Makefile.am +++

[yocto] [matchbox-desktop-2][PATCH 15/16] Use a GtkFlowBox instead of TakuTable

Remove ~500 lines of code by using FlowBox instead of custom code Also avoid using GtkFixed when in desktop mode Signed-off-by: Jussi Kukkonen --- libtaku/Makefile.am | 1 - libtaku/taku-launcher-tile.c | 8 +- libtaku/taku-launcher-tile.h | 2 +

[yocto] [matchbox-desktop-2][PATCH 10/16] main: ignore file not found errors when loading CSS

From: Ross Burton --- src/main.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/main.c b/src/main.c index 7b8a276..261198e 100644 --- a/src/main.c +++ b/src/main.c @@ -63,7 +63,7 @@ load_style (GtkWidget *widget) provider = gtk_css_provider_new

[yocto] [matchbox-desktop-2][PATCH 11/16] desktop: add --mode

From: Ross Burton The --mode argument takes "desktop" (be a normal desktop), "titlebar" (normal desktop but don't hide titlebar, YMMV depending on WM) or "window" (for testing). This replaces the --enable-standalone configure option. --- src/desktop.c | 59

[yocto] [matchbox-desktop-2][PATCH 12/16] build: remove unused --enable-standalone option

From: Ross Burton --- configure.ac | 7 --- 1 file changed, 7 deletions(-) diff --git a/configure.ac b/configure.ac index afa64ae..774a4ac 100644 --- a/configure.ac +++ b/configure.ac @@ -30,13 +30,6 @@ if test x$enable_startup_notification != xno; then

[yocto] [matchbox-desktop-2][PATCH 08/16] taku-table: port to GtkGrid

From: Ross Burton --- libtaku/taku-table.c | 44 libtaku/taku-table.h | 7 +++ 2 files changed, 23 insertions(+), 28 deletions(-) diff --git a/libtaku/taku-table.c b/libtaku/taku-table.c index 67f630e..058700e 100644 ---

[yocto] [matchbox-desktop-2][PATCH 09/16] More fixes

From: Ross Burton --- libtaku/taku-table.c | 34 -- libtaku/taku-tile.c | 2 ++ libtaku/xutil.c | 3 +-- libtaku/xutil.h | 2 +- src/desktop.c| 17 ++--- 5 files changed, 26 insertions(+), 32 deletions(-)

[yocto] [matchbox-desktop-2][PATCH 06/16] desktop: set as unresizable to hide resize grip

From: Ross Burton --- src/desktop.c | 1 + 1 file changed, 1 insertion(+) diff --git a/src/desktop.c b/src/desktop.c index 22beeab..fbecd20 100644 --- a/src/desktop.c +++ b/src/desktop.c @@ -160,6 +160,7 @@ create_desktop (void) g_signal_connect (window,

[yocto] [matchbox-desktop-2][PATCH 07/16] fixup initial port

From: Ross Burton --- src/desktop.c | 8 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/src/desktop.c b/src/desktop.c index fbecd20..b7858b7 100644 --- a/src/desktop.c +++ b/src/desktop.c @@ -47,9 +47,9 @@ on_item_added (TakuMenu *menu,

[yocto] [matchbox-desktop-2][PATCH 05/16] taku-category-bar: don't try to make the arrows square

From: Ross Burton --- src/taku-category-bar.c | 11 --- 1 file changed, 11 deletions(-) diff --git a/src/taku-category-bar.c b/src/taku-category-bar.c index 765c713..e5c5533 100644 --- a/src/taku-category-bar.c +++ b/src/taku-category-bar.c @@ -66,15 +66,6 @@

[yocto] [matchbox-desktop-2][PATCH 04/16] main: load a custom CSS stylesheet if present

From: Ross Burton --- src/Makefile.am | 7 ++- src/main.c | 31 ++- 2 files changed, 32 insertions(+), 6 deletions(-) diff --git a/src/Makefile.am b/src/Makefile.am index e8fa7e2..5f5e961 100644 --- a/src/Makefile.am +++

[yocto] [matchbox-desktop-2][PATCH 03/16] fixup 1024d115181a182918197d280e0797566178d26f

From: Ross Burton --- libtaku/taku-launcher-tile.c | 4 ++-- libtaku/taku-tile.c | 2 ++ 2 files changed, 4 insertions(+), 2 deletions(-) diff --git a/libtaku/taku-launcher-tile.c b/libtaku/taku-launcher-tile.c index 56151b2..58deafb 100644 ---

[yocto] [matchbox-desktop-2][PATCH 01/16] Initial port to GTK+ 3

From: Ross Burton More to be done, but it works. The only known regression is that startup notification isn't multi-screen aware, but this should be ported to use GAppInfo in the future. Also themeing is likely to be broken, but this needs to be rethought for GTK+ 3

[yocto] [matchbox-desktop-2][PATCH 00/16] Upgrade to GTK+3

This branch was started 4(!) years ago to update matchbox-desktop to GTK+3, most of it is Ross' handiwork. For my part, the TakuTable removal started because it had some small but annoying layout bugs and FlowBox seems to do everything we need without those problems (and with less code). Code

[yocto] [matchbox-sato][PATCH 2/2] Remove the qvga theme

Not maintaining a 320px theme in 2016... Signed-off-by: Jussi Kukkonen --- Sato/matchbox/Makefile.am | 17 - Sato/matchbox/arrow-down-active-qvga.png | Bin 333 -> 0 bytes Sato/matchbox/arrow-down-qvga.png | Bin 332 -> 0 bytes

[yocto] [matchbox-sato][PATCH 1/2] Make titlebar more like default GTK3

Includes titlebar layout, close and arrow buttons. Removes gradient, rounded corners and the bold green: The theme is now plain boring gray. Button active states are currently same as inactive. The new icons are modified from adwaita-icon-theme which is CC-BY-SA 3.0 (or LGPL 3+). ---

[yocto] [matchbox-sato][PATCH 0/2] Matchbox theme update

Update the matchbox window manager theme to be more compatible with current GTK default themes. The theme is now gray and boring but hopefully does not clash with everything else as badly. The titlebar is much thinner in preparation for the separation of panel and titlebar: With client side

Re: [yocto] how to configure the build packages of a makefile based libary

On 28 April 2016 at 13:09, wrote: > ERROR: QA Issue: libhiredis: Files/directories were installed but not > shipped in any package: > /usr/local > It either hard-codes /usr/local as the prefix, or if it respects a prefix variable you should also pass in ${prefix}

Re: [yocto] what's the "standard" for adding .dts patches to a BSP layer?

On 2016-04-28 14:14, Robert P. J. Day wrote: looking for common practice here ... what's the canonical way that one should add content to a .dts file for a new board -- all at once, or broken into patches associated with corresponding .scc files that come into play only if one selects that

Re: [yocto] [Yocto] Enable a recipe/package only when other dependent recipe/package is part of image.

Hi Ross, An alternative would be to have some naming pattern for conf packages (-conf is reasonable) and invent a new image-feature called conf-packages that uses a glob to find all complementary packages matching the *-conf pattern. This is how dev-pkgs, dbg-pkgs, doc-pkgs etc work. I

[yocto] what's the "standard" for adding .dts patches to a BSP layer?

looking for common practice here ... what's the canonical way that one should add content to a .dts file for a new board -- all at once, or broken into patches associated with corresponding .scc files that come into play only if one selects that functionality? i ask since i'm a big fan of

Re: [yocto] how to configure the build packages of a makefile based libary

Hej The makefile has an install section. I relocated it with the ${D}. By doing that I managed that the compiler filled the "package" directory. But there is still a packing issue. Below is the log (and below of it is the libhiredis.bb). Now my question: How to define the FILES variable for a

Re: [yocto] how to configure the build packages of a makefile based libary

On 28 April 2016 at 10:50, wrote: > I like to include the hiredis library. I created a recipe and modified the > EXTRA_OEMAKE. The compilation works (in the git directory object, "so" and > "a" files are generated). But the generated files are not placed into > packages.

Re: [yocto] how to configure the build packages of a makefile based libary

If bins/libs are installed in non standard paths other than usr/bin or /usr/lib in image directory, then you need to add them explicitly in your recipe like FILES_${PN} += "/lib/lib.so" On Thu, Apr 28, 2016 at 3:20 PM, wrote: > Hej > > I like to include the hiredis

[yocto] how to configure the build packages of a makefile based libary

Hej I like to include the hiredis library. I created a recipe and modified the EXTRA_OEMAKE. The compilation works (in the git directory object, "so" and "a" files are generated). But the generated files are not placed into packages. Any ideas? below there is the "libhiredis.bb" file:

[linux-yocto] [PATCH 3/4] Revert "spi: modify spidev_test to test automatic PIO/DMA switching"

From: "Chai, Chong Yi" This reverts commit c4554857d23b4370e4f2051ed05758badc48227b. Signed-off-by: Chai, Chong Yi --- Documentation/spi/spidev_test.c | 21 + 1 file changed, 1 insertion(+), 20 deletions(-) diff --git

[linux-yocto] [PATCH 4/4] Revert "spi/pxa2xx: auto switch between PIO and DMA with configurable threshold size"

From: "Chai, Chong Yi" This reverts commit afe9c4b82e119cd9e8e69ef2dbae1191375bfb51. Signed-off-by: Chai, Chong Yi --- drivers/spi/spi-pxa2xx.c| 17 ++--- drivers/spi/spidev.c| 2 -- include/linux/spi/spi.h

[linux-yocto] [PATCH 1/4] Revert "spi: modify spidev_test to test modifying FIFO trigger level during runtime"

From: "Chai, Chong Yi" This reverts commit 950a0f480664e4a8c9aa9567cd547f6e6f9e9cad. Signed-off-by: Chai, Chong Yi --- Documentation/spi/spidev_test.c | 55 ++--- 1 file changed, 2 insertions(+), 53

[linux-yocto] [PATCH 2/4] Revert "spi/pxa2xx: Add new ioctl for configuring FIFO trigger level in runtime"

From: "Chai, Chong Yi" This reverts commit db6b51575bde505ac64ae23a1be6b008ba897fc0. Signed-off-by: Chai, Chong Yi --- drivers/spi/spi-pxa2xx.c| 13 - drivers/spi/spidev.c| 17 -

[linux-yocto] [PATCH 0/4] Revert SPI patches

From: "Chai, Chong Yi" Hi Bruce, When userspace program try to initialize full duplex SPI transaction through ioctl system call to SPIDEV driver, SPIDEV driver return "invalid argument" to userspace program. There are 4 patches modify the size of the structure used

Re: [yocto] [OE-core] [RFT] GCC 6 Recipes

> On Apr 27, 2016, at 11:06 AM, Mark Hatle wrote: > > On 4/27/16 12:53 PM, Khem Raj wrote: >> thanks I think most of them come to these categories. So any help in >> fixing them is welcome. >> >> 1. kernel older than 4.4, backport needed fixed into these branches or

Re: [yocto] [OE-core] [RFT] GCC 6 Recipes

> On Apr 27, 2016, at 3:10 PM, Tom Rini wrote: > > On Wed, Apr 27, 2016 at 10:53:52AM -0700, Khem Raj wrote: >> thanks I think most of them come to these categories. So any help in >> fixing them is welcome. >> >> 1. kernel older than 4.4, backport needed fixed into these