Re: [yocto] How do you build 2 versions of the same recipe and a specific version from bitbake cmd line

[Robert Joslyn]

On Fri, 2017-07-14 at 19:49 +0100, Burton, Ross wrote:
> 
> On 14 July 2017 at 18:17, Jimi Damon  wrote:
> > Do to a fun "feature" of zeromq, the newest libraries are not
> > backward compatible and hence I need to install a zeromq-4.1.5 and
> > zeromq-3.2.2 libraries onto my target to assist with one
> > application using the old version and a newer application using the
> > newer one. 
> > 
> > How can I do this from the local.conf file AND how can I specify a
> > single recipe version to build on the command line ? 
> > 
> 
> You need two recipes *with different names*, and they must not
> conflict in any way with each other.
> 
> Ross

Just to clarify, the typical way this is done is to put the major
version number as part of the package name. For example, the recipes
could be called zeromq3_3.2.2.bb and zeromq4_4.1.5.bb. This assumes
zeromq can tolerate having multiple versions installed at the same
time.

Robert
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [linux-yocto] [kernel-cache][RFC PATCH 5/7] bsp/qemumicroblazeeb: Add BSP configs for qemumicroblazeeb

[Bruce Ashfield]

On 2017-07-13 1:56 PM, Nathan Rossi wrote:

On 13 July 2017 at 05:22, Bruce Ashfield  wrote:

On 2017-07-04 11:29 AM, Nathan Rossi wrote:


Create configs for the qemumicroblazeeb machine. This includes both
-standard and -tiny configs.

Signed-off-by: Nathan Rossi 
---
   bsp/qemumicroblaze/qemumicroblazeeb-standard.scc | 15 +++
   bsp/qemumicroblaze/qemumicroblazeeb-tiny.scc | 12 
   bsp/qemumicroblaze/qemumicroblazeeb.cfg  | 15 +++
   3 files changed, 42 insertions(+)
   create mode 100644 bsp/qemumicroblaze/qemumicroblazeeb-standard.scc
   create mode 100644 bsp/qemumicroblaze/qemumicroblazeeb-tiny.scc
   create mode 100644 bsp/qemumicroblaze/qemumicroblazeeb.cfg

diff --git a/bsp/qemumicroblaze/qemumicroblazeeb-standard.scc
b/bsp/qemumicroblaze/qemumicroblazeeb-standard.scc
new file mode 100644
index 00..ae93b49a11
--- /dev/null
+++ b/bsp/qemumicroblaze/qemumicroblazeeb-standard.scc
@@ -0,0 +1,15 @@
+define KMACHINE qemumicroblazeeb
+define KTYPE standard
+define KARCH microblaze
+
+include ktypes/standard/standard.scc
+
+include arch/microblaze/microblaze.scc
+kconf hardware qemumicroblazeeb.cfg
+
+include bsp/xilinx/soc/drivers-softip.scc
+include bsp/xilinx/board-common.scc
+
+# default policy for standard kernels
+include features/latencytop/latencytop.scc
+include features/profiling/profiling.scc
diff --git a/bsp/qemumicroblaze/qemumicroblazeeb-tiny.scc
b/bsp/qemumicroblaze/qemumicroblazeeb-tiny.scc
new file mode 100644
index 00..2d1bb74132
--- /dev/null
+++ b/bsp/qemumicroblaze/qemumicroblazeeb-tiny.scc
@@ -0,0 +1,12 @@
+define KMACHINE qemumicroblazeeb
+define KTYPE tiny
+define KARCH microblaze
+
+include ktypes/tiny/tiny.scc
+
+include arch/microblaze/microblaze.scc
+kconf hardware qemumicroblazeeb.cfg
+
+include bsp/xilinx/soc/drivers-softip.scc
+include bsp/xilinx/board-common.scc
+
diff --git a/bsp/qemumicroblaze/qemumicroblazeeb.cfg
b/bsp/qemumicroblaze/qemumicroblazeeb.cfg
new file mode 100644
index 00..0f635c1652
--- /dev/null
+++ b/bsp/qemumicroblaze/qemumicroblazeeb.cfg
@@ -0,0 +1,15 @@
+
+CONFIG_XILINX_MICROBLAZE0_FAMILY="spartan3"



Out curiosity, is it this config that actually dictates
the endianess ?


This config just populates the fpga family. It does control some
instruction flags for very old microblaze cpu versions [0]. But
otherwise just embeds a string that can be read at run time.



I ask, because I didn't see anything else obvious that would
trigger this to build BE.


There is no kernel config to switch endianess, it is defined by the
toolchain used. You can see how the arch picks based on compiler
defines e.g. [1], [2].


Aha. So the naming convention of 'eb' isn't significant from the
point of view of endianess.

If so, what is the delta between the kernel configs of the el and
eb machine ?

Bruce



The compiler defines are gcc specific [3].

[0] - 
http://elixir.free-electrons.com/linux/latest/source/arch/microblaze/Makefile#L26
[1] - 
http://elixir.free-electrons.com/linux/latest/source/arch/microblaze/include/uapi/asm/byteorder.h#L4
[2] - 
http://elixir.free-electrons.com/linux/latest/source/arch/microblaze/lib/libgcc.h#L17
[3] - 
https://github.com/gcc-mirror/gcc/blob/master/gcc/config/microblaze/microblaze-c.c#L45

