Re: [yocto] [meta-qt5] static link plugin lib path problem

2015-02-05 Thread Qiang Yu
I find some valuable info from
https://github.com/meta-qt5/meta-qt5/wiki/Building-with-OE

Now I use $$[QT_INSTALL_PLUGINS] which qmake will prefix /usr/lib/plugins
with SYSROOT.
But the Makefile has another problem when upgrade to 5.4:
LIBS  = $(SUBLIBS)
-L/opt/yocto-rel/yocto/0.1/build/linda-a20navi/tmp/work/cortexa7hf-vfp-vfpv4-neon-linda-linux-gnueabi/qtxmlpatterns/5.4.0-r0/build/lib
-lQt5XmlPatterns
-L/opt/yocto-rel/yocto/0.1/build/linda-a20navi/tmp/sysroots/a20navi/usr/lib/qt5/plugins/bearer
-lqgenericbearer -L${libdir} -lQt5Network -lQt5Core -lz -lm -ldl -lrt
-lpthread

The ${libdir} expend to /usr/lib which is cross-compile unsafe.

Another question, from the wiki I saw quit some work on the QT5 build path.
Now that QT5 is enhancing its cross-compile
support, will meta-qt5 switch to the native, less-patch and clean method?

Regards,
Qiang

On Thu, Feb 5, 2015 at 10:43 PM, Qiang Yu yuq...@gmail.com wrote:

 I find the problem:

 qt.prf:
 plugpath = $$[QT_INSTALL_PLUGINS/get]

 both $$[QT_INSTALL_PLUGINS/get] and $$[QT_INSTALL_PLUGINS/raw] equal
 /usr/lib/qt5/plugins
 but $$[QT_INSTALL_PLUGINS] equals right path.

 Now my question is
 1. why there are three var of QT_INSTALL_PLUGINS?
 2. where are their values from?

 Thanks,
 Qiang

 On Thu, Feb 5, 2015 at 11:04 AM, Qiang Yu yuq...@gmail.com wrote:

 the share link version of the same Makefile's LIBS has no plugin link:
 LIBS  = $(SUBLIBS)
 -L/opt/yocto/build/sunxi/linda-a20navi-base/tmp/work/cortexa7hf-vfp-vfpv4-neon-linda-linux-gnueabi/qtxmlpatterns/5.3.2-r0/build/lib
 -lQt5XmlPatterns -lQt5Network -lQt5Core -lpthread

 On Thu, Feb 5, 2015 at 10:53 AM, Qiang Yu yuq...@gmail.com wrote:

 Hi all,

 I use meta-qt5 for QT5 support. But I need static link the application
 so I remove the -share from configure args and add -static.

 The bitbake qtbase is fine, but bitbake qtxmlpatterns do_compile
 fail:
 | linking ../../bin/xmlpatterns
 |
 /opt/yocto-rel/yocto/0.1/build/linda-a20navi/tmp/sysroots/x86_64-linux/usr/libexec/arm-linda-linux-gnueabi/gcc/arm-linda-linux-gnueabi/4.9.1/ld:
 warning: library search path /usr/lib/qt5/plugins/bearer is unsafe for
 cross-compilation
 |
 /opt/yocto-rel/yocto/0.1/build/linda-a20navi/tmp/sysroots/x86_64-linux/usr/libexec/arm-linda-linux-gnueabi/gcc/arm-linda-linux-gnueabi/4.9.1/ld:
 cannot find -lqgenericbearer
 | collect2: error: ld returned 1 exit status
 | make[2]: *** [../../bin/xmlpatterns] Error 1
 | make[2]: Leaving directory
 `/opt/yocto-rel/yocto/0.1/build/linda-a20navi/tmp/work/cortexa7hf-vfp-vfpv4-neon-linda-linux-gnueabi/qtxmlpatterns/5.3.2-r0/build/tools/xmlpatterns'

 I find the Makefile generated by qmake for tools/xmlpatterns has the
 wrong LIBS:
 LIBS  = $(SUBLIBS)
 -L/opt/yocto-rel/yocto/0.1/build/linda-a20navi/tmp/work/cortexa7hf-vfp-vfpv4-neon-linda-linux-gnueabi/qtxmlpatterns/5.3.2-r0/build/lib
 -lQt5XmlPatterns -lQt5Network -lQt5Core -lz -lm -ldl -lrt
 -L/usr/lib/qt5/plugins/bearer -lqgenericbearer -lpthread

 It seems the plugin lib dir doesn't have a cross compile prefix. Any one
 meet this problem before or know how to fix static link plugin lib path?

 Thanks,
 Qiang




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


Re: [yocto] [meta-qt5] static link plugin lib path problem

2015-02-05 Thread Qiang Yu
The libdir problem occurs when I change $$[QT_INSTALL_PLUGINS/get] to
$$[QT_INSTALL_PLUGINS].


On Fri, Feb 6, 2015 at 1:32 PM, Qiang Yu yuq...@gmail.com wrote:

 I find some valuable info from
 https://github.com/meta-qt5/meta-qt5/wiki/Building-with-OE

 Now I use $$[QT_INSTALL_PLUGINS] which qmake will prefix /usr/lib/plugins
 with SYSROOT.
 But the Makefile has another problem when upgrade to 5.4:
 LIBS  = $(SUBLIBS)
 -L/opt/yocto-rel/yocto/0.1/build/linda-a20navi/tmp/work/cortexa7hf-vfp-vfpv4-neon-linda-linux-gnueabi/qtxmlpatterns/5.4.0-r0/build/lib
 -lQt5XmlPatterns
 -L/opt/yocto-rel/yocto/0.1/build/linda-a20navi/tmp/sysroots/a20navi/usr/lib/qt5/plugins/bearer
 -lqgenericbearer -L${libdir} -lQt5Network -lQt5Core -lz -lm -ldl -lrt
 -lpthread

 The ${libdir} expend to /usr/lib which is cross-compile unsafe.

 Another question, from the wiki I saw quit some work on the QT5 build
 path. Now that QT5 is enhancing its cross-compile
 support, will meta-qt5 switch to the native, less-patch and clean method?

 Regards,
 Qiang

 On Thu, Feb 5, 2015 at 10:43 PM, Qiang Yu yuq...@gmail.com wrote:

 I find the problem:

 qt.prf:
 plugpath = $$[QT_INSTALL_PLUGINS/get]

 both $$[QT_INSTALL_PLUGINS/get] and $$[QT_INSTALL_PLUGINS/raw] equal
 /usr/lib/qt5/plugins
 but $$[QT_INSTALL_PLUGINS] equals right path.

 Now my question is
 1. why there are three var of QT_INSTALL_PLUGINS?
 2. where are their values from?

 Thanks,
 Qiang

 On Thu, Feb 5, 2015 at 11:04 AM, Qiang Yu yuq...@gmail.com wrote:

 the share link version of the same Makefile's LIBS has no plugin link:
 LIBS  = $(SUBLIBS)
 -L/opt/yocto/build/sunxi/linda-a20navi-base/tmp/work/cortexa7hf-vfp-vfpv4-neon-linda-linux-gnueabi/qtxmlpatterns/5.3.2-r0/build/lib
 -lQt5XmlPatterns -lQt5Network -lQt5Core -lpthread

 On Thu, Feb 5, 2015 at 10:53 AM, Qiang Yu yuq...@gmail.com wrote:

 Hi all,

 I use meta-qt5 for QT5 support. But I need static link the application
 so I remove the -share from configure args and add -static.

 The bitbake qtbase is fine, but bitbake qtxmlpatterns do_compile
 fail:
 | linking ../../bin/xmlpatterns
 |
 /opt/yocto-rel/yocto/0.1/build/linda-a20navi/tmp/sysroots/x86_64-linux/usr/libexec/arm-linda-linux-gnueabi/gcc/arm-linda-linux-gnueabi/4.9.1/ld:
 warning: library search path /usr/lib/qt5/plugins/bearer is unsafe for
 cross-compilation
 |
 /opt/yocto-rel/yocto/0.1/build/linda-a20navi/tmp/sysroots/x86_64-linux/usr/libexec/arm-linda-linux-gnueabi/gcc/arm-linda-linux-gnueabi/4.9.1/ld:
 cannot find -lqgenericbearer
 | collect2: error: ld returned 1 exit status
 | make[2]: *** [../../bin/xmlpatterns] Error 1
 | make[2]: Leaving directory
 `/opt/yocto-rel/yocto/0.1/build/linda-a20navi/tmp/work/cortexa7hf-vfp-vfpv4-neon-linda-linux-gnueabi/qtxmlpatterns/5.3.2-r0/build/tools/xmlpatterns'

 I find the Makefile generated by qmake for tools/xmlpatterns has the
 wrong LIBS:
 LIBS  = $(SUBLIBS)
 -L/opt/yocto-rel/yocto/0.1/build/linda-a20navi/tmp/work/cortexa7hf-vfp-vfpv4-neon-linda-linux-gnueabi/qtxmlpatterns/5.3.2-r0/build/lib
 -lQt5XmlPatterns -lQt5Network -lQt5Core -lz -lm -ldl -lrt
 -L/usr/lib/qt5/plugins/bearer -lqgenericbearer -lpthread

 It seems the plugin lib dir doesn't have a cross compile prefix. Any
 one meet this problem before or know how to fix static link plugin lib 
 path?

 Thanks,
 Qiang





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


