Hi,
i have created an image for genericx86 from the krogoth branch and would
like to integrate a build appliance. I used build-appliance-image.bb as
a template.
However, there is still something missing. When I run bitbake, i’m
getting a loop.
After aborting by [strg + c] I get this outp
Hi all,
I'm trying to a build a core-image-minimal for my RaspberryPi3 with Qt5 support.
I'm working with Poky Krogth and master branches of meta-qt5 and
meta-raspberrypi.
The build failed at qtbase do_configure().
It reports
"| checking for OpenGL...
| Cannot read
/home/kai/yocto/build-
I wrote a mistake in my first post.
I meant:
In the mesa-gl work dir, I can find:
./tmp/work/xxx/mesa-gl-xxx/usr/include/GL/
./tmp/work/xxx/mesa-gl-xxx/usr/include/GL/GL
./tmp/work/xxx/mesa-gl-xxx/usr/include/GL/GLES
./tmp/work/xxx/mesa-gl-xxx/usr/include/GL/GLES2
./tmp/work/xxx/mesa-gl-xxx/us
On Sun, Oct 16, 2016 at 8:45 AM, Karim ATIKI wrote:
> Hi all,
>
>
> I'm trying to a build a core-image-minimal for my RaspberryPi3 with Qt5
> support.
>
> I'm working with Poky Krogth and master branches of meta-qt5 and
> meta-raspberrypi.
>
>
> The build failed at qtbase do_configure().
>
> It r
Hi Khem,
>it currently have some vc4 support if you want mesa to work then use
>vc4graphics in machine features.
You mean, I should add "vc4graphics" in MACHINE_FEATURES ?
Actually, I don't specially want to have mesa. I just want to have Qt5 without
X11 so I can build my programs with eglfs
you can use bitbake -g to dump the dep graphs in dotty format and
explore the depchains
> On Oct 16, 2016, at 11:15 AM, Karim ATIKI wrote:
>
> Hi Khem,
>
> >it currently have some vc4 support if you want mesa to work then use
> >vc4graphics in machine features.
> You mean, I should add "vc4gr
> On Oct 12, 2016, at 11:13 PM, Peter Balazovic
> wrote:
>
> Hello Jason,
>
> I'm interested in your code + BitBake recipe to be able to automatically
> resize on first boot.
Take a look at 96boards layer there is a recipe as well as systemd service file
that will be packaged into image
ht
> On Oct 11, 2016, at 4:53 PM, Stroz, Glenn wrote:
>
> Hi,
>
> We have a project running an aarch64 compatible processor. For backward
> compatibility with some internal software packages, we’re using the
> armv7a-vfp machine type as a multilib lib32 variant. However, we have found
> that wh
The license for brcm43430-license should be the license it contains
instead of all the licenses of the linux-firmware packages.
[YOCTO #10251]
Signed-off-by: Jonathan Liu
---
recipes-kernel/linux-firmware/linux-firmware_git.bbappend | 1 +
1 file changed, 1 insertion(+)
diff --git a/recipes-ke
On Sun, Oct 16, 2016 at 1:48 PM, Harshal Govind (hgovind)
wrote:
> Thanks Raj!
>
> I was pulling yocto 1.7.2 and did not add any custom recipe or target. I just
> build core-image-minimal image with enabling uclibc in
> "meta/conf/distro/defaultsetup.conf" (#TCLIBC ?= "uclibc")
>
> But if I do s
On Sun, Oct 16, 2016 at 3:08 PM, Jonathan Liu wrote:
> The license for brcm43430-license should be the license it contains
> instead of all the licenses of the linux-firmware packages.
>
this is ok
> [YOCTO #10251]
>
> Signed-off-by: Jonathan Liu
> ---
> recipes-kernel/linux-firmware/linux-fir
This mail was sent out by Recipe reporting system.
This message list those recipes which need to be upgraded. If maintainers
believe some of them needn't to upgrade at this time, they can fill
RECIPE_NO_UPDATE_REASON in respective recipe file to ignore this remainder
until newer upstream version w
Hi,
I found that before yocto-1.6, source archives were deployed by license.
The following commit changed the directory for deploying source archives:
cbcf5b219858b58c4429ee87444eaacc5a7cfa3e
But from commit log, there is no explaining about this change.
Are there someone who can tell me why.
13 matches
Mail list logo