Regards,
Nathan



--
___
linux-yocto mailing list
linux-yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/linux-yocto

Re: [linux-yocto] [kernel-cache][PATCH 0/8] features: Additional features and added configs to existing features

[Bruce Ashfield]

On Thu, Jul 13, 2017 at 4:34 AM, Syed Mohamad Fauzi, Syed Johan Arif <
syed.johan.arif.syed.mohamad.fa...@intel.com> wrote:

> Dear maintainer,
>
> Here are some additional features and some added configs to existing
> features.
> Please apply to 4.9 and beyond
> The additions are listed below:
>
> ADDITONAL FEATURES
>
> 1) intel-txt
> 2) IOMMU
> 3) MTD
> 4) NUMA
> 5) VFIO
>
> ADDITIONAL CONFIGURATIONS
>
> 1) features/qat
>- CONFIG_CRYPTO_RSA=y
>- CONFIG_CRYPTO_DH=y
> 2) features/netfilter
> - CONFIG_IP_NF_TARGET_ULOG=m
> - CONFIG_IP_NF_MATCH_RPFILTER=m
> - CONFIG_IP_NF_TARGET_SYNPROXY=m
> - CONFIG_IP_NF_SECURITY=m
> - CONFIG_BRIDGE_EBT_ULOG=m
>

merged.

Bruce


>
> Syed Johan Arif Bin Syed Mohamad Fauzi (7):
>   features/intel-txt: add intel-txt feature
>   features/iommu: add IOMMU feature
>   features/mtd: add MTD feature
>   features/numa: Add NUMA feature
>   features/vfio: add VFIO feature
>   features/netfilter: additional configurations
>   features/qat: additional configurations, CONFIG_CRYPTO_RSA and
> CONFIG_CRYPTO_DH
>
> Syed Mohamad Fauzi, Syed Johan Arif (1):
>   features/x2apic: add X2APIC feature
>
>  features/intel-txt/intel-txt.cfg | 1 +
>  features/intel-txt/intel-txt.scc | 3 +++
>  features/iommu/iommu.cfg | 7 +++
>  features/iommu/iommu.scc | 3 +++
>  features/mtd/mtd.cfg | 7 +++
>  features/mtd/mtd.scc | 3 +++
>  features/netfilter/netfilter.cfg | 5 +
>  features/numa/numa.cfg   | 8 
>  features/numa/numa.scc   | 3 +++
>  features/qat/qat.cfg | 2 ++
>  features/vfio/vfio.cfg   | 9 +
>  features/vfio/vfio.scc   | 3 +++
>  features/x2apic/x2apic.cfg   | 2 ++
>  features/x2apic/x2apic.scc   | 3 +++
>  14 files changed, 59 insertions(+)
>  create mode 100644 features/intel-txt/intel-txt.cfg
>  create mode 100644 features/intel-txt/intel-txt.scc
>  create mode 100644 features/iommu/iommu.cfg
>  create mode 100644 features/iommu/iommu.scc
>  create mode 100644 features/mtd/mtd.cfg
>  create mode 100644 features/mtd/mtd.scc
>  create mode 100644 features/numa/numa.cfg
>  create mode 100644 features/numa/numa.scc
>  create mode 100644 features/vfio/vfio.cfg
>  create mode 100644 features/vfio/vfio.scc
>  create mode 100644 features/x2apic/x2apic.cfg
>  create mode 100644 features/x2apic/x2apic.scc
>
> --
> 1.9.1
>
>


-- 
"Thou shalt not follow the NULL pointer, for chaos and madness await thee
at its end"
-- 
___
linux-yocto mailing list
linux-yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/linux-yocto

Re: [linux-yocto] [PATCH] common-pc-wifi: Enable SDIO for BroadCom BRCMFMAC

[Bruce Ashfield]

merged.

SRCREV updates will follow shortly.

Bruce

On 2017-07-12 11:47 PM, Saul Wold wrote:

Enable Broadcom Wifi driver for SDIO mounted hardware on Intel boards

Signed-off-by: Saul Wold 
---
Please apply to 4.9 and beyond.

  bsp/common-pc/common-pc-wifi.cfg | 3 +++
  1 file changed, 3 insertions(+)

diff --git a/bsp/common-pc/common-pc-wifi.cfg b/bsp/common-pc/common-pc-wifi.cfg
index 442aa2f..998a789 100644
--- a/bsp/common-pc/common-pc-wifi.cfg
+++ b/bsp/common-pc/common-pc-wifi.cfg
@@ -22,6 +22,9 @@ CONFIG_BRCMUTIL=m
  CONFIG_BRCMSMAC=m
  CONFIG_BRCMFMAC=m
  CONFIG_BRCMFMAC_USB=y
+CONFIG_BRCMFMAC_SDIO=y
+CONFIG_BRCMFMAC_PROTO_BCDC=y
+CONFIG_BRCMFMAC_PROTO_MSGBUF=y
  
  CONFIG_WEXT_CORE=y

  CONFIG_WEXT_PROC=y