[yocto] http://adtrepo.yoctoproject.org Not Found

2015-02-05 Thread Gabo
Hallo,
it seems the server http://adtrepo.yoctoproject.org  does not respond
correcty (Page Not Found 404)

this is the output of adt-installer script

--2015-02-03 10:12:11--  http://adtrepo.yoctoproject.org/1.6.1
Resolving adtrepo.yoctoproject.org (adtrepo.yoctoproject.org)...
140.211.169.59
Connecting to adtrepo.yoctoproject.org
(adtrepo.yoctoproject.org)|140.211.169.59|:80...
connected.
HTTP request sent, awaiting response... 404 Not Found
2015-02-03 10:12:11 ERROR 404: Not Found.

Is there any problem?
thank you
Gabriele
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


[yocto] SDKMACHINE settings

2015-02-05 Thread Parthiban Kandasamy
entirely i am new to embedded linux. first i did bitbake of
core-image-minimal it came out very well. then again i tried sdk toolchain
development using bitbake -k meta-toolchain-qte. it gives so many error. so
could you provide details for how do i start to develop BSP for
beagleboard-XM. i am entirely confused to understand yocto online document.

-- 
thanks and regards,
parthiban
  +919790329795
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


[yocto] MIPS32r2 little endian bsp

2015-02-05 Thread Raghavendra Kakarla
Hi,

