Re: [yocto] Error during webkit compilation for rasberry pi3
Hi Khem, this layer is: https://layers.openembedded.org/layerindex/branch/master/layer/meta-webkit/ I've also tried to use the webkit recipe from poky but I've got the same error. In this case I used a different configuration because poky doesn't have webkitgtk-bin (mini browser). To test that I've tried to build a modified version of meta-web-kiosk (https://github.com/mont3z/meta-web-kiosk). This is still a work in progress but basically it replaces midori by epiphany. local.conf: MACHINE = "raspberrypi3" DISTRO_FEATURES_append = " x11 gles2" command: bitbake core-image-web-kiosk bblayes.conf: BBLAYERS ?= " \ /home/mont3z/yocto/poky/meta \ /home/mont3z/yocto/poky/meta-poky \ /home/mont3z/yocto/poky/meta-yocto-bsp \ /home/mont3z/yocto/meta-openembedded/meta-oe \ /home/mont3z/yocto/meta-raspberrypi \ /home/mont3z/yocto/meta-web-kiosk \ " I also found this discussion about rpi2. I'll try to run some of those configurations: https://github.com/Igalia/meta-webkit/issues/1 On Sat, Dec 10, 2016 at 1:02 PM, Khem Raj wrote: > On Sat, Dec 10, 2016 at 7:52 AM, Mont3z Claros > wrote: >> Hi all, >> >> I don't know what I'm doing wrong but I'm getting an error during >> compilation of webkit for raspberry pi3. Please see below the error >> and my configurations, >> >> Thanks, >> Mont3z >> >> local.conf: >> MACHINE = "raspberrypi3" >> DISTRO_FEATURES_append = " x11 gles2" >> IMAGE_INSTALL_append = " webkitgtk-bin" >> >> Error: >> | ERROR: oe_runmake failed >> | In file included from >> /home/mont3z/yocto/poky/build/tmp/work/cortexa7t2hf-neon-vfpv4-poky-linux-gnueabi/webkitgtk/2.14.2-r0/webkitgtk-2.14.2/Source/WebCore/platform/graphics/cairo/GraphicsContext3DCairo.cpp:51:0: >> | >> /home/mont3z/yocto/poky/build/tmp/work/cortexa7t2hf-neon-vfpv4-poky-linux-gnueabi/webkitgtk/2.14.2-r0/webkitgtk-2.14.2/Source/WebCore/platform/graphics/opengl/Extensions3DOpenGLES.h:109:5: >> error: 'PFNGLFRAMEBUFFERTEXTURE2DMULTISAMPLEIMGPROC' does not name a >> type >> | PFNGLFRAMEBUFFERTEXTURE2DMULTISAMPLEIMGPROC >> m_glFramebufferTexture2DMultisampleIMG; >> | ^~~ >> >> command: >> bitbake core-image-sato >> >> bblayes.conf: >> BBLAYERS ?= " \ >> /home/mont3z/yocto/poky/meta \ >> /home/mont3z/yocto/poky/meta-poky \ >> /home/mont3z/yocto/poky/meta-yocto-bsp \ >> /home/mont3z/yocto/meta-openembedded/meta-oe \ >> /home/mont3z/yocto/meta-webkit \ > > > what does this layer do ? > >> /home/mont3z/yocto/meta-raspberrypi \ >> " -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Error during webkit compilation for rasberry pi3
userland graphics drivers dont have gles1 support, that might be one reason for it. You might try our vc4graphics driver by adding 'vc4graphics' to MACHINE_FEATURES and then it will use mesa. On Sun, Dec 11, 2016 at 7:49 AM, Mont3z Claros wrote: > Hi Khem, > > this layer is: > https://layers.openembedded.org/layerindex/branch/master/layer/meta-webkit/ > > I've also tried to use the webkit recipe from poky but I've got the > same error. In this case I used a different configuration because poky > doesn't have webkitgtk-bin (mini browser). To test that I've tried to > build a modified version of meta-web-kiosk > (https://github.com/mont3z/meta-web-kiosk). This is still a work in > progress but basically it replaces midori by epiphany. > > local.conf: > MACHINE = "raspberrypi3" > DISTRO_FEATURES_append = " x11 gles2" > > command: > bitbake core-image-web-kiosk > > bblayes.conf: > BBLAYERS ?= " \ > /home/mont3z/yocto/poky/meta \ > /home/mont3z/yocto/poky/meta-poky \ > /home/mont3z/yocto/poky/meta-yocto-bsp \ > /home/mont3z/yocto/meta-openembedded/meta-oe \ > /home/mont3z/yocto/meta-raspberrypi \ > /home/mont3z/yocto/meta-web-kiosk \ > " > > I also found this discussion about rpi2. I'll try to run some of those > configurations: > https://github.com/Igalia/meta-webkit/issues/1 > > On Sat, Dec 10, 2016 at 1:02 PM, Khem Raj wrote: >> On Sat, Dec 10, 2016 at 7:52 AM, Mont3z Claros >> wrote: >>> Hi all, >>> >>> I don't know what I'm doing wrong but I'm getting an error during >>> compilation of webkit for raspberry pi3. Please see below the error >>> and my configurations, >>> >>> Thanks, >>> Mont3z >>> >>> local.conf: >>> MACHINE = "raspberrypi3" >>> DISTRO_FEATURES_append = " x11 gles2" >>> IMAGE_INSTALL_append = " webkitgtk-bin" >>> >>> Error: >>> | ERROR: oe_runmake failed >>> | In file included from >>> /home/mont3z/yocto/poky/build/tmp/work/cortexa7t2hf-neon-vfpv4-poky-linux-gnueabi/webkitgtk/2.14.2-r0/webkitgtk-2.14.2/Source/WebCore/platform/graphics/cairo/GraphicsContext3DCairo.cpp:51:0: >>> | >>> /home/mont3z/yocto/poky/build/tmp/work/cortexa7t2hf-neon-vfpv4-poky-linux-gnueabi/webkitgtk/2.14.2-r0/webkitgtk-2.14.2/Source/WebCore/platform/graphics/opengl/Extensions3DOpenGLES.h:109:5: >>> error: 'PFNGLFRAMEBUFFERTEXTURE2DMULTISAMPLEIMGPROC' does not name a >>> type >>> | PFNGLFRAMEBUFFERTEXTURE2DMULTISAMPLEIMGPROC >>> m_glFramebufferTexture2DMultisampleIMG; >>> | ^~~ >>> >>> command: >>> bitbake core-image-sato >>> >>> bblayes.conf: >>> BBLAYERS ?= " \ >>> /home/mont3z/yocto/poky/meta \ >>> /home/mont3z/yocto/poky/meta-poky \ >>> /home/mont3z/yocto/poky/meta-yocto-bsp \ >>> /home/mont3z/yocto/meta-openembedded/meta-oe \ >>> /home/mont3z/yocto/meta-webkit \ >> >> >> what does this layer do ? >> >>> /home/mont3z/yocto/meta-raspberrypi \ >>> " -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Kernel config incremental modification not working.
On Fri, 09 Dec 2016 11:19:56 Bruce Ashfield wrote:
> On 2016-12-09 11:17 AM, Andrea Galbusera wrote:
> > Hi Bruce,
> >
> > On Thu, Dec 8, 2016 at 3:36 PM, Bruce Ashfield
> >
> > mailto:bruce.ashfi...@windriver.com>>
wrote:
> > On 2016-12-08 09:06 AM, Bent Bisballe Nyeng wrote:
> > Hi list
> >
> > I am working on a project based on the iMX6UL-EVK using the
> > meta-fsl-arm
> > layer for the kernel.
> > In a local layer I have a bbappend recipe containing a patch for
> > an
> > extra kernel feature (a framebuffer device) in that kernel as
> > well as a
> > .cfg enabling said feature.
> > The bbappend recipe is located in
> > recipes-kernel/linux/linux-fslc-imx_%.bbappend and looks like
> > this:
> > FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}:"
> >
> > SRC_URI += " \
> >
> > file://0001-mxc-4.1.patch \
> > file://ST7789S.cfg \
> >
> > "
> >
> > KERNEL_DEVICETREE = "imx6ul-14x14-evk.dtb"
> >
> > The .cfg is located in
> > recipes-kernel/linux/linux-fslc-imx/ST7789S.cfg
> > and looks like:
> > CONFIG_FB_MXS_ST7789S_QVGA=y
> >
> > The 0001-mxc-4.1.patch patch is correctly applied but the .cfg
> > is either
> > ignored or overwritten by some later buyild step since the
> > resulting
> > .config after kernel compilation contains:
> > # CONFIG_FB_MXS_ST7789S_QVGA is not set
> >
> > I have tried finding the script in the build/.../temp folder
> > that takes
> > care of the .cfg file patching but have not been able to find
> > anything
> > useful.
> >
> > Any hints as to where I should start looking for a solution?
> >
> > Fragment processing using the kernel tools + auditing is only
> > currently
> > available to kernel recipes that use the kernel-yocto bbclass. That
> > opt-in requirement was to ensure that existing recipes and workflows
> > weren't broken by the new features.
> >
> > Last time I checked, the meta-fsl* kernel recipes don't use the
> > kernel-yocto bbclass, so the fragment would be ignored.
> >
> > I'm taking the processing of fragments and making it universally
> > available in the upcoming 2.3 release, so what I just described
> > won't be an issue for much longer.
> >
> > In the mean time, you have a few options:
> > - in your bbappend, add "inherit kernel-yocto" and the processing
> >
> >of fragments will be enabled (I can't say that I've tested
> >it against that recipe .. but the entire point of the new tasks
> >is that they are transparent/don't break existing worflows)
> >
> > - carry a defconfig in your layer, and add it to the SRC_URI. That
> >
> >defconfig would be the existing kernel recipe's defconfig + your
> >options
> >
> > I was just testing one of my layers against your recent patchset on
> > kernel-yocto when I noticed this thread. My build is broken by commit
> > 476ffd57cf5b6fba40d4e3f5dd913824ab8a8d3d on oe-core
> > (e38775a1d82e6dc60fc96cf243ecb94be964d9b2 on the poky repo side).
> >
> > WARNING: linux-altera-ltsi-4.1.22-ltsi+gitAUTOINC+76bdba2700-r0
> > do_kernel_metadata: GIZERO: before 'cmp'
> > ERROR: linux-altera-ltsi-4.1.22-ltsi+gitAUTOINC+76bdba2700-r0
> > do_kernel_metadata: Function failed: do_kernel_metadata (log file is
> > located at
> > /scratch/gizero/mitysom-5csx-master-build/tmp/work/cyclone5-poky-linux-gnu
> > eabi/linux-altera-ltsi/4.1.22-ltsi+gitAUTOINC+76bdba2700-r0/temp/log.do_ke
> > rnel_metadata.28274) ERROR: Logfile of failure stored in:
> > /scratch/gizero/mitysom-5csx-master-build/tmp/work/cyclone5-poky-linux-gnu
> > eabi/linux-altera-ltsi/4.1.22-ltsi+gitAUTOINC+76bdba2700-r0/temp/log.do_ke
> > rnel_metadata.28274>
> > Log data follows:
> > | DEBUG: Executing shell function do_kernel_metadata
> > | WARNING: GIZERO: before 'cmp'
> >
> > /scratch/gizero/mitysom-5csx-master-build/tmp/work/cyclone5-poky-linux-gnu
> > eabi/linux-altera-ltsi/4.1.22-ltsi+gitAUTOINC+76bdba2700-r0/defconfig
> > /scratch/gizero/mitysom-5csx-master-build/tmp/work-shared/cyclone5/kernel
> > -source/arch/arm/configs/socfpga_defconfig differ: byte 1525, line 72
> >
> > | WARNING: exit code 1 from a shell command.
> > | ERROR: Function failed: do_kernel_metadata (log file is located at
> >
> > /scratch/gizero/mitysom-5csx-master-build/tmp/work/cyclone5-poky-linux-gnu
> > eabi/linux-altera-ltsi/4.1.22-ltsi+gitAUTOINC+76bdba2700-r0/temp/log.do_ke
> > rnel_metadata.28274) ERROR: Task
> > (/home/gizero/work/decos/repo-master/poky/../meta-altera/recipes-kernel/li
> > nux/linux-altera-ltsi_4.1.22.bb:do_kernel_metadata) failed with exit code
> > '1'
> >
> > The commit in the patch r
Re: [yocto] libssp_nonshared.a not present in native SDK.
On Fri, Dec 9, 2016 at 1:24 AM, Rafael Gago Castano wrote:
> Hello again.
>
>
> I tried to fix this in my layers by adding a
> "recipes-devtools/gcc_5.3.bbappend" file to containing the additions that
> you did to poky on...
>
>
> http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=1c0fc7fcf7772ef8774f623126050972f526fe83
>
>
> ...as I think that adding these dependencies to gcc is the right thing.
>
>
> Running "bitbake gcc -e" shows the next:
>
>
> # $RRECOMMENDS_gcc
> # rename from RRECOMMENDS_${PN} data.py:169 [expandKeys]
> # " libssp libssp-dev "
> RRECOMMENDS_gcc=" libssp libssp-dev "
>
> So the recipe is at least processed.
>
>
> The problem is that "libssp_nonshared.a" is still not present on the SDK. It
> may happen that this is still happening in poky.
how do you generate your SDK ? if you are not using -cpopulate_sdk
then it wont come in you might need to add it to TOOLCHAIN_TARGET_TASK
>
> --
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] libssp_nonshared.a not present in native SDK.
On Fri, 09 Dec 2016 09:24:41 Rafael Gago Castano wrote:
> Hello again.
>
>
> I tried to fix this in my layers by adding a
> "recipes-devtools/gcc_5.3.bbappend" file to containing the additions that
> you did to poky on...
>
>
> http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=1c0fc7fcf7772ef877
> 4f623126050972f526fe83
>
>
> ...as I think that adding these dependencies to gcc is the right thing.
>
>
> Running "bitbake gcc -e" shows the next:
>
>
> # $RRECOMMENDS_gcc
> # rename from RRECOMMENDS_${PN} data.py:169 [expandKeys]
> # " libssp libssp-dev "
> RRECOMMENDS_gcc=" libssp libssp-dev "
>
> So the recipe is at least processed.
>
> The problem is that "libssp_nonshared.a" is still not present on the SDK. It
> may happen that this is still happening in poky.
Hmm, I just tried building an SDK (bitbake -c populate_sdk core-image-minimal)
with master and it definitely includes libssp_nonshared.a. Does the target
manifest for your SDK indicate libssp-dev is included?
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [meta-raspberrypi][PATCH] linux-raspberrypi-base.bbclass: remove version hack
On Thu, Dec 8, 2016 at 2:40 AM, Andreas Müller
wrote:
> * no more required (version > 3.17 | > 4.3.x | > 4.4.5)
> * causes error with rt kernel
>
I think this is ok to apply now.
> Signed-off-by: Andreas Müller
> ---
> classes/linux-raspberrypi-base.bbclass | 15 ---
> 1 file changed, 15 deletions(-)
>
> diff --git a/classes/linux-raspberrypi-base.bbclass
> b/classes/linux-raspberrypi-base.bbclass
> index 3a6e33d..dc2330a 100644
> --- a/classes/linux-raspberrypi-base.bbclass
> +++ b/classes/linux-raspberrypi-base.bbclass
> @@ -14,21 +14,6 @@ def get_dts(d, ver=None):
> from the kernel staging '''
> ver = get_kernelversion_file(staging_dir)
>
> -if ver is not None:
> -min_ver = ver.split('.', 3)
> -else:
> -return dts
> -
> -# Always turn off device tree support for kernel's < 3.18
> -try:
> -if int(min_ver[0]) >= 4:
> -if (int(min_ver[1]) < 4) or (int(min_ver[1]) == 4 and
> int(min_ver[2]) < 6):
> -dts = ' '.join([(re.sub(r'(.*)\.dtbo$', r'\1-overlay.dtb',
> x)) for x in dts.split()])
> -elif int(min_ver[1]) < 18:
> -dts = ""
> -except IndexError:
> -min_ver = None
> -
> return dts
>
>
> --
> 2.7.4
>
> --
> ___
> 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] [Recipe reporting system] Upgradable recipe name list
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 was detected. Example: RECIPE_NO_UPDATE_REASON = "Version 2.0 is unstable" You can check the detail information at: http://recipes.yoctoproject.org/ Package VersionUpstream version Maintainer NoUpgradeReason - -- -- liberation-fonts 1.04 2.00.1Alexander Kanavin 2.x depends on fontforge pa... liburcu 0.9.2 0.9.3 Alexander Kanavin ca-certificates 20161102 20161130 Alexander Kanavin openssl 1.0.2j 1.1.0cAlexander Kanavin icu 58.1 58.2 Alexander Kanavin vala 0.34.3 0.34.4Alexander Kanavin libfm-extra 1.2.4 1.2.5 Alexander Kanavin babeltrace1.4.0 1.5.0 Alexander Kanavin gnutls3.5.6 3.5.7 Alexander Kanavin ffmpeg3.2.1 3.2.2 Alexander Kanavin kexec-tools 2.0.12 2.0.13Alexander Kanavin btrfs-tools 4.8.4 4.8.5 Alexander Kanavin sysprof 3.22.2 3.22.3Alexander Kanavin cmake-native 3.7.0 3.7.1 Alexander Kanavin libfm 1.2.4 1.2.5 Alexander Kanavin cmake 3.7.0 3.7.1 Alexander Kanavin tiff 4.0.6 4.0.7 Alexander Kanavin mkelfimage4.0+gitX 4.5+gitAUTOINC+0b... Alexander Kanavin mkelfimage has been removed... perl 5.24.0 5.24.1Aníbal Limón dpkg 1.18.7 1.18.15 Aníbal Limón perl-native 5.24.0 5.24.1Aníbal Limón pinentry 0.9.2 1.0.0 Armin Kuster linux-libc-headers4.84.9 Bruce Ashfield systemd-bootchart 230+gitX 231+gitAUTOINC+9e... Chen Qi busybox 1.25.0+gitX1.25.1+gitAUTOINC... Chen Qi systemd-boot 1.0232 Chen Qi dbus 1.10.101.10.14 Chen Qi byacc 20160606 20161202 Chen Qi coreutils 8.25 8.26 Chen Qi cups 2.1.4 2.2.1 Chen Qi util-linux2.28.1 2.29 Chen Qi dbus-glib 0.106 0.108 Chen Qi dbus-test 1.10.101.10.14 Chen Qi sudo 1.8.17p1 1.8.18p1 Chen Qi sysstat 11.4.0 11.5.3Chen Qi flex 2.6.0 2.6.2 Chen Qi grep 2.26 2.27 Chen Qi build-appliance-i... 15.0.0 16.0.0Cristian Iorga chkconfig 1.3.58 1.8 Dengke Du Version 1.5 requires selinux ltp 20160126 20160920 Dengke Du python3-docutils 0.12 0.13.1Edwin Plauchu pcmanfm 1.2.4 1.2.5 Edwin Plauchu python3-setuptools29.0.1 31.0.0Edwin Plauchu python-setuptools 29.0.1 31.0.0Edwin Plauchu pax-utils 1.1.6 1.1.7 Hongxu Jia gnupg 2.1.14 2.1.16Hongxu Jia createrepo0.4.11 0.10.4Hongxu Jia Versions after 0.9.* use YU... elfutils 0.166 0.167 Hongxu Jia gpgme 1.6.0 1.8.0 Hongxu Jia bash 4.3.30 4.4 Hongxu Jia ghostscript 9.19 9.20rc1 Hongxu Jia ncurses 6.0+20160625 6.0+20161126 Hongxu Jia rpcbind 0.2.3 0.2.4 Hongxu Jia python-git2.1.0 2.1.1 Jose Lamego python3-git 2.1.0 2.1.1 Jose Lamego libinput 1.5.0 1.5.3 Jussi Kukkonen weston1.11.1 1.12.0Jussi Kukkonen gtk-icon-utils-na... 3.22.1 3.22.5Jussi Kukkonen xf86-inp
Re: [yocto] Error during webkit compilation for rasberry pi3
On 2016-12-11 16:49, Mont3z Claros wrote: Hi Khem, this layer is: https://layers.openembedded.org/layerindex/branch/master/layer/meta-webkit/ I've also tried to use the webkit recipe from poky but I've got the same error. In this case I used a different configuration because poky doesn't have webkitgtk-bin (mini browser). To test that I've tried to build a modified version of meta-web-kiosk (https://github.com/mont3z/meta-web-kiosk). This is still a work in progress but basically it replaces midori by epiphany. local.conf: MACHINE = "raspberrypi3" DISTRO_FEATURES_append = " x11 gles2" command: bitbake core-image-web-kiosk bblayes.conf: BBLAYERS ?= " \ /home/mont3z/yocto/poky/meta \ /home/mont3z/yocto/poky/meta-poky \ /home/mont3z/yocto/poky/meta-yocto-bsp \ /home/mont3z/yocto/meta-openembedded/meta-oe \ /home/mont3z/yocto/meta-raspberrypi \ /home/mont3z/yocto/meta-web-kiosk \ " I also found this discussion about rpi2. I'll try to run some of those configurations: https://github.com/Igalia/meta-webkit/issues/1 I built webkit for rpi3 just fine (yesterday 2016-12-11) using just poky: e38775a1d82e6dc60fc96cf243ecb94be964d9b2 meta-raspberrypi: 44d41bf3e94c4c8fe5ad5a3650572c8d17ef36c9 these were the current master as of then. What version(s) are you trying to use? On Sat, Dec 10, 2016 at 1:02 PM, Khem Raj wrote: On Sat, Dec 10, 2016 at 7:52 AM, Mont3z Claros wrote: Hi all, I don't know what I'm doing wrong but I'm getting an error during compilation of webkit for raspberry pi3. Please see below the error and my configurations, Thanks, Mont3z local.conf: MACHINE = "raspberrypi3" DISTRO_FEATURES_append = " x11 gles2" IMAGE_INSTALL_append = " webkitgtk-bin" Error: | ERROR: oe_runmake failed | In file included from /home/mont3z/yocto/poky/build/tmp/work/cortexa7t2hf-neon-vfpv4-poky-linux-gnueabi/webkitgtk/2.14.2-r0/webkitgtk-2.14.2/Source/WebCore/platform/graphics/cairo/GraphicsContext3DCairo.cpp:51:0: | /home/mont3z/yocto/poky/build/tmp/work/cortexa7t2hf-neon-vfpv4-poky-linux-gnueabi/webkitgtk/2.14.2-r0/webkitgtk-2.14.2/Source/WebCore/platform/graphics/opengl/Extensions3DOpenGLES.h:109:5: error: 'PFNGLFRAMEBUFFERTEXTURE2DMULTISAMPLEIMGPROC' does not name a type | PFNGLFRAMEBUFFERTEXTURE2DMULTISAMPLEIMGPROC m_glFramebufferTexture2DMultisampleIMG; | ^~~ command: bitbake core-image-sato bblayes.conf: BBLAYERS ?= " \ /home/mont3z/yocto/poky/meta \ /home/mont3z/yocto/poky/meta-poky \ /home/mont3z/yocto/poky/meta-yocto-bsp \ /home/mont3z/yocto/meta-openembedded/meta-oe \ /home/mont3z/yocto/meta-webkit \ what does this layer do ? /home/mont3z/yocto/meta-raspberrypi \ " -- Gary Thomas | Consulting for the MLB Associates |Embedded world -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] update mechanisms
On 09/12/16 16:13, Patrick Ohly wrote: > Kristian, I added a comment that Mender requires U-Boot. That is > correct, isn't it? I understand that this restriction allows you to > implement things like automatic rollback, but it's worth mentioning that > this comes with that limitation. Yes, that is correct, I should have added it the first time around. -- Kristian -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Ignoring Fetch errors for optional source.
> On Dec 7, 2016, at 5:00 AM, Beth 'pidge' Flanagan wrote:
>
> I've an odd use case that I wonder if anyone has a work around/way of
> doing it.
>
> I've a client who has contractors who can't have access to a certain
> segment of the code base. So for example, a recipe will have a SRC_URI
> for the main bit that everyone has access to, but an extra src_uri that
> some people won't have access to.
>
> I want to be able to just ignore any fetch/unpack errors if that extra
> src is unfetchable. Thoughts on how to achieve this?
You can append them via bbappends in a layer of its own. and control the access
to that layer. If the layer does not exist in bblayers then those repos dont
bother fetching
if there is a case where these additional stuff is must have then define
SRC_URI += “${ADDITIONAL_URIS}”
ADDITIONAL_URIS ? = “”
and let the layers fill this variables via bbappend and if it turns out to be
empty in the end
you can raise parse errors,
basically look into RDK, there are several examples of such cases.
>
> -b
>
> --
> Beth 'pidge' Flanagan
> www.toganlabs.com
>
> --
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