--
___
linux-yocto mailing list
linux-yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/linux-yocto

[yocto] How do you build 2 versions of the same recipe and a specific version from bitbake cmd line

[Jimi Damon]

Hi,


Do to a fun "feature" of zeromq, the newest libraries are not backward 
compatible and hence I need to install a zeromq-4.1.5 and zeromq-3.2.2 
libraries onto my target to assist with one application using the old 
version and a newer application using the newer one.



How can I do this from the local.conf file AND how can I specify a 
single recipe version to build on the command line ?



I've tried this in my local.conf


CORE_IMAGE_EXTRA_INSTALL += "zeromq_4.1.5 zeromq_3.2.2 "


but I get errors saying :

WARNING: Host distribution "Ubuntu-16.10" has not been validated with 
this version of the build system; you may possibly experience 
unexpected failures. It is recommended that you use a tested distribution.
Loading cache: 100% 
|#| 
Time: 0:00:00

Loaded 3485 entries from dependency cache.
NOTE: Resolving any missing task queue dependencies
ERROR: Nothing RPROVIDES 'zeromq_3.2.2' (but 
/media/tools/newboot2qt_builds/sources/meta-boot2qt/recipes-qt/images/b2qt-embedded-qt5-image.bb 
RDEPENDS on or otherwise requires it)

NOTE: Runtime target 'zeromq_3.2.2' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['zeromq_3.2.2']
ERROR: Required build target 'b2qt-embedded-qt5-image' has no 
buildable providers.
Missing or unbuildable dependency chain was: 
['b2qt-embedded-qt5-image', 'zeromq_3.2.2']


Summary: There was 1 WARNING message shown.
Summary: There were 2 ERROR messages shown, returning a non-zero exit 
code. 



In addition , how can I specify a specific version of a package from the 
command line with bitbake ?



Here are my layers

% bitbake-layers show-recipes | grep -A 2 zeromq


zeromq:
  meta-oe  4.1.5
  meta-oe  3.2.2



Now this fails


bitbake zeromq-4.1.5

WARNING: Host distribution "Ubuntu-16.10" has not been validated with 
this version of the build system; you may possibly experience 
unexpected failures. It is recommended that you use a tested distribution.
Loading cache: 100% 
|#| 
Time: 0:00:00

Loaded 3485 entries from dependency cache.
ERROR: Nothing PROVIDES 'zeromq-4.1.5'

Summary: There was 1 WARNING message shown.
Summary: There was 1 ERROR message shown, returning a non-zero exit code.


or


bitbake zeromq_4.1.5

WARNING: Host distribution "Ubuntu-16.10" has not been validated with 
this version of the build system; you may possibly experience 
unexpected failures. It is recommended that you use a tested distribution.
Loading cache: 100% 
|#| 
Time: 0:00:00

Loaded 3485 entries from dependency cache.
ERROR: Nothing PROVIDES 'zeromq_4.1.5'

Summary: There was 1 WARNING message shown.
Summary: There was 1 ERROR message shown, returning a non-zero exit code.



Thanks,




-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] Kernel Build Failures with Shared SSTATE

[Schmitt, Richard]

Hi,

I had been running into kernel build failures on the morty branch when using a 
shared state.  First I'll describe the error, and then my solution.

The first build that initializes the sstate cache works fine.  Subsequent clean 
builds will fail.  The failure
would occur in the do_compile_kernelmodules task.  The error would indicate a 
failure because tmp/work-shared//kernel-build-artifacts was missing.

My analysis concluded that the kernel build was restored from the cache, but it 
did not restore the kernel-build-artifacts needed by the 
do_compile_kernelmodules task.

My solution was to include the following in a bbappend file for the kernel:

SSTATETASKS += "do_shared_workdir"

do_shared_workdir[sstate-plaindirs] = "${STAGING_KERNEL_BUILDDIR}"

python do_shared_workdir_setscene () {
sstate_setscene(d)
}

I assume the correct way to fix this would be to update the 
meta/classes/kernel.bbclass.  It looks like there was some attempt to do 
something with the shared_workdir because there is a do_shared_workdir_setscene 
routine, but right now it just returns a 1.  Is that intentional.  It seems 
wrong.

Rich
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [meta-raspberrypi][PATCH] userland: Add missing EGL_CAST defines

[Andrei Gherzan]

On Fri, Jul 14, 2017 at 2:31 PM, Khem Raj  wrote:

