After adjust SRCREV and LICENSE.FDL the source is fetched. My bb :
/
//require qt5.inc//
//require qt5-git.inc//
//
//# There are no LGPLv3-only licensed files in this component.//
//# There are no GPLv2 licensed files in this component.//
//LICENSE = "GFDL-1.3 & BSD & (LGPL-2.1 & The-Qt-Company-Qt-LGPL-Exception-1.1 | LGPL-3.0)"//
//LIC_FILES_CHKSUM = " \//
//file://LICENSE.LGPLv3;md5=b8c75190712063cde04e1f41b6fdad98 \//
//file://LICENSE.GPLv3;md5=40f9bf30e783ddc201497165dfb32afb \//
//file://LICENSE.FDL;md5=f70ee9a6c44ae8917586fea34dff0ab5 \//
//file://LICENSE.GPLv2;md5=05832301944453ec79e40ba3c3cfceec \//
//"//
//
//DEPENDS += "qtbase qtserialport"//
//
//SRCREV = "92c979c6652d55c30ab9118d45db74d8da96fc3b"/

When i launch bitbake qtserialbus, the process build without error, but it seems there is something missing because the compile step is very fast and my neoBuild/tmp/work/cortexa9hf-vfp-neon-poky-linux-gnueabi/qtserialbus/5.5.99+5.6.0-rc+gitAUTOINC+92c979c665-r0/package/ folder is empty ! If i take the qtsensors folder, there are this folder (in package) :
usr/
    include/
    lib/
    src/

I'm looking to meta-qt5 BSP to find where i can precise to build my new recipe but didn't find anything can help. Can you explain how to proceed please ?

regards,

Le 17/03/2016 17:24, idealsim a écrit :
Like another user advise me on yocto project mailling list, i create a qtserialbus_git.bb based on qtsensor_git.bb, this is the file :

/require qt5.inc//
//require qt5-git.inc//
//
//# There are no LGPLv3-only licensed files in this component.//
//# There are no GPLv2 licensed files in this component.//
//LICENSE = "GFDL-1.3 & BSD & (LGPL-2.1 & The-Qt-Company-Qt-LGPL-Exception-1.1 | LGPL-3.0)"//
//LIC_FILES_CHKSUM = " \//
//file://LICENSE.LGPLv3;md5=b8c75190712063cde04e1f41b6fdad98 \//
//file://LICENSE.GPLv3;md5=40f9bf30e783ddc201497165dfb32afb \//
//file://LICENSE.FDL;md5=6d9f2a9af4c8b8c3c769f6cc1b6aaf7e \//
//file://LICENSE.GPLv2;md5=05832301944453ec79e40ba3c3cfceec \//
//"//
//
//DEPENDS += "qtbase qtserialport"//
//
//SRCREV = "6a16281aceedb713676e16c3074e6f7ea1e70b79"//


/I didn't change the md5 and SRCREV from qtsensor (i don't know how to obtain it !), i have this error during the build :

/WARNING: Failed to fetch URL git://github.com/qtproject/qtserialbus.git;name=qtserialbus;branch=5.6;protocol=git, attempting MIRRORS if available// //ERROR: Fetcher failure: Unable to find revision 6a16281aceedb713676e16c3074e6f7ea1e70b79 in branch 5.6 even from upstream// //ERROR: Function failed: Fetcher failure for URL: 'git://github.com/qtproject/qtserialbus.git;name=qtserialbus;branch=5.6;protocol=git'. Unable to fetch URL from any source.// //ERROR: Logfile of failure stored in: /media/modjo/data1TO/yocto/seco/udoo-community-bsp/neoBuild/tmp/work/cortexa9hf-vfp-neon-poky-linux-gnueabi/qtserialbus/5.5.99+5.6.0-rc+gitAUTOINC+6a16281ace-r0/temp/log.do_fetch.5862// //ERROR: Task 894 (/media/modjo/data1TO/yocto/seco/udoo-community-bsp/sources/meta-qt5/recipes-qt/qt5/qtserialbus_git.bb, do_fetch) failed with exit code '1'

/If someone can help please .../

regards
/
Le 15/03/2016 13:39, idealsim a écrit :
I have tried to add qtquickcontrols2 and qtserialbus to my conf but this
modules have not buildable providers.
This modules are not included to meta qt5 ? If someone can just explain
how to add this modules for yocto build (if is possible)this is very
helpful !

regards

Mickaël

Le Mon, 14 Mar 2016 21:36:24 +0100, idealsim <[email protected]> a
écrit:

Hi, we have build an image for udoo neo from meta-qt5 jansa/master-5.6 and works fine (thanks to Christian Ege ;-) ). The problem is that I'm looking for https://github.com/qtproject/qtquickcontrols2 and https://github.com/qtproject/qtserialbus. My question is, to add this modules to our build, what do we need to add to our local.conf :

     "qtquickcontrols2 \
      qtserialbus \
     "
     This is sufficient ?

regards,

Mickael.




-- 
_______________________________________________
meta-freescale mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/meta-freescale

Reply via email to