Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Get Qt Extensions
  • Unsolved
Collapse
Brand Logo
  1. Home
  2. Qt Development
  3. General and Desktop
  4. GLIB-2.0 error on yocto build
Forum Updated to NodeBB v4.3 + New Features

GLIB-2.0 error on yocto build

Scheduled Pinned Locked Moved Unsolved General and Desktop
23 Posts 2 Posters 3.6k Views
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • Ronel_qtmasterR Ronel_qtmaster

    @Srioff Hi.Is glib not already included in meta/recipes-core?

    S Offline
    S Offline
    Srioff
    wrote on last edited by
    #3

    @Ronel_qtmaster it is included.

    Ronel_qtmasterR 1 Reply Last reply
    0
    • S Srioff

      @Ronel_qtmaster it is included.

      Ronel_qtmasterR Offline
      Ronel_qtmasterR Offline
      Ronel_qtmaster
      wrote on last edited by
      #4

      @Srioff now what is the link between displaymod and building the image.You want to build the image but you run display mode?

      check this https://developer.toradex.com/linux-bsp/os-development/build-yocto/build-a-reference-image-with-yocto-projectopenembedded/

      S 1 Reply Last reply
      0
      • Ronel_qtmasterR Ronel_qtmaster

        @Srioff now what is the link between displaymod and building the image.You want to build the image but you run display mode?

        check this https://developer.toradex.com/linux-bsp/os-development/build-yocto/build-a-reference-image-with-yocto-projectopenembedded/

        S Offline
        S Offline
        Srioff
        wrote on last edited by
        #5

        @Ronel_qtmaster displaymod is the name of my .bb file. i want to build an image that has qt program as the gui.
        the bitbake command that i ran was :
        bitbake displaymod

        Ronel_qtmasterR 1 Reply Last reply
        0
        • S Srioff

          @Ronel_qtmaster displaymod is the name of my .bb file. i want to build an image that has qt program as the gui.
          the bitbake command that i ran was :
          bitbake displaymod

          Ronel_qtmasterR Offline
          Ronel_qtmasterR Offline
          Ronel_qtmaster
          wrote on last edited by
          #6

          @Srioff THE PROPER way to do is to build a simple image with your recipe included.not only your recipe.So il local.conf, add the recipe for your application, then build a simple image

          S 1 Reply Last reply
          0
          • S Offline
            S Offline
            Srioff
            wrote on last edited by
            #7

            @Srioff i was able to previously build an image successfully which ran on my board with only the issue as gui didn't come up. so i modified and tried building again, that's when i faced this issue.

            Ronel_qtmasterR 1 Reply Last reply
            0
            • Ronel_qtmasterR Ronel_qtmaster

              @Srioff THE PROPER way to do is to build a simple image with your recipe included.not only your recipe.So il local.conf, add the recipe for your application, then build a simple image

              S Offline
              S Offline
              Srioff
              wrote on last edited by
              #8

              @Ronel_qtmaster Steps i followed
              created a meta layer
              added a recipe folder in which i added my recipe file and the qtprogram files
              added my layer to bblayers.conf
              in local.conf configured my machine name, added the packages-core for the program
              then ran bitbake command

              Ronel_qtmasterR 1 Reply Last reply
              0
              • S Srioff

                @Srioff i was able to previously build an image successfully which ran on my board with only the issue as gui didn't come up. so i modified and tried building again, that's when i faced this issue.

                Ronel_qtmasterR Offline
                Ronel_qtmasterR Offline
                Ronel_qtmaster
                wrote on last edited by
                #9

                @Srioff okay building an image is one thing.Making the gui start after the boot is another thing.

                1. Firstly build and image with your recipe
                2. From the Image,configure your app on start using .autostart file or Xsession file, or systemd script
                3. Disable all console output during the boot
                  4.Restart your board
                1 Reply Last reply
                0
                • S Srioff

                  @Ronel_qtmaster Steps i followed
                  created a meta layer
                  added a recipe folder in which i added my recipe file and the qtprogram files
                  added my layer to bblayers.conf
                  in local.conf configured my machine name, added the packages-core for the program
                  then ran bitbake command

                  Ronel_qtmasterR Offline
                  Ronel_qtmasterR Offline
                  Ronel_qtmaster
                  wrote on last edited by
                  #10

                  @Srioff i think you should run bitbake with the standard image not only your recipe

                  S 1 Reply Last reply
                  0
                  • Ronel_qtmasterR Ronel_qtmaster

                    @Srioff i think you should run bitbake with the standard image not only your recipe

                    S Offline
                    S Offline
                    Srioff
                    wrote on last edited by
                    #11

                    @Ronel_qtmaster with the reference image name of toradex and not my recipe?

                    Ronel_qtmasterR 1 Reply Last reply
                    0
                    • S Srioff

                      @Ronel_qtmaster with the reference image name of toradex and not my recipe?

                      Ronel_qtmasterR Offline
                      Ronel_qtmasterR Offline
                      Ronel_qtmaster
                      wrote on last edited by
                      #12

                      @Srioff yes exactly

                      S 1 Reply Last reply
                      0
                      • Ronel_qtmasterR Ronel_qtmaster

                        @Srioff yes exactly

                        S Offline
                        S Offline
                        Srioff
                        wrote on last edited by
                        #13

                        @Ronel_qtmaster
                        I'm new to Yocto and QT
                        I have added my bblayers.conf, local.conf and recipe file
                        would you please let me know what changes i need to make and bitbake command for it

                        displaymod.bb
                        DESCRIPTION = "Qt Application for Yocto"
                        LICENSE = "CLOSED"

                        PR = "r1"

                        DEPENDS += "glib-2.0 qtbase qtdeclarative qtquickcontrols2"

                        SRC_URI = "file://main.cpp
                        file://mainwindow.cpp
                        file://surround_view.cpp
                        file://mainwindow.h
                        file://Resource.qrc
                        file://surround_view.h
                        file://mainwindow.ui
                        file://surround_view.ui
                        file://wireframe_v1.pro
                        file://icons/"

                        S = "${WORKDIR}"

                        inherit qmake5

                        RDEPENDS_${PN} += "qtbase qtdeclarative qtquickcontrols2"

                        do_install:append() {
                        install -d ${D}${datadir}
                        install -m 0755 ${B}/displaymod ${D}/${bindir}
                        }

                        FILES_${PN} += "${bindir}/displaymod"

                        local.conf

                        MACHINE ?= "verdin-imx8mp"
                        ACCEPT_FSL_EULA = "1"
                        #IMAGE_INSTALL:append += " displayimage "
                        #IMAGE_INSTALL:append = "qtbase qtwayland "
                        DISTRO_FEATURES:append = " systemd"
                        VIRTUAL-RUNTIME_init_manager = " systemd"
                        DISTRO_FEATURES_BACKFILE_CONSIDERED = "sysvinit"
                        VIRTUAL-RUNTIME_initscripts = ""
                        IMAGE_INSTALL:append = " packagegroup-core-boot packagegroup-core-qt"

                        CORE_IMAGE_EXTRA_INSTALL += " packagegroup-core-x11 packagegroup-fonts packagegroup-core-full-cmdline"

                        DL_DIR ?= "${TOPDIR}/../downloads"

                        SSTATE_DIR ?= "${TOPDIR}/../sstate-cache"

                        DEPLOY_DIR = "${TOPDIR}/deploy"
                        TI_COMMON_DEPLOY = "${DEPLOY_DIR}"

                        PACKAGE_CLASSES ?= "package_ipk"

                        EXTRA_IMAGE_FEATURES ?= "debug-tweaks package-management"

                        USER_CLASSES ?= "buildstats"

                        PATCHRESOLVE = "noop"

                        bblayers.conf

                        LAYER_CONF_VERSION is increased each time build/conf/bblayers.conf

                        changes incompatibly

                        LCONF_VERSION = "7"

                        BBPATH = "${TOPDIR}"
                        BBFILES ?= ""

                        BBLAYERS_NXP ?= "
                        ${TOPDIR}/../layers/meta-toradex-nxp
                        ${TOPDIR}/../layers/meta-freescale
                        ${TOPDIR}/../layers/meta-freescale-3rdparty
                        "

                        BBLAYERS_TI ?= "
                        ${TOPDIR}/../layers/meta-toradex-ti
                        ${TOPDIR}/../layers/meta-arm/meta-arm-toolchain
                        ${TOPDIR}/../layers/meta-arm/meta-arm
                        ${TOPDIR}/../layers/meta-ti/meta-ti-bsp
                        ${TOPDIR}/../layers/meta-ti/meta-ti-extras
                        "

                        BBLAYERS ?= "
                        ${BBLAYERS_NXP}
                        ${BBLAYERS_TI}

                        ${TOPDIR}/../layers/meta-toradex-bsp-common

                        ${TOPDIR}/../layers/meta-openembedded/meta-oe
                        ${TOPDIR}/../layers/meta-openembedded/meta-filesystems
                        ${TOPDIR}/../layers/meta-openembedded/meta-gnome
                        ${TOPDIR}/../layers/meta-openembedded/meta-xfce
                        ${TOPDIR}/../layers/meta-openembedded/meta-networking
                        ${TOPDIR}/../layers/meta-openembedded/meta-multimedia
                        ${TOPDIR}/../layers/meta-openembedded/meta-python
                        ${TOPDIR}/../layers/meta-freescale-distro
                        ${TOPDIR}/../layers/meta-toradex-demos
                        ${TOPDIR}/../layers/meta-qt5
                        ${TOPDIR}/../layers/meta-security/meta-tpm

                        ${TOPDIR}/../layers/meta-toradex-distro
                        ${TOPDIR}/../layers/meta-yocto/meta-poky
                        ${TOPDIR}/../layers/openembedded-core/meta
                        ${TOPDIR}/../layers/meta-custom
                        "

                        Ronel_qtmasterR 1 Reply Last reply
                        0
                        • S Srioff

                          @Ronel_qtmaster
                          I'm new to Yocto and QT
                          I have added my bblayers.conf, local.conf and recipe file
                          would you please let me know what changes i need to make and bitbake command for it

                          displaymod.bb
                          DESCRIPTION = "Qt Application for Yocto"
                          LICENSE = "CLOSED"

                          PR = "r1"

                          DEPENDS += "glib-2.0 qtbase qtdeclarative qtquickcontrols2"

                          SRC_URI = "file://main.cpp
                          file://mainwindow.cpp
                          file://surround_view.cpp
                          file://mainwindow.h
                          file://Resource.qrc
                          file://surround_view.h
                          file://mainwindow.ui
                          file://surround_view.ui
                          file://wireframe_v1.pro
                          file://icons/"

                          S = "${WORKDIR}"

                          inherit qmake5

                          RDEPENDS_${PN} += "qtbase qtdeclarative qtquickcontrols2"

                          do_install:append() {
                          install -d ${D}${datadir}
                          install -m 0755 ${B}/displaymod ${D}/${bindir}
                          }

                          FILES_${PN} += "${bindir}/displaymod"

                          local.conf

                          MACHINE ?= "verdin-imx8mp"
                          ACCEPT_FSL_EULA = "1"
                          #IMAGE_INSTALL:append += " displayimage "
                          #IMAGE_INSTALL:append = "qtbase qtwayland "
                          DISTRO_FEATURES:append = " systemd"
                          VIRTUAL-RUNTIME_init_manager = " systemd"
                          DISTRO_FEATURES_BACKFILE_CONSIDERED = "sysvinit"
                          VIRTUAL-RUNTIME_initscripts = ""
                          IMAGE_INSTALL:append = " packagegroup-core-boot packagegroup-core-qt"

                          CORE_IMAGE_EXTRA_INSTALL += " packagegroup-core-x11 packagegroup-fonts packagegroup-core-full-cmdline"

                          DL_DIR ?= "${TOPDIR}/../downloads"

                          SSTATE_DIR ?= "${TOPDIR}/../sstate-cache"

                          DEPLOY_DIR = "${TOPDIR}/deploy"
                          TI_COMMON_DEPLOY = "${DEPLOY_DIR}"

                          PACKAGE_CLASSES ?= "package_ipk"

                          EXTRA_IMAGE_FEATURES ?= "debug-tweaks package-management"

                          USER_CLASSES ?= "buildstats"

                          PATCHRESOLVE = "noop"

                          bblayers.conf

                          LAYER_CONF_VERSION is increased each time build/conf/bblayers.conf

                          changes incompatibly

                          LCONF_VERSION = "7"

                          BBPATH = "${TOPDIR}"
                          BBFILES ?= ""

                          BBLAYERS_NXP ?= "
                          ${TOPDIR}/../layers/meta-toradex-nxp
                          ${TOPDIR}/../layers/meta-freescale
                          ${TOPDIR}/../layers/meta-freescale-3rdparty
                          "

                          BBLAYERS_TI ?= "
                          ${TOPDIR}/../layers/meta-toradex-ti
                          ${TOPDIR}/../layers/meta-arm/meta-arm-toolchain
                          ${TOPDIR}/../layers/meta-arm/meta-arm
                          ${TOPDIR}/../layers/meta-ti/meta-ti-bsp
                          ${TOPDIR}/../layers/meta-ti/meta-ti-extras
                          "

                          BBLAYERS ?= "
                          ${BBLAYERS_NXP}
                          ${BBLAYERS_TI}

                          ${TOPDIR}/../layers/meta-toradex-bsp-common

                          ${TOPDIR}/../layers/meta-openembedded/meta-oe
                          ${TOPDIR}/../layers/meta-openembedded/meta-filesystems
                          ${TOPDIR}/../layers/meta-openembedded/meta-gnome
                          ${TOPDIR}/../layers/meta-openembedded/meta-xfce
                          ${TOPDIR}/../layers/meta-openembedded/meta-networking
                          ${TOPDIR}/../layers/meta-openembedded/meta-multimedia
                          ${TOPDIR}/../layers/meta-openembedded/meta-python
                          ${TOPDIR}/../layers/meta-freescale-distro
                          ${TOPDIR}/../layers/meta-toradex-demos
                          ${TOPDIR}/../layers/meta-qt5
                          ${TOPDIR}/../layers/meta-security/meta-tpm

                          ${TOPDIR}/../layers/meta-toradex-distro
                          ${TOPDIR}/../layers/meta-yocto/meta-poky
                          ${TOPDIR}/../layers/openembedded-core/meta
                          ${TOPDIR}/../layers/meta-custom
                          "

                          Ronel_qtmasterR Offline
                          Ronel_qtmasterR Offline
                          Ronel_qtmaster
                          wrote on last edited by
                          #14

                          @Srioff everything should be okay.Now init the build Environment.You will see the differents images you can build with bitbake

                          S 1 Reply Last reply
                          0
                          • Ronel_qtmasterR Ronel_qtmaster

                            @Srioff everything should be okay.Now init the build Environment.You will see the differents images you can build with bitbake

                            S Offline
                            S Offline
                            Srioff
                            wrote on last edited by
                            #15

                            @Ronel_qtmaster Thank you
                            i did a base build as you told and then when i tried to build my program i got this error:

                            ERROR: displaymod-1.0.0-r1 do_install: ExecutionError(‘/home/user1/oe-core/build/tmp/work/cortexa53-tdx-linux/displaymod/1.0.0-r1/temp/run.do_install.316633’, 1, None, None)
                            ERROR: Logfile of failure stored in: /home/user1/oe-core/build/tmp/work/cortexa53-tdx-linux/displaymod/1.0.0-r1/temp/log.do_install.316633
                            Log data follows:
                            | DEBUG: Executing python function extend_recipe_sysroot
                            | NOTE: Direct dependencies are [‘/home/user1/oe-core/build/…/layers/meta-qt5/recipes-qt/qt5/qtbase-native_git.bb:do_populate_sysroot’, ‘/home/user1/oe-core/build/…/layers/meta-qt5/recipes-qt/qt5/qtbase_git.bb:do_populate_sysroot’, ‘/home/user1/oe-core/build/…/layers/meta-qt5/recipes-qt/qt5/qtdeclarative_git.bb:do_populate_sysroot’, ‘/home/user1/oe-core/build/…/layers/meta-qt5/recipes-qt/qt5/qtquickcontrols2_git.bb:do_populate_sysroot’, ‘/home/user1/oe-core/build/…/layers/openembedded-core/meta/recipes-core/glibc/glibc_2.35.bb:do_populate_sysroot’, ‘/home/user1/oe-core/build/…/layers/openembedded-core/meta/recipes-devtools/gcc/gcc-cross_11.4.bb:do_populate_sysroot’, ‘/home/user1/oe-core/build/…/layers/openembedded-core/meta/recipes-devtools/gcc/gcc-runtime_11.4.bb:do_populate_sysroot’, ‘/home/user1/oe-core/build/…/layers/openembedded-core/meta/recipes-devtools/quilt/quilt-native_0.67.bb:do_populate_sysroot’, ‘virtual:native:/home/user1/oe-core/build/…/layers/openembedded-core/meta/recipes-devtools/patch/patch_2.7.6.bb:do_populate_sysroot’, ‘virtual:native:/home/user1/oe-core/build/…/layers/openembedded-core/meta/recipes-devtools/pseudo/pseudo_git.bb:do_populate_sysroot’]
                            | NOTE: Installed into sysroot:
                            | NOTE: Skipping as already exists in sysroot: [‘qtbase-native’, ‘qtbase’, ‘qtdeclarative’, ‘qtquickcontrols2’, ‘glibc’, ‘gcc-cross-aarch64’, ‘gcc-runtime’, ‘quilt-native’, ‘patch-native’, ‘pseudo-native’, ‘zlib-native’, ‘dbus-native’, ‘libpcre2’, ‘imx-gpu-viv’, ‘libpng’, ‘libxkbcommon’, ‘fontconfig’, ‘xcb-util-image’, ‘freetype’, ‘libxcb’, ‘zlib’, ‘xcb-util-wm’, ‘libxext’, ‘openssl’, ‘vulkan-headers’, ‘xcb-util-renderutil’, ‘dbus’, ‘icu’, ‘xcb-util-keysyms’, ‘glib-2.0’, ‘systemd’, ‘libdrm’, ‘sqlite3’, ‘libjpeg-turbo’, ‘libgcc’, ‘linux-libc-headers’, ‘binutils-cross-aarch64’, ‘gmp-native’, ‘xz-native’, ‘flex-native’, ‘texinfo-dummy-native’, ‘zstd-native’, ‘libtool-native’, ‘libmpc-native’, ‘gnu-config-native’, ‘mpfr-native’, ‘attr-native’, ‘expat-native’, ‘gettext-minimal-native’, ‘glib-2.0-native’, ‘bzip2’, ‘wayland’, ‘libxxf86vm’, ‘mesa’, ‘libxshmfence’, ‘wayland-protocols’, ‘libxml2’, ‘xkeyboard-config’, ‘util-linux’, ‘expat’, ‘xcb-util’, ‘libpthread-stubs’, ‘libxau’, ‘xorgproto’, ‘libxdmcp’, ‘xcb-proto’, ‘libx11’, ‘util-macros’, ‘opkg-utils’, ‘autoconf-archive’, ‘shadow-native’, ‘base-passwd’, ‘base-files’, ‘shadow’, ‘shadow-sysroot’, ‘libsm’, ‘libpcre’, ‘libffi’, ‘bash-completion’, ‘libpam’, ‘libseccomp’, ‘kmod’, ‘acl’, ‘zstd’, ‘libcap’, ‘libpciaccess’, ‘m4-native’, ‘cmake-native’, ‘gettext-native’, ‘libpcre-native’, ‘python3-native’, ‘libffi-native’, ‘util-linux-native’, ‘libxfixes’, ‘libxdamage’, ‘xrandr’, ‘python3’, ‘util-linux-libuuid’, ‘libcap-ng’, ‘libxcrypt’, ‘ncurses’, ‘xtrans’, ‘attr’, ‘libice’, ‘flex’, ‘cracklib’, ‘xz’, ‘bzip2-native’, ‘ncurses-native’, ‘curl-native’, ‘sqlite3-native’, ‘util-linux-libuuid-native’, ‘openssl-native’, ‘readline-native’, ‘libtirpc-native’, ‘gdbm-native’, ‘libnsl2-native’, ‘libpcre2-native’, ‘libcap-ng-native’, ‘libxrandr’, ‘libxrender’, ‘libnsl2’, ‘gdbm’, ‘readline’, ‘libtirpc’, ‘perl-native’, ‘make-native’]
                            | DEBUG: Python function extend_recipe_sysroot finished
                            | DEBUG: Executing shell function do_install
                            | install: cannot stat ‘/home/user1/oe-core/build/tmp/work/cortexa53-tdx-linux/displaymod/1.0.0-r1/build/displaymod’: No such file or directory
                            | WARNING: exit code 1 from a shell command.
                            ERROR: Task (/home/user1/oe-core/build/…/layers/meta-custom/recipes-cnhi/displaymod/displaymod_1.0.0.bb:do_install) failed with exit code ‘1’
                            NOTE: Tasks Summary: Attempted 8145 tasks of which 8131 didn’t need to be rerun and 1 failed.
                            NOTE: Writing buildhistory
                            NOTE: Writing buildhistory took: 7 seconds

                            Summary: 1 task failed:
                            /home/user1/oe-core/build/…/layers/meta-custom/recipes-cnhi/displaymod/displaymod_1.0.0.bb:do_install
                            Summary: There were 5 WARNING messages.
                            Summary: There was 1 ERROR message, returning a non-zero exit code

                            Ronel_qtmasterR 1 Reply Last reply
                            0
                            • S Srioff

                              @Ronel_qtmaster Thank you
                              i did a base build as you told and then when i tried to build my program i got this error:

                              ERROR: displaymod-1.0.0-r1 do_install: ExecutionError(‘/home/user1/oe-core/build/tmp/work/cortexa53-tdx-linux/displaymod/1.0.0-r1/temp/run.do_install.316633’, 1, None, None)
                              ERROR: Logfile of failure stored in: /home/user1/oe-core/build/tmp/work/cortexa53-tdx-linux/displaymod/1.0.0-r1/temp/log.do_install.316633
                              Log data follows:
                              | DEBUG: Executing python function extend_recipe_sysroot
                              | NOTE: Direct dependencies are [‘/home/user1/oe-core/build/…/layers/meta-qt5/recipes-qt/qt5/qtbase-native_git.bb:do_populate_sysroot’, ‘/home/user1/oe-core/build/…/layers/meta-qt5/recipes-qt/qt5/qtbase_git.bb:do_populate_sysroot’, ‘/home/user1/oe-core/build/…/layers/meta-qt5/recipes-qt/qt5/qtdeclarative_git.bb:do_populate_sysroot’, ‘/home/user1/oe-core/build/…/layers/meta-qt5/recipes-qt/qt5/qtquickcontrols2_git.bb:do_populate_sysroot’, ‘/home/user1/oe-core/build/…/layers/openembedded-core/meta/recipes-core/glibc/glibc_2.35.bb:do_populate_sysroot’, ‘/home/user1/oe-core/build/…/layers/openembedded-core/meta/recipes-devtools/gcc/gcc-cross_11.4.bb:do_populate_sysroot’, ‘/home/user1/oe-core/build/…/layers/openembedded-core/meta/recipes-devtools/gcc/gcc-runtime_11.4.bb:do_populate_sysroot’, ‘/home/user1/oe-core/build/…/layers/openembedded-core/meta/recipes-devtools/quilt/quilt-native_0.67.bb:do_populate_sysroot’, ‘virtual:native:/home/user1/oe-core/build/…/layers/openembedded-core/meta/recipes-devtools/patch/patch_2.7.6.bb:do_populate_sysroot’, ‘virtual:native:/home/user1/oe-core/build/…/layers/openembedded-core/meta/recipes-devtools/pseudo/pseudo_git.bb:do_populate_sysroot’]
                              | NOTE: Installed into sysroot:
                              | NOTE: Skipping as already exists in sysroot: [‘qtbase-native’, ‘qtbase’, ‘qtdeclarative’, ‘qtquickcontrols2’, ‘glibc’, ‘gcc-cross-aarch64’, ‘gcc-runtime’, ‘quilt-native’, ‘patch-native’, ‘pseudo-native’, ‘zlib-native’, ‘dbus-native’, ‘libpcre2’, ‘imx-gpu-viv’, ‘libpng’, ‘libxkbcommon’, ‘fontconfig’, ‘xcb-util-image’, ‘freetype’, ‘libxcb’, ‘zlib’, ‘xcb-util-wm’, ‘libxext’, ‘openssl’, ‘vulkan-headers’, ‘xcb-util-renderutil’, ‘dbus’, ‘icu’, ‘xcb-util-keysyms’, ‘glib-2.0’, ‘systemd’, ‘libdrm’, ‘sqlite3’, ‘libjpeg-turbo’, ‘libgcc’, ‘linux-libc-headers’, ‘binutils-cross-aarch64’, ‘gmp-native’, ‘xz-native’, ‘flex-native’, ‘texinfo-dummy-native’, ‘zstd-native’, ‘libtool-native’, ‘libmpc-native’, ‘gnu-config-native’, ‘mpfr-native’, ‘attr-native’, ‘expat-native’, ‘gettext-minimal-native’, ‘glib-2.0-native’, ‘bzip2’, ‘wayland’, ‘libxxf86vm’, ‘mesa’, ‘libxshmfence’, ‘wayland-protocols’, ‘libxml2’, ‘xkeyboard-config’, ‘util-linux’, ‘expat’, ‘xcb-util’, ‘libpthread-stubs’, ‘libxau’, ‘xorgproto’, ‘libxdmcp’, ‘xcb-proto’, ‘libx11’, ‘util-macros’, ‘opkg-utils’, ‘autoconf-archive’, ‘shadow-native’, ‘base-passwd’, ‘base-files’, ‘shadow’, ‘shadow-sysroot’, ‘libsm’, ‘libpcre’, ‘libffi’, ‘bash-completion’, ‘libpam’, ‘libseccomp’, ‘kmod’, ‘acl’, ‘zstd’, ‘libcap’, ‘libpciaccess’, ‘m4-native’, ‘cmake-native’, ‘gettext-native’, ‘libpcre-native’, ‘python3-native’, ‘libffi-native’, ‘util-linux-native’, ‘libxfixes’, ‘libxdamage’, ‘xrandr’, ‘python3’, ‘util-linux-libuuid’, ‘libcap-ng’, ‘libxcrypt’, ‘ncurses’, ‘xtrans’, ‘attr’, ‘libice’, ‘flex’, ‘cracklib’, ‘xz’, ‘bzip2-native’, ‘ncurses-native’, ‘curl-native’, ‘sqlite3-native’, ‘util-linux-libuuid-native’, ‘openssl-native’, ‘readline-native’, ‘libtirpc-native’, ‘gdbm-native’, ‘libnsl2-native’, ‘libpcre2-native’, ‘libcap-ng-native’, ‘libxrandr’, ‘libxrender’, ‘libnsl2’, ‘gdbm’, ‘readline’, ‘libtirpc’, ‘perl-native’, ‘make-native’]
                              | DEBUG: Python function extend_recipe_sysroot finished
                              | DEBUG: Executing shell function do_install
                              | install: cannot stat ‘/home/user1/oe-core/build/tmp/work/cortexa53-tdx-linux/displaymod/1.0.0-r1/build/displaymod’: No such file or directory
                              | WARNING: exit code 1 from a shell command.
                              ERROR: Task (/home/user1/oe-core/build/…/layers/meta-custom/recipes-cnhi/displaymod/displaymod_1.0.0.bb:do_install) failed with exit code ‘1’
                              NOTE: Tasks Summary: Attempted 8145 tasks of which 8131 didn’t need to be rerun and 1 failed.
                              NOTE: Writing buildhistory
                              NOTE: Writing buildhistory took: 7 seconds

                              Summary: 1 task failed:
                              /home/user1/oe-core/build/…/layers/meta-custom/recipes-cnhi/displaymod/displaymod_1.0.0.bb:do_install
                              Summary: There were 5 WARNING messages.
                              Summary: There was 1 ERROR message, returning a non-zero exit code

                              Ronel_qtmasterR Offline
                              Ronel_qtmasterR Offline
                              Ronel_qtmaster
                              wrote on last edited by
                              #16

                              @Srioff hi.The base build should already have your program if you included the recipe for it

                              S 1 Reply Last reply
                              0
                              • Ronel_qtmasterR Ronel_qtmaster

                                @Srioff hi.The base build should already have your program if you included the recipe for it

                                S Offline
                                S Offline
                                Srioff
                                wrote on last edited by
                                #17

                                @Ronel_qtmaster I included my recipe by creating another custom layer and also added that custom layer to bblayer.conf and included the recipe to install in
                                IMAGE_INSTALL:append = "<name>"
                                under local.conf

                                Ronel_qtmasterR 1 Reply Last reply
                                0
                                • S Srioff

                                  @Ronel_qtmaster I included my recipe by creating another custom layer and also added that custom layer to bblayer.conf and included the recipe to install in
                                  IMAGE_INSTALL:append = "<name>"
                                  under local.conf

                                  Ronel_qtmasterR Offline
                                  Ronel_qtmasterR Offline
                                  Ronel_qtmaster
                                  wrote on last edited by
                                  #18

                                  @Srioff when building your recipe it has already built your app.You just have to search in the install dir.You can refer to the pro file

                                  S 3 Replies Last reply
                                  0
                                  • Ronel_qtmasterR Ronel_qtmaster

                                    @Srioff when building your recipe it has already built your app.You just have to search in the install dir.You can refer to the pro file

                                    S Offline
                                    S Offline
                                    Srioff
                                    wrote on last edited by
                                    #19
                                    This post is deleted!
                                    1 Reply Last reply
                                    0
                                    • Ronel_qtmasterR Ronel_qtmaster

                                      @Srioff when building your recipe it has already built your app.You just have to search in the install dir.You can refer to the pro file

                                      S Offline
                                      S Offline
                                      Srioff
                                      wrote on last edited by
                                      #20

                                      @Ronel_qtmaster
                                      thank you,
                                      But the issue is with do_install() part of it
                                      another hello-world qt application i was able to find in the /usr/bin folder but not the new program

                                      1 Reply Last reply
                                      0
                                      • Ronel_qtmasterR Ronel_qtmaster

                                        @Srioff when building your recipe it has already built your app.You just have to search in the install dir.You can refer to the pro file

                                        S Offline
                                        S Offline
                                        Srioff
                                        wrote on last edited by
                                        #21

                                        @Ronel_qtmaster
                                        I came across this error
                                        Please set FILES such that these items are packaged. Alternatively if they are unneeded, avoid installing them or delete them within do_install.
                                        wireframe: 61 installed and not shipped files. [installed-vs-shipped]
                                        ERROR: wireframe-1.0.0-r1 do_package: Fatal QA errors were found, failing task.
                                        ERROR: Logfile of failure stored in: /home/inbe1e-dt550cn/oe-core/build/tmp/work/cortexa53-tdx-linux/wireframe/1.0.0-r1/temp/log.do_package.199565
                                        ERROR: Task (/home/inbe1e-dt550cn/oe-core/build/../layers/meta-custom/recipes-cnhi/wireframe/wireframe_1.0.0.bb:do_package) failed with exit code '1

                                        i dont know what to do

                                        Ronel_qtmasterR 1 Reply Last reply
                                        0
                                        • S Srioff

                                          @Ronel_qtmaster
                                          I came across this error
                                          Please set FILES such that these items are packaged. Alternatively if they are unneeded, avoid installing them or delete them within do_install.
                                          wireframe: 61 installed and not shipped files. [installed-vs-shipped]
                                          ERROR: wireframe-1.0.0-r1 do_package: Fatal QA errors were found, failing task.
                                          ERROR: Logfile of failure stored in: /home/inbe1e-dt550cn/oe-core/build/tmp/work/cortexa53-tdx-linux/wireframe/1.0.0-r1/temp/log.do_package.199565
                                          ERROR: Task (/home/inbe1e-dt550cn/oe-core/build/../layers/meta-custom/recipes-cnhi/wireframe/wireframe_1.0.0.bb:do_package) failed with exit code '1

                                          i dont know what to do

                                          Ronel_qtmasterR Offline
                                          Ronel_qtmasterR Offline
                                          Ronel_qtmaster
                                          wrote on last edited by Ronel_qtmaster
                                          #22

                                          @Srioff Good Morning.It seems you have a problem with the creation of recipes.I don't know which tutorial you used to create your recipe but as you're a beginner with yocto, do not start directly with the creation of recipes without enough understanding of yocto.That said , after you compile a simple image, setup yocto in Qt, create a simple project and deploy it to your target board directly.

                                          To wrap up
                                          1 - Remove your custom recipe
                                          2- Build a simple image with qt included
                                          3- Build the qt sdk to use it in Qt IDE
                                          4-Install and setup the sdk in qt creator, add your device through ssh
                                          5-create a simple project
                                          6-Build it and deploy it to the target board
                                          7-Test your program
                                          8-Autostart your program using systemd script or x11

                                          Only when you have mastered these steps that you can try with recipes.I mean when you will understand a bit more yocto.
                                          Hope it helps

                                          S 1 Reply Last reply
                                          0

                                          • Login

                                          • Login or register to search.
                                          • First post
                                            Last post
                                          0
                                          • Categories
                                          • Recent
                                          • Tags
                                          • Popular
                                          • Users
                                          • Groups
                                          • Search
                                          • Get Qt Extensions
                                          • Unsolved