> On Fri, Jul 14, 2017 at 2:03 AM, Andrea Galbusera 
> wrote:
> > Needed by libepoxy
> >
> > Signed-off-by: Andrea Galbusera 
> > ---
> >  .../0015-EGL-glplatform.h-define-EGL_CAST.patch| 32
> ++
> >  recipes-graphics/userland/userland_git.bb  |  1 +
> >  2 files changed, 33 insertions(+)
> >  create mode 100644 recipes-graphics/userland/
> userland/0015-EGL-glplatform.h-define-EGL_CAST.patch
> >
> > diff --git 
> > a/recipes-graphics/userland/userland/0015-EGL-glplatform.h-define-EGL_CAST.patch
> b/recipes-graphics/userland/userland/0015-EGL-glplatform.
> h-define-EGL_CAST.patch
> > new file mode 100644
> > index 000..5a80a26
> > --- /dev/null
> > +++ b/recipes-graphics/userland/userland/0015-EGL-glplatform.
> h-define-EGL_CAST.patch
> > @@ -0,0 +1,32 @@
> > +From 382e3b16cbcc09d825540d5bd3e45a2fca4484fe Mon Sep 17 00:00:00 2001
> > +From: Andrea Galbusera 
> > +Date: Fri, 14 Jul 2017 09:52:54 +0200
> > +Subject: [PATCH] EGL/glplatform.h: define EGL_CAST
> > +
> > +C++ / C typecast macros for special EGL handle values: used by libepoxy
> code
> > +The definition comes from the updated version of this header in mesa.
> > +
> > +Upstream-Status: Pending
> > +---
> > + interface/khronos/include/EGL/eglplatform.h | 7 +++
> > + 1 file changed, 7 insertions(+)
> > +
> > +diff --git a/interface/khronos/include/EGL/eglplatform.h
> b/interface/khronos/include/EGL/eglplatform.h
> > +index 1f7c930..c39d425 100644
> > +--- a/interface/khronos/include/EGL/eglplatform.h
> >  b/interface/khronos/include/EGL/eglplatform.h
> > +@@ -202,4 +202,11 @@ EGLAPI void EGLAPIENTRY BEGL_
> GetDefaultDriverInterfaces(BEGL_DriverInterfaces *i
> > + #include "interface/khronos/common/khrn_client_mangle.h"
> > + #endif
> > +
> > ++/* C++ / C typecast macros for special EGL handle values */
> > ++#if defined(__cplusplus)
> > ++#define EGL_CAST(type, value) (static_cast(value))
> > ++#else
> > ++#define EGL_CAST(type, value) ((type) (value))
> > ++#endif
> > ++
> > + #endif /* __eglplatform_h */
> > +--
>
> LGTM
> please merge it


Your wish is my command :) Merged in master after builds passed. Thanks for
you contribution, Andrea.

Regards,
Andrei
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [meta-raspberrypi][PATCH] userland: Add missing EGL_CAST defines

[Khem Raj]

On Fri, Jul 14, 2017 at 2:03 AM, Andrea Galbusera  wrote:
> Needed by libepoxy
>
> Signed-off-by: Andrea Galbusera 
> ---
>  .../0015-EGL-glplatform.h-define-EGL_CAST.patch| 32 
> ++
>  recipes-graphics/userland/userland_git.bb  |  1 +
>  2 files changed, 33 insertions(+)
>  create mode 100644 
> recipes-graphics/userland/userland/0015-EGL-glplatform.h-define-EGL_CAST.patch
>
> diff --git 
> a/recipes-graphics/userland/userland/0015-EGL-glplatform.h-define-EGL_CAST.patch
>  
> b/recipes-graphics/userland/userland/0015-EGL-glplatform.h-define-EGL_CAST.patch
> new file mode 100644
> index 000..5a80a26
> --- /dev/null
> +++ 
> b/recipes-graphics/userland/userland/0015-EGL-glplatform.h-define-EGL_CAST.patch
> @@ -0,0 +1,32 @@
> +From 382e3b16cbcc09d825540d5bd3e45a2fca4484fe Mon Sep 17 00:00:00 2001
> +From: Andrea Galbusera 
> +Date: Fri, 14 Jul 2017 09:52:54 +0200
> +Subject: [PATCH] EGL/glplatform.h: define EGL_CAST
> +
> +C++ / C typecast macros for special EGL handle values: used by libepoxy code
> +The definition comes from the updated version of this header in mesa.
> +
> +Upstream-Status: Pending
> +---
> + interface/khronos/include/EGL/eglplatform.h | 7 +++
> + 1 file changed, 7 insertions(+)
> +
> +diff --git a/interface/khronos/include/EGL/eglplatform.h 
> b/interface/khronos/include/EGL/eglplatform.h
> +index 1f7c930..c39d425 100644
> +--- a/interface/khronos/include/EGL/eglplatform.h
>  b/interface/khronos/include/EGL/eglplatform.h
> +@@ -202,4 +202,11 @@ EGLAPI void EGLAPIENTRY 
> BEGL_GetDefaultDriverInterfaces(BEGL_DriverInterfaces *i
> + #include "interface/khronos/common/khrn_client_mangle.h"
> + #endif
> +
> ++/* C++ / C typecast macros for special EGL handle values */
> ++#if defined(__cplusplus)
> ++#define EGL_CAST(type, value) (static_cast(value))
> ++#else
> ++#define EGL_CAST(type, value) ((type) (value))
> ++#endif
> ++
> + #endif /* __eglplatform_h */
> +--

LGTM
please merge it

> +2.7.4
> +
> diff --git a/recipes-graphics/userland/userland_git.bb 
> b/recipes-graphics/userland/userland_git.bb
> index 26bbfaf..893fcba 100644
> --- a/recipes-graphics/userland/userland_git.bb
> +++ b/recipes-graphics/userland/userland_git.bb
> @@ -34,6 +34,7 @@ SRC_URI = "\
>  file://0012-implement-buffer-wrapping-interface-for-dispmanx.patch \
>  file://0013-Implement-triple-buffering-for-wayland.patch \
>  file://0014-GLES2-gl2ext.h-Define-GL_R8_EXT-and-GL_RG8_EXT.patch \
> +file://0015-EGL-glplatform.h-define-EGL_CAST.patch \
>  "
>  S = "${WORKDIR}/git"
>
> --
> 2.7.4
>
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [EXT] Re: [meta-intel] How to build module iasImage from bzImage outside yocto

[Francesco Camarda (fcamarda)]

> -Original Message-
> From: Tim Orling [mailto:timothy.t.orl...@linux.intel.com]
> Sent: Friday, July 14, 2017 8:45 AM
> To: Francesco Camarda (fcamarda) 
> Cc: yocto@yoctoproject.org; meta-in...@yoctoproject.org
> Subject: [EXT] Re: [meta-intel] How to build module iasImage from bzImage
> outside yocto
> 
> 
> > On Jul 13, 2017, at 5:59 AM, Francesco Camarda (fcamarda)
>  wrote:
> >
> > Hello,
> > Starting from a yocto build (details below):
> >
> > $ bitbake ias-kc-pf-image
> > Loading cache: 100%
> >
> |#
> ###| ETA:  00:00:00 Loaded 2536
> entries from dependency cache.
> > Parsing recipes: 100%
> >
> |#
> #| Time: 00:00:00 Parsing of 1964
> .bb files complete (1963 cached, 1 parsed). 2536 targets, 322 skipped, 2
> masked, 0 errors.
> > NOTE: Resolving any missing task queue dependencies
> >
> > Build Configuration:
> > BB_VERSION= "1.28.0"
> > BUILD_SYS = "x86_64-linux"
> > NATIVELSBSTRING   = "Ubuntu-16.04"
> > TARGET_SYS= "x86_64-poky-linux"
> > MACHINE   = "gr-mrb-64"
> > DISTRO= "poky-ivi-systemd"
> > DISTRO_VERSION= "10.0+snapshot-20170713"
> > TUNE_FEATURES = "m64 corei7"
> > TARGET_FPU= ""
> > meta
> > meta-yocto
> 
> This should be meta-poky now. How old is the metadata (version of poky /
> Yocto Project release) your distro is based on?
> 
> >
> > meta-yocto-bsp=
> "first_build:dade0e68c645473d94e1b05020b064df40677e81”
> 
> This hash shows you are using a local branch, so I can’t guess at which 
> version
> of poky you are using.
> 

The commit ID of these meta-layer repositories are:

poky/meta git://git.yoctoproject.org/poky 
dade0e68c645473d94e1b05020b064df40677e81
poky/meta-yocto git://git.yoctoproject.org/poky 
dade0e68c645473d94e1b05020b064df40677e81
poky/meta-yocto-bsp git://git.yoctoproject.org/poky 
dade0e68c645473d94e1b05020b064df40677e81
meta-intel git://git.yoctoproject.org/meta-intel 
8c15de8dbaa1414ffd0f69bea7227e7285816f85
meta-intel/meta-isg/meta-valleyisland git://git.yoctoproject.org/meta-intel 
8c15de8dbaa1414ffd0f69bea7227e7285816f85
meta-ivi/meta-ivi git://git.yoctoproject.org/meta-ivi 
e42777ef74b476ed6702b036818bcffd4fe0d768
meta-openembedded/meta-filesystems git://git.openembedded.org/meta-openembedded 
dc5634968b270dde250690609f0015f881db81f2
meta-openembedded/meta-networking git://git.openembedded.org/meta-openembedded 
dc5634968b270dde250690609f0015f881db81f2
meta-openembedded/meta-oe git://git.openembedded.org/meta-openembedded 
dc5634968b270dde250690609f0015f881db81f2
meta-openembedded/meta-python git://git.openembedded.org/meta-openembedded 
dc5634968b270dde250690609f0015f881db81f2
meta-oracle-java git://git.yoctoproject.org/meta-oracle-java 
f7c98706f80a2488ad2628e5b0c6d3f9f80c24fd
 
> > meta-ias-audio
> > meta-ias-boot
> > meta-ias-core
> > meta-ias-devtools
> > meta-ias-earlyapplication
> > meta-ias-graphics
> > meta-ias-gr-mrb-bsp
> > meta-ias-ivi-adapt
> > meta-ias-kc-reference
> > meta-ias-lifecycle
> > meta-ias-mediasdk
> > meta-ias-mediatransport
> > meta-ias-oss
> > meta-ias-security
> > meta-ias-setup
> > meta-ias-systembus
> > meta-ias-targetutilities
> > meta-ias-vehiclebus =
> "master:89811f29229764d65db9b577252e9016083b8699”
> 
> I can find no references to meta-ias on layers.openembedded.org or in a
> Google search, so no idea how to help you with respect to your “iasImage”
> question.
> 
> > meta-intel
> > meta-valleyisland =
> "first_build:8c15de8dbaa1414ffd0f69bea7227e7285816f85"
> > meta-ivi  = "first_build:e42777ef74b476ed6702b036818bcffd4fe0d768"
> > meta-filesystems
> > meta-networking
> > meta-oe
> > meta-python   =
> "first_build:dc5634968b270dde250690609f0015f881db81f2"
> > meta-oracle-java  =
> "first_build:f7c98706f80a2488ad2628e5b0c6d3f9f80c24fd"
> >
> > After building the bzImage from an external toolchain is it possible to 
> > build
> (outside yocto) the iasImage necessary to boot the Gordon peak (Intel
> Apollo lake SoC).
> >
> 
> > Also I am trying to build a sato image but:
> >
> > $ bitbake core-image-sato
> > Loading cache: 100%
> >
> |#
> ###| ETA:  00:00:00 Loaded 2536
> entries from dependency cache.
> > Parsing recipes: 100%
> >
> |#
> #| Time: 00:00:00 Parsing of 1964
> .bb files complete (1963 cached, 1 parsed). 2536 targets, 322 skipped, 2
> masked, 0 errors.
> > NOTE: Resolving any missing task queue dependencies
> > ERROR: Nothing RPROVIDES 'packagegroup-core-x11-sato-games' (but
> > /home/rah/workspace/intel_GP_APL/GR_Yocto/poky/meta/recipes-
> sato/image
> > s/core-image-sato.bb RDEPENDS on or otherwise requires it)
> > NOTE: Runtime target 

Re: [yocto] [meta-raspberrypi][PATCH] userland: Add missing EGL_CAST defines

[Andrei Gherzan]

Hello,

On Fri, Jul 14, 2017 at 10:03 AM, Andrea Galbusera  wrote:

> Needed by libepoxy
>
> Signed-off-by: Andrea Galbusera 
> ---
>  .../0015-EGL-glplatform.h-define-EGL_CAST.patch| 32
> ++
>  recipes-graphics/userland/userland_git.bb  |  1 +
>  2 files changed, 33 insertions(+)
>  create mode 100644 recipes-graphics/userland/
> userland/0015-EGL-glplatform.h-define-EGL_CAST.patch
>
> diff --git 
> a/recipes-graphics/userland/userland/0015-EGL-glplatform.h-define-EGL_CAST.patch
> b/recipes-graphics/userland/userland/0015-EGL-glplatform.
> h-define-EGL_CAST.patch
> new file mode 100644
> index 000..5a80a26
> --- /dev/null
> +++ b/recipes-graphics/userland/userland/0015-EGL-glplatform.
> h-define-EGL_CAST.patch
> @@ -0,0 +1,32 @@
> +From 382e3b16cbcc09d825540d5bd3e45a2fca4484fe Mon Sep 17 00:00:00 2001
> +From: Andrea Galbusera 
> +Date: Fri, 14 Jul 2017 09:52:54 +0200
> +Subject: [PATCH] EGL/glplatform.h: define EGL_CAST
> +
> +C++ / C typecast macros for special EGL handle values: used by libepoxy
> code
> +The definition comes from the updated version of this header in mesa.
> +
> +Upstream-Status: Pending
> +---
> + interface/khronos/include/EGL/eglplatform.h | 7 +++
> + 1 file changed, 7 insertions(+)
> +
> +diff --git a/interface/khronos/include/EGL/eglplatform.h
> b/interface/khronos/include/EGL/eglplatform.h
> +index 1f7c930..c39d425 100644
> +--- a/interface/khronos/include/EGL/eglplatform.h
>  b/interface/khronos/include/EGL/eglplatform.h
> +@@ -202,4 +202,11 @@ EGLAPI void EGLAPIENTRY BEGL_
> GetDefaultDriverInterfaces(BEGL_DriverInterfaces *i
> + #include "interface/khronos/common/khrn_client_mangle.h"
> + #endif
> +
> ++/* C++ / C typecast macros for special EGL handle values */
> ++#if defined(__cplusplus)
> ++#define EGL_CAST(type, value) (static_cast(value))
> ++#else
> ++#define EGL_CAST(type, value) ((type) (value))
> ++#endif
> ++
> + #endif /* __eglplatform_h */
> +--
> +2.7.4
> +
> diff --git a/recipes-graphics/userland/userland_git.bb
> b/recipes-graphics/userland/userland_git.bb
> index 26bbfaf..893fcba 100644
> --- a/recipes-graphics/userland/userland_git.bb
> +++ b/recipes-graphics/userland/userland_git.bb
> @@ -34,6 +34,7 @@ SRC_URI = "\
>  file://0012-implement-buffer-wrapping-interface-for-dispmanx.patch \
>  file://0013-Implement-triple-buffering-for-wayland.patch \
>  file://0014-GLES2-gl2ext.h-Define-GL_R8_EXT-and-GL_RG8_EXT.patch \
> +file://0015-EGL-glplatform.h-define-EGL_CAST.patch \
>  "
>  S = "${WORKDIR}/git"
>

Looks good to me.
--
Andrei Gherzan
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Cross compile recipe cmake

[Andrea Galbusera]

On Thu, Jul 13, 2017 at 10:48 AM, Elmar van Rijnswou <
elmarbla...@hotmail.com> wrote:

> Hello! I've been doing a lot of searching on the internet,but I can't seem
> to find anybody with my problem. I'm trying to add a recipe to my image and
> deliver it straight with the system. Everything goes fine, up until the
> recipe I created links to other libraries. I have dependencies to Qt4. I
> used the hello world example recipe, which I can bitbake successfully. My
> recipe is the following:
>
>
> SUMMARY = "Simple helloworld application"
> SECTION = "examples"
> LICENSE = "Closed"
> SRC_URI = "file://media/traffic/Yocto/src/elva/"
> S = "/media/traffic/Yocto/src/elva/proj/src"
>

it looks like you're trying to build from an "external" source tree. Yocto
does support this with a dedicated class you can inherit (externalsrc). See
[1] for the relevant doc. Maybe it can help solving the issue with cmake...

[1]
http://www.yoctoproject.org/docs/2.3/mega-manual/mega-manual.html#building-software-from-an-external-source


> inherit cmake
> EXTRA_OECMAKE = ""
>
> The problem I'm having now is that, using the generated toolchain, cmake
> is looking at the wrong directories. The rootpath is also crooked when I
> print it out in my cmake project file:
>
> CMAKE_FIND_ROOT_PATH:/media/traffic/Yocto/QorIQ-SDK-V2.0-
> 20160527-yocto/build_ls2080abluebox/tmp/sysroots/ls2080abluebox
> /media/traffic/Yocto/QorIQ-SDK-V2.0-20160527-yocto/build_ls2080abluebox/
> tmp/sysroots/x86_64-linux
>
>
> What am I doing wrong? My target is arm. I can build my image fine without
> the recipe, so I'm thinking that there is a step I'm missing. Also when I
> export the SDK I can see that all the right libraries and findscripts are
> available (in the sysroot). But whenever I change my source, it still looks
> in the sysroot of the host system. Any help would be greatly appreciated!
>
> --
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>
>
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] [meta-raspberrypi][PATCH] userland: Add missing EGL_CAST defines

[Andrea Galbusera]

Needed by libepoxy

Signed-off-by: Andrea Galbusera 
---
 .../0015-EGL-glplatform.h-define-EGL_CAST.patch| 32 ++
 recipes-graphics/userland/userland_git.bb  |  1 +
 2 files changed, 33 insertions(+)
 create mode 100644 
recipes-graphics/userland/userland/0015-EGL-glplatform.h-define-EGL_CAST.patch

diff --git 
a/recipes-graphics/userland/userland/0015-EGL-glplatform.h-define-EGL_CAST.patch
 
b/recipes-graphics/userland/userland/0015-EGL-glplatform.h-define-EGL_CAST.patch
new file mode 100644
index 000..5a80a26
--- /dev/null
+++ 
b/recipes-graphics/userland/userland/0015-EGL-glplatform.h-define-EGL_CAST.patch
@@ -0,0 +1,32 @@
+From 382e3b16cbcc09d825540d5bd3e45a2fca4484fe Mon Sep 17 00:00:00 2001
+From: Andrea Galbusera 
+Date: Fri, 14 Jul 2017 09:52:54 +0200
+Subject: [PATCH] EGL/glplatform.h: define EGL_CAST
+
+C++ / C typecast macros for special EGL handle values: used by libepoxy code
+The definition comes from the updated version of this header in mesa.
+
+Upstream-Status: Pending
+---
+ interface/khronos/include/EGL/eglplatform.h | 7 +++
+ 1 file changed, 7 insertions(+)
+
+diff --git a/interface/khronos/include/EGL/eglplatform.h 
b/interface/khronos/include/EGL/eglplatform.h
+index 1f7c930..c39d425 100644
+--- a/interface/khronos/include/EGL/eglplatform.h
 b/interface/khronos/include/EGL/eglplatform.h
+@@ -202,4 +202,11 @@ EGLAPI void EGLAPIENTRY 
BEGL_GetDefaultDriverInterfaces(BEGL_DriverInterfaces *i
+ #include "interface/khronos/common/khrn_client_mangle.h"
+ #endif
+ 
++/* C++ / C typecast macros for special EGL handle values */
++#if defined(__cplusplus)
++#define EGL_CAST(type, value) (static_cast(value))
++#else
++#define EGL_CAST(type, value) ((type) (value))
++#endif
++
+ #endif /* __eglplatform_h */
+-- 
+2.7.4
+
diff --git a/recipes-graphics/userland/userland_git.bb 
b/recipes-graphics/userland/userland_git.bb
index 26bbfaf..893fcba 100644
--- a/recipes-graphics/userland/userland_git.bb
+++ b/recipes-graphics/userland/userland_git.bb
@@ -34,6 +34,7 @@ SRC_URI = "\
 file://0012-implement-buffer-wrapping-interface-for-dispmanx.patch \
 file://0013-Implement-triple-buffering-for-wayland.patch \
 file://0014-GLES2-gl2ext.h-Define-GL_R8_EXT-and-GL_RG8_EXT.patch \
+file://0015-EGL-glplatform.h-define-EGL_CAST.patch \
 "
 S = "${WORKDIR}/git"
 
-- 
2.7.4

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [meta-intel] How to build module iasImage from bzImage outside yocto

[Tim Orling]

> On Jul 13, 2017, at 5:59 AM, Francesco Camarda (fcamarda) 
>  wrote:
> 
> Hello,
> Starting from a yocto build (details below):
>  
> $ bitbake ias-kc-pf-image
> Loading cache: 100% 
> ||
>  ETA:  00:00:00
> Loaded 2536 entries from dependency cache.
> Parsing recipes: 100% 
> |##|
>  Time: 00:00:00
> Parsing of 1964 .bb files complete (1963 cached, 1 parsed). 2536 targets, 322 
> skipped, 2 masked, 0 errors.
> NOTE: Resolving any missing task queue dependencies
>  
> Build Configuration:
> BB_VERSION= "1.28.0"
> BUILD_SYS = "x86_64-linux"
> NATIVELSBSTRING   = "Ubuntu-16.04"
> TARGET_SYS= "x86_64-poky-linux"
> MACHINE   = "gr-mrb-64"
> DISTRO= "poky-ivi-systemd"
> DISTRO_VERSION= "10.0+snapshot-20170713"
> TUNE_FEATURES = "m64 corei7"
> TARGET_FPU= ""
> meta  
> meta-yocto

This should be meta-poky now. How old is the metadata (version of poky / Yocto 
Project release) your distro is based on?

>
> meta-yocto-bsp= "first_build:dade0e68c645473d94e1b05020b064df40677e81”

This hash shows you are using a local branch, so I can’t guess at which version 
of poky you are using.

> meta-ias-audio
> meta-ias-boot 
> meta-ias-core 
> meta-ias-devtools 
> meta-ias-earlyapplication 
> meta-ias-graphics 
> meta-ias-gr-mrb-bsp 
> meta-ias-ivi-adapt 
> meta-ias-kc-reference 
> meta-ias-lifecycle 
> meta-ias-mediasdk 
> meta-ias-mediatransport 
> meta-ias-oss  
> meta-ias-security 
> meta-ias-setup
> meta-ias-systembus 
> meta-ias-targetutilities 
> meta-ias-vehiclebus = "master:89811f29229764d65db9b577252e9016083b8699”

I can find no references to meta-ias on layers.openembedded.org or in a Google 
search, so no idea how to help you with respect to your “iasImage” question.

> meta-intel
> meta-valleyisland = "first_build:8c15de8dbaa1414ffd0f69bea7227e7285816f85"
> meta-ivi  = "first_build:e42777ef74b476ed6702b036818bcffd4fe0d768"
> meta-filesystems  
> meta-networking   
> meta-oe   
> meta-python   = "first_build:dc5634968b270dde250690609f0015f881db81f2"
> meta-oracle-java  = "first_build:f7c98706f80a2488ad2628e5b0c6d3f9f80c24fd"
>  
> After building the bzImage from an external toolchain is it possible to build 
> (outside yocto) the iasImage necessary to boot the Gordon peak (Intel Apollo 
> lake SoC).
>  

> Also I am trying to build a sato image but:
>  
> $ bitbake core-image-sato
> Loading cache: 100% 
> ||
>  ETA:  00:00:00
> Loaded 2536 entries from dependency cache.
> Parsing recipes: 100% 
> |##|
>  Time: 00:00:00
> Parsing of 1964 .bb files complete (1963 cached, 1 parsed). 2536 targets, 322 
> skipped, 2 masked, 0 errors.
> NOTE: Resolving any missing task queue dependencies
> ERROR: Nothing RPROVIDES 'packagegroup-core-x11-sato-games' (but 
> /home/rah/workspace/intel_GP_APL/GR_Yocto/poky/meta/recipes-sato/images/core-image-sato.bb
>  RDEPENDS on or otherwise requires it)
> NOTE: Runtime target 'packagegroup-core-x11-sato-games' is unbuildable, 
> removing...
> Missing or unbuildable dependency chain was: 
> ['packagegroup-core-x11-sato-games']
> ERROR: Required build target 'core-image-sato' has no buildable providers.
> Missing or unbuildable dependency chain was: ['core-image-sato', 
> 'packagegroup-core-x11-sato-games']
>  

You are missing the following commit from either poky or oe-core:
http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/meta/recipes-sato/images/core-image-sato.bb?id=3afed1549a623d2a4921883319ff96bf3e6edc54

> Summary: There were 2 ERROR messages shown, returning a non-zero exit code.
>  
>  
> Regards,
> Francesco
>  
> 
> Francesco Camarda | EBU 
> Automotive Sr. System AE
> desk +39.095.7483536 | mobile +39.346.7897221
>  
> -- 
> ___
> meta-intel mailing list
> meta-in...@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/meta-intel

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto