Re: [yocto] [Meta-Qt5] "Unknown Module: declarative" Error While Creating Toolchain
Hi Khem, Thank you for your answer. I have built a toolchain as exactly as you said, days ago. But it was giving error Unknown Modules: widgets when I try to compile. Me and my BSP found that this is a know Qt layer issue that will not be solved til an update is pushed to meta-qt5 layer. Thank you anyway, I am trying to native compile over Debian. Have a great week! Onur Khem Raj , 15 Tem 2019 Pzt, 03:55 tarihinde şunu yazdı: > On Mon, Jul 8, 2019 at 10:59 PM Onur Eser wrote: > > > > Hello All, > > > > I have talked to my BSP provider and they have solved the conflict files > issue with an update. Now I am able to create and boot a Yocto Image with > Meta-Qt5 recipes and 'dev_pkgs' in it. But still cannot create a toolchain. > Nor with I guess it is trying to compile something before qtdeclarative, > but these 'something' depends on qtdeclarative. > > > > My image is core image is Weston. I added the line 'inherit > populate_sdk_qt5' to my core-image-weston.bb file. And tried both > commands 'bitbake meta-toolchain-qt5' and 'bitbake -c populate_sdk > core-image-weston'. The result is the same. > > > > I cut just the error part of my output: > > > > | cd qdeclarativefolderlistmodel/ && ( test -e Makefile || > /home/closx/poky/build/tmp/work/cortexa9hf-neon-poky-linux-gnueabi/qtquick1/5.10.1+gitAUTOINC+b2476dcd53-r0/recipe-sysroot-native/usr/bin/qt5/qmake > -o Makefile > /home/closx/poky/build/tmp/work/cortexa9hf-neon-poky-linux-gnueabi/qtquick1/5.10.1+gitAUTOINC+b2476dcd53-r0/git/tests/auto/declarative/qdeclarativefolderlistmodel/ > qdeclarativefolderlistmodel.pro ) && make -f Makefile > > | Project ERROR: Unknown module(s) in QT: declarative widgets > > | Makefile:88: recipe for target 'sub-qdeclarativecomponent-make_first' > failed > > | make[2]: *** [sub-qdeclarativecomponent-make_first] Error 3 > > | make[2]: *** Waiting for unfinished jobs > > | Project ERROR: Unknown module(s) in QT: declarative > > | Project ERROR: Unknown module(s) in QT: declarative > > | Makefile:113: recipe for target 'sub-qdeclarativecontext-make_first' > failed > > | make[2]: *** [sub-qdeclarativecontext-make_first] Error 3 > > | Project ERROR: Unknown module(s) in QT: declarative > > | Makefile:138: recipe for target 'sub-qdeclarativeengine-make_first' > failed > > | make[2]: *** [sub-qdeclarativeengine-make_first] Error 3 > > | Makefile:63: recipe for target 'sub-parserstress-make_first' failed > > | make[2]: *** [sub-parserstress-make_first] Error 3 > > | make[2]: Entering directory > '/home/closx/poky/build/tmp/work/cortexa9hf-neon-poky-linux-gnueabi/qtquick1/5.10.1+gitAUTOINC+b2476dcd53-r0/build/tests/manual/declarative' > > | make[2]: Nothing to be done for 'first'. > > | make[2]: Leaving directory > '/home/closx/poky/build/tmp/work/cortexa9hf-neon-poky-linux-gnueabi/qtquick1/5.10.1+gitAUTOINC+b2476dcd53-r0/build/tests/manual/declarative' > > | make[1]: Leaving directory > '/home/closx/poky/build/tmp/work/cortexa9hf-neon-poky-linux-gnueabi/qtquick1/5.10.1+gitAUTOINC+b2476dcd53-r0/build/tests/manual' > > | Project ERROR: Unknown module(s) in QT: declarative > > | Makefile:163: recipe for target 'sub-qdeclarativeerror-make_first' > failed > > | make[2]: *** [sub-qdeclarativeerror-make_first] Error 3 > > | Project ERROR: Unknown module(s) in QT: declarative > > | Makefile:188: recipe for target > 'sub-qdeclarativefolderlistmodel-make_first' failed > > | make[2]: *** [sub-qdeclarativefolderlistmodel-make_first] Error 3 > > | make[2]: Leaving directory > '/home/closx/poky/build/tmp/work/cortexa9hf-neon-poky-linux-gnueabi/qtquick1/5.10.1+gitAUTOINC+b2476dcd53-r0/build/tests/auto/declarative' > > | Makefile:45: recipe for target 'sub-declarative-make_first' failed > > | make[1]: *** [sub-declarative-make_first] Error 2 > > | make[1]: Leaving directory > '/home/closx/poky/build/tmp/work/cortexa9hf-neon-poky-linux-gnueabi/qtquick1/5.10.1+gitAUTOINC+b2476dcd53-r0/build/tests/auto' > > | Makefile:45: recipe for target 'sub-auto-make_first' failed > > | make: *** [sub-auto-make_first] Error 2 > > | ERROR: oe_runmake failed > > | WARNING: exit code 1 from a shell command. > > | ERROR: Function failed: do_compile_ptest_base (log file is located at > /home/closx/poky/build/tmp/work/cortexa9hf-neon-poky-linux-gnueabi/qtquick1/5.10.1+gitAUTOINC+b2476dcd53-r0/temp/log.do_compile_ptest_base.29566) > > ERROR: Task > > (/home/closx/poky/meta-qt5/recipes-qt/qt5/qtquick1_git.bb:do_compile_ptest_base) >
Re: [yocto] [Meta-Qt5] "Unknown Module: declarative" Error While Creating Toolchain
Hello everyone, I have tried the thud branch as Zoran suggested. Faced exactly the same issue. Any other suggestions? Output: https://paste.ee/p/PupWr#Epvqnw9FoasgQEBhIXqQ8hH7veMcRybX I have built a system with qt5 recipes, but cannot create a toolchain for it since a week ago. Am I retarded? Have a lovely day! Onur Zoran Stojsavljevic , 9 Tem 2019 Sal, 12:47 tarihinde şunu yazdı: > One thing on my prio list is to buy very powerful 16 or 32 INTEL core > 6950 or + server. Maybe AMD Ryzen 32 or 64 core (most likely). This > almost eliminates this build problem... But in the current situation I > am presently, I could not even buy extra bubble gum. ;-) > > I have only my HP Elite Book 840 G1 which has 4 HW threads (2C + > 2HYP), and I have the same problem for YOCTO. To build any YOCTO build > goes forever (the extras is that I have 500GB SSD there, which makes > it much faster). > > But, nevertheless, the newer, the better... Hopefully! Toradex YOCTO > gurus may hop to this thread, and help... > > Zoran > _______ > > On Tue, Jul 9, 2019 at 11:12 AM Onur Eser wrote: > > > > Zoran, > > > > I know you are not a Qt Layers expert. I am trying to describe my > problem to experts via common mails, so they will not missunderstand my > issue. > > Oh lord, whole new building... I am not a time traveller, but I can say > that I will wait for 10 hours or something for that to build, and it will > fail because of something else. > > The worst part is, it gives the error on the FINAL STEP. After hours and > hours and hours. > > Anyway, I will try thud branch. Wish me luck. > > > > Others can still offer solutions, I will keep this build too. > > Onur > -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [Meta-Qt5] "Unknown Module: declarative" Error While Creating Toolchain
Zoran, I know you are not a Qt Layers expert. I am trying to describe my problem to experts via common mails, so they will not missunderstand my issue. Oh lord, whole new building... I am not a time traveller, but I can say that I will wait for 10 hours or something for that to build, and it will fail because of something else. The worst part is, it gives the error on the FINAL STEP. After hours and hours and hours. Anyway, I will try thud branch. Wish me luck. Others can still offer solutions, I will keep this build too. Onur -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [Meta-Qt5] "Unknown Module: declarative" Error While Creating Toolchain
Hello Zoran! Thank you for your answer, but that page is about the missing packages in your configuration. There is no a missing dependency in my configuration. The recipe "qtdeclarative" is already added. Note: Sending again because sent as PM accidentally. Thanks anyway! Onur Zoran Stojsavljevic , 9 Tem 2019 Sal, 10:59 tarihinde şunu yazdı: > Maybe this: > > https://www.technexion.com/support/knowledgebase/resolving-dependencies-issues-in-yocto/ > > Zoran > ___ > > On Tue, Jul 9, 2019 at 7:59 AM Onur Eser wrote: > > > > Hello All, > > > > I have talked to my BSP provider and they have solved the conflict files > issue with an update. Now I am able to create and boot a Yocto Image with > Meta-Qt5 recipes and 'dev_pkgs' in it. But still cannot create a toolchain. > Nor with I guess it is trying to compile something before qtdeclarative, > but these 'something' depends on qtdeclarative. > > > > My image is core image is Weston. I added the line 'inherit > populate_sdk_qt5' to my core-image-weston.bb file. And tried both > commands 'bitbake meta-toolchain-qt5' and 'bitbake -c populate_sdk > core-image-weston'. The result is the same. > > > > I cut just the error part of my output: > > > > | cd qdeclarativefolderlistmodel/ && ( test -e Makefile || > /home/closx/poky/build/tmp/work/cortexa9hf-neon-poky-linux-gnueabi/qtquick1/5.10.1+gitAUTOINC+b2476dcd53-r0/recipe-sysroot-native/usr/bin/qt5/qmake > -o Makefile > /home/closx/poky/build/tmp/work/cortexa9hf-neon-poky-linux-gnueabi/qtquick1/5.10.1+gitAUTOINC+b2476dcd53-r0/git/tests/auto/declarative/qdeclarativefolderlistmodel/ > qdeclarativefolderlistmodel.pro ) && make -f Makefile > > | Project ERROR: Unknown module(s) in QT: declarative widgets > > | Makefile:88: recipe for target 'sub-qdeclarativecomponent-make_first' > failed > > | make[2]: *** [sub-qdeclarativecomponent-make_first] Error 3 > > | make[2]: *** Waiting for unfinished jobs > > | Project ERROR: Unknown module(s) in QT: declarative > > | Project ERROR: Unknown module(s) in QT: declarative > > | Makefile:113: recipe for target 'sub-qdeclarativecontext-make_first' > failed > > | make[2]: *** [sub-qdeclarativecontext-make_first] Error 3 > > | Project ERROR: Unknown module(s) in QT: declarative > > | Makefile:138: recipe for target 'sub-qdeclarativeengine-make_first' > failed > > | make[2]: *** [sub-qdeclarativeengine-make_first] Error 3 > > | Makefile:63: recipe for target 'sub-parserstress-make_first' failed > > | make[2]: *** [sub-parserstress-make_first] Error 3 > > | make[2]: Entering directory > '/home/closx/poky/build/tmp/work/cortexa9hf-neon-poky-linux-gnueabi/qtquick1/5.10.1+gitAUTOINC+b2476dcd53-r0/build/tests/manual/declarative' > > | make[2]: Nothing to be done for 'first'. > > | make[2]: Leaving directory > '/home/closx/poky/build/tmp/work/cortexa9hf-neon-poky-linux-gnueabi/qtquick1/5.10.1+gitAUTOINC+b2476dcd53-r0/build/tests/manual/declarative' > > | make[1]: Leaving directory > '/home/closx/poky/build/tmp/work/cortexa9hf-neon-poky-linux-gnueabi/qtquick1/5.10.1+gitAUTOINC+b2476dcd53-r0/build/tests/manual' > > | Project ERROR: Unknown module(s) in QT: declarative > > | Makefile:163: recipe for target 'sub-qdeclarativeerror-make_first' > failed > > | make[2]: *** [sub-qdeclarativeerror-make_first] Error 3 > > | Project ERROR: Unknown module(s) in QT: declarative > > | Makefile:188: recipe for target > 'sub-qdeclarativefolderlistmodel-make_first' failed > > | make[2]: *** [sub-qdeclarativefolderlistmodel-make_first] Error 3 > > | make[2]: Leaving directory > '/home/closx/poky/build/tmp/work/cortexa9hf-neon-poky-linux-gnueabi/qtquick1/5.10.1+gitAUTOINC+b2476dcd53-r0/build/tests/auto/declarative' > > | Makefile:45: recipe for target 'sub-declarative-make_first' failed > > | make[1]: *** [sub-declarative-make_first] Error 2 > > | make[1]: Leaving directory > '/home/closx/poky/build/tmp/work/cortexa9hf-neon-poky-linux-gnueabi/qtquick1/5.10.1+gitAUTOINC+b2476dcd53-r0/build/tests/auto' > > | Makefile:45: recipe for target 'sub-auto-make_first' failed > > | make: *** [sub-auto-make_first] Error 2 > > | ERROR: oe_runmake failed > > | WARNING: exit code 1 from a shell command. > > | ERROR: Function failed: do_compile_ptest_base (log file is located at > /home/closx/poky/build/tmp/work/cortexa9hf-neon-poky-linux-gnueabi/qtquick1/5.10.1+gitAUTOINC+b2476dcd53-r0/temp/log.do_compile_ptest_base.29566) > > ERROR: Task > > (/home/clos
[yocto] [Meta-Qt5] "Unknown Module: declarative" Error While Creating Toolchain
Hello All, I have talked to my BSP provider and they have solved the conflict files issue with an update. Now I am able to create and boot a Yocto Image with Meta-Qt5 recipes and 'dev_pkgs' in it. But still cannot create a toolchain. Nor with I guess it is trying to compile something before qtdeclarative, but these 'something' depends on qtdeclarative. My image is core image is Weston. I added the line 'inherit populate_sdk_qt5' to my core-image-weston.bb file. And tried both commands 'bitbake meta-toolchain-qt5' and 'bitbake -c populate_sdk core-image-weston'. The result is the same. I cut just the error part of my output: | cd qdeclarativefolderlistmodel/ && ( test -e Makefile || /home/closx/poky/build/tmp/work/cortexa9hf-neon-poky-linux-gnueabi/qtquick1/5.10.1+gitAUTOINC+b2476dcd53-r0/recipe-sysroot-native/usr/bin/qt5/qmake -o Makefile /home/closx/poky/build/tmp/work/cortexa9hf-neon-poky-linux-gnueabi/qtquick1/5.10.1+gitAUTOINC+b2476dcd53-r0/git/tests/auto/declarative/qdeclarativefolderlistmodel/ qdeclarativefolderlistmodel.pro ) && make -f Makefile | Project ERROR: Unknown module(s) in QT: declarative widgets | Makefile:88: recipe for target 'sub-qdeclarativecomponent-make_first' failed | make[2]: *** [sub-qdeclarativecomponent-make_first] Error 3 | make[2]: *** Waiting for unfinished jobs | Project ERROR: Unknown module(s) in QT: declarative | Project ERROR: Unknown module(s) in QT: declarative | Makefile:113: recipe for target 'sub-qdeclarativecontext-make_first' failed | make[2]: *** [sub-qdeclarativecontext-make_first] Error 3 | Project ERROR: Unknown module(s) in QT: declarative | Makefile:138: recipe for target 'sub-qdeclarativeengine-make_first' failed | make[2]: *** [sub-qdeclarativeengine-make_first] Error 3 | Makefile:63: recipe for target 'sub-parserstress-make_first' failed | make[2]: *** [sub-parserstress-make_first] Error 3 | make[2]: Entering directory '/home/closx/poky/build/tmp/work/cortexa9hf-neon-poky-linux-gnueabi/qtquick1/5.10.1+gitAUTOINC+b2476dcd53-r0/build/tests/manual/declarative' | make[2]: Nothing to be done for 'first'. | make[2]: Leaving directory '/home/closx/poky/build/tmp/work/cortexa9hf-neon-poky-linux-gnueabi/qtquick1/5.10.1+gitAUTOINC+b2476dcd53-r0/build/tests/manual/declarative' | make[1]: Leaving directory '/home/closx/poky/build/tmp/work/cortexa9hf-neon-poky-linux-gnueabi/qtquick1/5.10.1+gitAUTOINC+b2476dcd53-r0/build/tests/manual' | Project ERROR: Unknown module(s) in QT: declarative | Makefile:163: recipe for target 'sub-qdeclarativeerror-make_first' failed | make[2]: *** [sub-qdeclarativeerror-make_first] Error 3 | Project ERROR: Unknown module(s) in QT: declarative | Makefile:188: recipe for target 'sub-qdeclarativefolderlistmodel-make_first' failed | make[2]: *** [sub-qdeclarativefolderlistmodel-make_first] Error 3 | make[2]: Leaving directory '/home/closx/poky/build/tmp/work/cortexa9hf-neon-poky-linux-gnueabi/qtquick1/5.10.1+gitAUTOINC+b2476dcd53-r0/build/tests/auto/declarative' | Makefile:45: recipe for target 'sub-declarative-make_first' failed | make[1]: *** [sub-declarative-make_first] Error 2 | make[1]: Leaving directory '/home/closx/poky/build/tmp/work/cortexa9hf-neon-poky-linux-gnueabi/qtquick1/5.10.1+gitAUTOINC+b2476dcd53-r0/build/tests/auto' | Makefile:45: recipe for target 'sub-auto-make_first' failed | make: *** [sub-auto-make_first] Error 2 | ERROR: oe_runmake failed | WARNING: exit code 1 from a shell command. | ERROR: Function failed: do_compile_ptest_base (log file is located at /home/closx/poky/build/tmp/work/cortexa9hf-neon-poky-linux-gnueabi/qtquick1/5.10.1+gitAUTOINC+b2476dcd53-r0/temp/log.do_compile_ptest_base.29566) ERROR: Task (/home/closx/poky/meta-qt5/recipes-qt/qt5/qtquick1_git.bb:do_compile_ptest_base) failed with exit code '1' What do you guys think the reason of this issue may be? Any solution offers? My full output: https://paste.ee/p/PupWr#Epvqnw9FoasgQEBhIXqQ8hH7veMcRybX Another source issue again? Have a lovely day! Onur -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] How to extrac rootfs.wic in Ubuntu?
Hello Jupiter, I guess you can directly use archieve manager of ubuntu to extract it. And then you can tar the files from terminal. Or there should be another image ends with .wic (not .rootfs.wic) inside /build/tmp/deploy/image-name Onur Kimden: JH adına yocto-boun...@yoctoproject.org Gönderme tarihi: Cuma, Temmuz 5, 2019 3:23 ÖS Kime: Yocto discussion list Konu: [yocto] How to extrac rootfs.wic in Ubuntu? Hi, I know I can use dd to write wic to a device such as a SD card, but I need to extract rootfs.wic then repack it by tar.gz in Ubuntu machine. Is it possible? How can I do it. Thank you. - jupiter -- ___ 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] dev_pkgs feature caused conflict
Hello everyone, I am trying to build a toolchain for my image. Added line IMAGE_FEATURES += "dev-pkgs" to my local.conf file and rebuilt everything from zero. It gives two conflict errors. Check my error log: https://paste.ee/p/HbC5r#zh4fQsZhX9vAQEXQiwIqc7c2VkK82i2d Note: If I exclude the line IMAGE_FEATURES += "dev-pkgs" image is being builded and booted successfully. But I need it to cross compile if I am not wrong. If I include this line, following error shows up. Note2: My base image is core-image-weston. My device is SolidRun Humming Board 2 i.MX6 ARMv7 Cheers, Onur -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Json-Glib failed to build during the building of Weston image
Zoran, I have just notice that I sent the guide to you specially :D Now
sending it again including Yocto Mailing List too. It is good to contact
with you! Thanks!
HUMMING BOARD 2 (or humming board edge) i.MX6 Yocto meta-qt5 configuration
sources, (all of em with sumo branches)
git://git.yoctoproject.org/poky
https://github.com/Freescale/meta-freescale.git
https://github.com/meta-qt5/meta-qt5.git
https://github.com/openembedded/meta-openembedded.git
https://github.com/SolidRun/meta-solidrun-bsp.git
my configration files,
BBLAYERS.CONF
# POKY_BBLAYERS_CONF_VERSION is increased each time build/conf/bblayers.conf
# changes incompatibly
POKY_BBLAYERS_CONF_VERSION = "2"
BBPATH = "${TOPDIR}"
BBFILES ?= ""
BBLAYERS ?= " \
/home/closx/poky/meta \
/home/closx/poky/meta-poky \
/home/closx/poky/meta-yocto-bsp \
/home/closx/poky/meta-solidrun-bsp \
/home/closx/poky/meta-freescale \
/home/closx/poky/meta-qt5 \
/home/closx/poky/meta-openembedded/meta-oe \
"
LOCAL.CONF
MACHINE ??= "solidrun-imx6"
DISTRO ?= "poky"
PACKAGE_CLASSES ?= "package_rpm"
EXTRA_IMAGE_FEATURES ?= "debug-tweaks package-management"
USER_CLASSES ?= "buildstats image-mklibs image-prelink"
PATCHRESOLVE = "noop"
BB_DISKMON_DIRS ??= "\
STOPTASKS,${TMPDIR},1G,100K \
STOPTASKS,${DL_DIR},1G,100K \
STOPTASKS,${SSTATE_DIR},1G,100K \
STOPTASKS,/tmp,100M,100K \
ABORT,${TMPDIR},100M,1K \
ABORT,${DL_DIR},100M,1K \
ABORT,${SSTATE_DIR},100M,1K \
ABORT,/tmp,10M,1K"
PACKAGECONFIG_append_pn-qemu-native = " sdl"
PACKAGECONFIG_append_pn-nativesdk-qemu = " sdl"
CONF_VERSION = "1"
ACCEPT_FSL_EULA = "1"
LICENSE_FLAGS_WHITELIST = "commercial"
DISTRO_FEATURES_remove = "x11"
IMAGE_INSTALL_append += " qtbase"
IMAGE_INSTALL_append += " qtquickcontrols"
IMAGE_INSTALL_append += " qtquickcontrols2"
IMAGE_INSTALL_append += " qtserialport"
IMAGE_INSTALL_append += " qtmultimedia"
IMAGE_INSTALL_append += " qtserialport"
IMAGE_INSTALL_append += " qtwayland"
IMAGE_INSTALL_append += " qtserialbus"
IMAGE_INSTALL_append += " qtdeclarative"
IMAGE_INSTALL_append += " cinematicexperience"
PARALLEL_MAKE ?= "-j 6"
BB_NUMBER_THREADS ?= "6"
DL_DIR ?= "${TOPDIR}/downloads"
INHERIT += "rm_work"
IMPORTANT NOTE: If reader (you) don't know what you are doing, you should
change these lines (in local.conf) depending on how many threads can your
computer run!!!
PARALLEL_MAKE ?= "-j 6"
BB_NUMBER_THREADS ?= "6"
You can contact with me: onurese...@gmail.com
Cheers,
Onur
Zoran Stojsavljevic , 4 Tem 2019 Per, 15:43
tarihinde şunu yazdı:
> Thank you for letting me and us know. The good stuff is the following:
> if you attach yours fixed local.conf as the reference to all of us:
> [1] As referent model;
> [2] As something very valuable we also learned from you (not a joke,
> believe me)!
>
> Thank you,
> Zoran
> ___
>
> On Thu, Jul 4, 2019 at 2:38 PM Onur Eser wrote:
> >
> > Thanks everyone, the problem was a line missing in my local.conf file.
> Now understand what is wrong. My image is booting! Thanks again, have a
> good dai!
> >
> > Zoran Stojsavljevic , 4 Tem 2019 Per,
> 15:22 tarihinde şunu yazdı:
> >>
> >> > Weston is arguably superior to X11 in most respects, and for new
> >> > platforms which are not tied to a classic X server I entirely
> >> > recommend Weston over X.
> >>
> >> Never opposed that. The idea was to (as first step) do the easier and
> >> much better documented part (X11 build), and then do the next harder
> >> and more challenging step, Weston protocol.
> >>
> >> But this is only me and my thinking. ;-)
> >>
> >> Zoran
> >> ___
> >>
> >> On Thu, Jul 4, 2019 at 12:16 PM Burton, Ross
> wrote:
> >> >
> >> > On Thu, 4 Jul 2019 at 10:43, Zoran Stojsavljevic
> >> > wrote:
> >> > > Why Weston protocol? Why not classical X11 Client Server in user
> >> > > space? Which DeskTop are U using in Ur YOCTO build?
> >> >
> >> > Weston is arguably superior to X11 in most respects, and for new
> >> > platforms which are not tied to a classic X server I entirely
> >> > recommend Weston over X.
> >> >
> >> > Ross
>
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Json-Glib failed to build during the building of Weston image
Well, changed my configuration a little bit. Now, compiling again for a core weston image. I will let you know if anything goes wrong again. And thank you for giving me information about my host system, Zoran. Onur Kimden: Burton, Ross Gönderme tarihi: Perşembe, Temmuz 4, 2019 1:16 ÖS Kime: Zoran Stojsavljevic Bilgi: Onur Eser; Yocto Project Konu: Re: [yocto] Json-Glib failed to build during the building of Weston image On Thu, 4 Jul 2019 at 10:43, Zoran Stojsavljevic wrote: > Why Weston protocol? Why not classical X11 Client Server in user > space? Which DeskTop are U using in Ur YOCTO build? Weston is arguably superior to X11 in most respects, and for new platforms which are not tied to a classic X server I entirely recommend Weston over X. Ross -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Json-Glib failed to build during the building of Weston image
Hello Zoran, Using weston just for testing GPU acceleration. Then will be converted to X11. SYS info: closx@closx-pc:~$ uname -a Linux closx-pc 4.15.0-54-generic #58~16.04.1-Ubuntu SMP Mon Jun 24 13:21:41 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux Onur Zoran Stojsavljevic , 4 Tem 2019 Per, 12:43 tarihinde şunu yazdı: > Hello Onur, > > Why Weston protocol? Why not classical X11 Client Server in user > space? Which DeskTop are U using in Ur YOCTO build? > > Thank you, > Zoran > ___ > > > > On Thu, Jul 4, 2019 at 10:46 AM Onur Eser wrote: > > > > Hello Yocto Community! > > When I was trying to build core-image-weston with meta-qt5 and > meta-fsl-arm layer for my imx6 (Humming Board 2 - Armv7) board, it gave an > error on compilation of the "jason-glib". I would suprised if my image was > builded without errors. I never could have finished a Yocto or Qt-cross > building in my life... > > > > So, my error log is, > > > > Got pkgconfig variable girdir : > > Program g-ir-scanner found: YES > (/home/closx/poky/build/tmp-glibc/work/cortexa9hf-neon-oe-linux-gnueabi/json-glib/1.4.2-r0/recipe-sysroot-native/usr/bin/g-ir-scanner) > > Adding test "array". > > Adding test "boxed". > > Adding test "builder". > > Adding test "generator". > > Adding test "gvariant". > > Adding test "invalid". > > Adding test "node". > > Adding test "object". > > Adding test "parser". > > Adding test "path". > > Adding test "reader". > > Adding test "serialize-simple". > > Adding test "serialize-complex". > > Adding test "serialize-full". > > ERROR: meson failed > > WARNING: exit code 1 from a shell command. > > ERROR: Function failed: do_configure (log file is located at > /home/closx/poky/build/tmp-glibc/work/cortexa9hf-neon-oe-linux-gnueabi/json-glib/1.4.2-r0/temp/log.do_configure.1) > > > > Thanks, > > Have a good day! > > Onur > > -- > > ___ > > 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] Json-Glib failed to build during the building of Weston image
Hello Yocto Community! When I was trying to build core-image-weston with meta-qt5 and meta-fsl-arm layer for my imx6 (Humming Board 2 - Armv7) board, it gave an error on compilation of the "jason-glib". I would suprised if my image was builded without errors. I never could have finished a Yocto or Qt-cross building in my life... So, my error log is, Got pkgconfig variable girdir : Program g-ir-scanner found: YES (/home/closx/poky/build/tmp-glibc/work/cortexa9hf-neon-oe-linux-gnueabi/json-glib/1.4.2-r0/recipe-sysroot-native/usr/bin/g-ir-scanner) Adding test "array". Adding test "boxed". Adding test "builder". Adding test "generator". Adding test "gvariant". Adding test "invalid". Adding test "node". Adding test "object". Adding test "parser". Adding test "path". Adding test "reader". Adding test "serialize-simple". Adding test "serialize-complex". Adding test "serialize-full". ERROR: meson failed WARNING: exit code 1 from a shell command. ERROR: Function failed: do_configure (log file is located at /home/closx/poky/build/tmp-glibc/work/cortexa9hf-neon-oe-linux-gnueabi/json-glib/1.4.2-r0/temp/log.do_configure.1) Thanks, Have a good day! Onur -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] Anyone built Yocto with Qt5 layer for imx6?
Hello, Yocto Community! Trying to build Yocto with Qt5 layer for Humming Board 2. But I had almost a billion of errors and I am so bored. Does anyone had it built? Can you guys share some steps or configurations with me? Thanks! Onur -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] Yocto stucks when building!
Hello, I am trying to build a yocto for i.MX6, with a QT5 layer, everything is okay, but it freezes on 2666th task! When 4 tasks are running at the same time in normal, when it comes to 2666th, it is only one task and takes forever! (I made it wait for one night) Build Configuration: BB_VERSION= "1.26.0" BUILD_SYS = "x86_64-linux" NATIVELSBSTRING = "Ubuntu-16.04" TARGET_SYS= "i586-poky-linux" MACHINE = "qemux86" DISTRO= "poky" DISTRO_VERSION= "1.8.2" TUNE_FEATURES = "m32 i586" TARGET_FPU= "" meta = "fido:87631919819b6f85f23f57689cd1065c64d7fb03" meta-qt5 = "fido:90919b9d86988e7da01fa2c0a07246b5b5600a5d" meta-fsl-arm = "fido:c9f259a4bf8472dfa3ff75f1c3fcbe5e0ded7aaf" meta-solidrun-arm-imx6 = "fido:3e496c0895b0abf8d2aaca2c622246c1f9f3ed75" meta-yocto meta-yocto-bsp= "fido:87631919819b6f85f23f57689cd1065c64d7fb03" NOTE: Preparing RunQueue NOTE: Executing SetScene Tasks NOTE: Executing RunQueue Tasks Currently 1 running tasks (2666 of 5960): 0: attr-native-2.4.47-r0 do_compile (pid 3485) How to solve this? Thanks, Onur -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