I need to create a bsp layer for my board which is having mips32r2 little 
endian processor.

I gone through the YOCTO BSP user manual bit there is no information for little 
endian.

When I create with the yoct-bsp command is taking the mips32 big endian only.

Could you please help me in resolving this issue.


Thanks and regards,

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


Re: [yocto] [meta-qt5] static link plugin lib path problem

2015-02-05 Thread Qiang Yu
I find the problem:

qt.prf:
plugpath = $$[QT_INSTALL_PLUGINS/get]

both $$[QT_INSTALL_PLUGINS/get] and $$[QT_INSTALL_PLUGINS/raw] equal
/usr/lib/qt5/plugins
but $$[QT_INSTALL_PLUGINS] equals right path.

Now my question is
1. why there are three var of QT_INSTALL_PLUGINS?
2. where are their values from?

Thanks,
Qiang

On Thu, Feb 5, 2015 at 11:04 AM, Qiang Yu yuq...@gmail.com wrote:

 the share link version of the same Makefile's LIBS has no plugin link:
 LIBS  = $(SUBLIBS)
 -L/opt/yocto/build/sunxi/linda-a20navi-base/tmp/work/cortexa7hf-vfp-vfpv4-neon-linda-linux-gnueabi/qtxmlpatterns/5.3.2-r0/build/lib
 -lQt5XmlPatterns -lQt5Network -lQt5Core -lpthread

 On Thu, Feb 5, 2015 at 10:53 AM, Qiang Yu yuq...@gmail.com wrote:

 Hi all,

 I use meta-qt5 for QT5 support. But I need static link the application so
 I remove the -share from configure args and add -static.

 The bitbake qtbase is fine, but bitbake qtxmlpatterns do_compile fail:
 | linking ../../bin/xmlpatterns
 |
 /opt/yocto-rel/yocto/0.1/build/linda-a20navi/tmp/sysroots/x86_64-linux/usr/libexec/arm-linda-linux-gnueabi/gcc/arm-linda-linux-gnueabi/4.9.1/ld:
 warning: library search path /usr/lib/qt5/plugins/bearer is unsafe for
 cross-compilation
 |
 /opt/yocto-rel/yocto/0.1/build/linda-a20navi/tmp/sysroots/x86_64-linux/usr/libexec/arm-linda-linux-gnueabi/gcc/arm-linda-linux-gnueabi/4.9.1/ld:
 cannot find -lqgenericbearer
 | collect2: error: ld returned 1 exit status
 | make[2]: *** [../../bin/xmlpatterns] Error 1
 | make[2]: Leaving directory
 `/opt/yocto-rel/yocto/0.1/build/linda-a20navi/tmp/work/cortexa7hf-vfp-vfpv4-neon-linda-linux-gnueabi/qtxmlpatterns/5.3.2-r0/build/tools/xmlpatterns'

 I find the Makefile generated by qmake for tools/xmlpatterns has the
 wrong LIBS:
 LIBS  = $(SUBLIBS)
 -L/opt/yocto-rel/yocto/0.1/build/linda-a20navi/tmp/work/cortexa7hf-vfp-vfpv4-neon-linda-linux-gnueabi/qtxmlpatterns/5.3.2-r0/build/lib
 -lQt5XmlPatterns -lQt5Network -lQt5Core -lz -lm -ldl -lrt
 -L/usr/lib/qt5/plugins/bearer -lqgenericbearer -lpthread

 It seems the plugin lib dir doesn't have a cross compile prefix. Any one
 meet this problem before or know how to fix static link plugin lib path?

 Thanks,
 Qiang



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


Re: [yocto] Confused with adding drivers to kernel via bitbake -c menuconfig

2015-02-05 Thread Alvin D.M. DIZON
Hello Kevyn,

Thanks for your help. Do I still have to run bitbake -c cleansstate after 
creating the configuration fragment? Or do I go straight to bitbake linux-imx 
or bitbake fsl-image-x11?

Thanks

From: Kevyn-Alexandre Paré [kap...@rogue-research.com]
Sent: Friday, February 06, 2015 12:58 AM
To: Alvin D.M. DIZON
Subject: Re: [yocto] Confused with adding drivers to kernel via bitbake -c 
menuconfig

Hi Alvin,

On Thu, Feb 5, 2015 at 12:43 AM, Alvin D.M. DIZON
adm.di...@pciltd.com.sg wrote:
 Hello,

 I would like to the generic USB bluetooth driver btusb to my i.MX6Q SABRE 
 SD, so that my USB Bluetooth dongle(Cambridge Silicon Radio). Upon reading 
 https://community.freescale.com/docs/DOC-100847 I enabled the Bluetooth 
 subsystem support, RFCOMM, BNEP, and HIDP, as well as the HCI USB driver. I 
 saved the .config file and copied it to the directory where my Linux recipe 
 is (linux-imx_3.10.17.bb). I then renamed my .config file into defconfig, 
 made a new folder called files and placed the defconfig in it. I also made 
 a .bbappend file that contained

I personally prefer this approach:
http://www.yoctoproject.org/docs/1.6.1/kernel-dev/kernel-dev.html#changing-the-configuration
second part with the .cfg

Doing this you can then validate it:
bitbake linux-imx -c configure -f

cat tmp/work/PATH/linux-imx/VERSION/build/.config | grep CONFIG_BT


 FILESEXTRAPATHS_prepend := ${THISDIR}/files:
 SRC_URI += file://defconfig

 I then ran bitbake -c cleansstate linux-imx, after that I ran bitbake 
 fsl-image-x11. I flashed the resulting .sdcard file to an SD card, booted up 
 my board, but found no trace of btusb. I tried doing bitbake -f -c compile 
 linux-imx and then bitbake -f -c deploy linux-imx, and copied the 
 resulting uImage to my SD card's /media/Boot folder, but still no trace of 
 btusb. I checked the tar archive for the kernel modules found in the 
 /tmp/deploy/images/imx6qsabresd folder, and found two files called 
 modules.order and modules.builtin, the btusb driver is listed in the 
 modules.builtin file, but not mentioned in the modules.order file, I have 
 also tried compiling the driver as module, and then ran the same commands as 
 listed in the said link, but could not find the module. What am I doing wrong 
 here? Any help will be will be appreciated, since I am new to Linux and the 
 Yocto Project.


Before putting it on your SD you could validate that btusb is in
tmp/work/PATH/linux-imx/VERSION/image

Or

grep btusb tmp/work/PATH/linux-imx/VERSION/temp/*

Hope it could help,

-KA

 Thanks,
 Alvin
 [PCI]

   Innovative Manufacturing Solutions. Professionally Delivered!

 The information contained in this email is confidential and is intended for 
 addressee(s) only. If you have received this email in error, please notify 
 the originator immediately. Nothing in this email shall constitute an offer 
 or acceptance leading to a legally binding contract which shall only arise 
 from a formal written agreement between yourselves and ourselves in the form 
 of a Purchase Order issued by us and accepted by you in writing. For the 
 avoidance of doubt, this email shall not be construed in any way as a formal 
 written agreement. We accept no liability for any damage arising from 
 alteration of the contents of this message by a third party or as a result of 
 any virus being passed on. Please consider your environmental responsibility 
 before printing this e-mail.
 --
 ___
 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] How to build a library for both linux and windows

2015-02-05 Thread Francisco Torres
Hello,


We use Yocto to build a Linux distribution for an embedded device. This device 
uses clutter to create the graphical user interface.

Also there is a Windows tool (Codesys) which is able to generate applications 
which will run in our device.
In order to create an app in windows which has a graphical user interface we 
need to compile clutter for Windows (so Codesys will use it and developer can 
see what the result will look like).

So, basically I need to build clutter for both Linux (done no problem here) and 
Windows (this is what I do not know how to do).

I thought that enabling mingw as sdk in yocto would be an option (I have 
managed to do that) or maybe using mingw as an external toolchain, but I am not 
sure how to do that.

I have been able to compile mingw, which I have verified that generates code 
for Windows.
But now I do not know to instruct bitbake to use this generated toolchain 
(mingw) to compile clutter for Windows.

Best Regards,
Francis.
CONFIDENTIALITY: The contents of this e-mail are confidential and intended only 
for the above addressee(s). If you are not the intended recipient, or the 
person responsible for delivering it to the intended recipient, copying or 
delivering it to anyone else or using it in any unauthorized manner is 
prohibited and may be unlawful. If you receive this e-mail by mistake, please 
notify the sender and the systems administrator at straym...@tttech.com 
immediately.
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto