thank you for checking :-) that suggests a missing #include <GL/gl.h>

The original error: ../libepoxy-1.4.3/test/egl_common.c:36:20: error: implicit declaration of function 'XOpenDisplay'; did you mean 'eglGetDisplay'? [-Werror=implicit-function-declaration] Display *dp

Brilliant! Why isn't this the default?

You're missing a colon at the end of the path definition, and you should use the ':=' operator: FILESEXTRAPATHS_prepend := "$(THISDIR)/files:" The path you're introducing is getting added to a bunch o

Don't forget https://github.com/jackmitch/meta-tinker ;-) Romain started meta-rockchip initially, then I joined, then people from Rockchip joined later. The main goal Romain and I have is to have a me

<otavio.salvador@...> wrote: I've been trying (begging) since the start of August to get the above one added to OE-core https://bugzilla.yoctoproject.org/show_bug.cgi?id=11881

Along with the log files, in the "temp" directory of each recipe's work dir (e.g. tmp-glibc/work/cortex7hf-neon-vfpv4-oe-linux-gnueabi/i2c-tools/3.1.2-r0/temp) are "run" scripts (i.e. run.do_compile)

Hi, I'm trying to understand if memres is right for me. Every night my machine, via jenkins, grinds away doing about a dozen builds. Each of these builds is for a separate MACHINE, in separate directo

Thanks! :-D

Hey Tom, Excellent question! I was just thinking the same thing myself as I was preparing this patch :-) This patch is a maintenance patch that will allow builds to succeed, but I admit it isn't ideal

The oe-core recipe was updated (2017.05 -> 2017.07), this recipe needed to be updated to suit. However, this u-boot (from rockchip) is still at version 2017.05. Signed-off-by: Trevor Woerner <twoerner

Bump mainline kernel to latest release. Signed-off-by: Trevor Woerner <twoerner@...> --- recipes-kernel/linux/{linux_4.11.bb => linux_4.12.bb} | 4 ++-- 1 file changed, 2 insertions(+), 2 deletio

The older "IMAGE_DEPENDS..." notation has been deprecated in favour of the newer "do_image_...[depends]" notation. Signed-off-by: Trevor Woerner <twoerner@...> --- classes/rockchip-gpt-img.bbcla

In other words it's being pushed back a week for the US holiday?

Andrei, Will you need Drew to submit this as a pull request via github? Best regards, Trevor

Looks and works great! Thanks for investigating and getting this working :-) Tested-by: Trevor Woerner <twoerner@...>

That's all fine. As the maintainer (thank you!) you're welcome to use whatever workflow with which you're the happiest... as long as you update the "Contributing" section of the README :-)

<pderocco@...> wrote: I posted a v1, which worked great, and continues to work great. After posting the v1, lots of feedback was given. One of those pieces of feedback was that I shouldn't i

I'm investigating moving chromium to a newer version, specifically something much closer to the current Linux stable (59.0.3071.109). My understanding is the chromium developers use clang, which would

I want to have one recipe build with clang instead of gcc (gcc is being used for the rest of the image). I thought this was as simple as adding the following line to the recipe: TOOLCHAIN = "clang" Ad