Re: [yocto] How to disable OVERRIDES temperally

On Thu, Aug 27, 2015 at 9:53 PM, Mike Looijmans wrote: > On 27-08-15 13:40, Qiang Yu wrote: > >> Hi all, >> >> I want to load kernel module ci_hdrc_imx at boot time and add a conf file >> in >> /etc/modprobe.d. I find it can be done by add >> module_c

Re: [yocto] How to disable OVERRIDES temperally

On Thu, Aug 27, 2015 at 9:36 PM, Khem Raj wrote: > On Thu, Aug 27, 2015 at 4:40 AM, Qiang Yu wrote: > > Hi all, > > > > I want to load kernel module ci_hdrc_imx at boot time and add a conf > file in > > /etc/modprobe.d. I find it can be done by add > > mod

[yocto] How to disable OVERRIDES temperally

Hi all, I want to load kernel module ci_hdrc_imx at boot time and add a conf file in /etc/modprobe.d. I find it can be done by add module_conf_ci_hdrc_imx = "my configure" But the suffix "imx" is in OVERRIDES, so I get module_conf_ci_hdrc = "my configure" How to disable the OVERRIDES temperally

Re: [yocto] [meta-sunxi] handle no soname shared library

:' + libdir + ':' + ver + '\n') fd.write('libGLESv1_CM.so:' + libdir + ':' + ver + '\n') fd.write('libGLESv2.so:' + libdir + ':' + ver + '\n') fd.close() } On Tue, Feb 17, 2015 at 10:16 PM, Qiang Yu wrote:

[yocto] [meta-sunxi] handle no soname shared library

Hi all, I'm using meta-sunxi which provides binary libegl & libgles shared library files. They all link to a libMali.so file having no SONAME field in it. So it won't register libegl & libgles to shlib2 list when do_package, and other packages linking libegl & libgles won't add runtime dependent a

Re: [yocto] How to write a recipe whose source code will generate host and target output at the same build?

}/${STAGING_DIR_TARGET} to ${PKGD} #remove host files at ${PKGD}/${STAGING_DIR_NATIVE} } On Sun, Feb 8, 2015 at 11:21 AM, Qiang Yu wrote: > Hi all, > > I'm writing a recipe for QT5 which will generate both host tools and > target lib at the same build. How can I handle

[yocto] How to write a recipe whose source code will generate host and target output at the same build?

Hi all, I'm writing a recipe for QT5 which will generate both host tools and target lib at the same build. How can I handle this situation? It doesn't fix either target or native class. Can cross class solve this problem? Can cross generate target lib package and populate both target and host sys

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

, 2015 at 7:04 PM, Otavio Salvador wrote: > On Fri, Feb 6, 2015 at 3:32 AM, Qiang Yu wrote: > ... > > 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 n

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

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 wrote: > I find some valuable info from > https://github.com/meta-qt5/meta-qt5/wiki/Building-with-OE > > Now I use $$[QT_INSTALL_PLUGINS] whic

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

PM, Qiang Yu 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 &

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

values from? Thanks, Qiang On Thu, Feb 5, 2015 at 11:04 AM, Qiang Yu 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/qtxmlpat

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

Feb 5, 2015 at 10:53 AM, Qiang Yu 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_comp

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

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/

[yocto] Can two build dir of different yocto version share the same download/ and sstate/ dir?

Hi all, I know two build dir of the same yocto version can share download/ and sstate/ dir to speed up build. But what if two build dir of different yocto version, like 1.6 and 1.7? Regards, Qiang -- ___ yocto mailing list yocto@yoctoproject.org https:

Re: [yocto] prelink & mklibs problem

, Mark Hatle wrote: > On 12/12/14, 12:57 AM, Qiang Yu wrote: > >> Hi Mark, >> >> I have used the 81bab23a4661fdaaa859325d6d3603__811ecf1849 version >> prelink to >> build my image. >> Prelink run smoothly without output like before, the image is also &

Re: [yocto] prelink & mklibs problem

prelink_image Size before prelinking 49340. Size after prelinking 49592. DEBUG: Shell function prelink_image finished Regards, Qiang On Thu, Dec 11, 2014 at 7:09 AM, Mark Hatle wrote: > On 12/9/14, 9:01 PM, Mark Hatle wrote: > >> On 12/9/14, 8:41 PM, Qiang Yu wrote: >> >

Re: [yocto] prelink & mklibs problem

obody had requested prelink support for armhf up to this point. > > Open an enhancement / bug and assign it to me. I'll do what I can to > integrate the patch officially. > > I had been waiting for the prelink upstream to merge this, but they never > bothered to, so I'

Re: [yocto] prelink & mklibs problem

ld-linux-armhf.so.3 as a dynamic linker. > You should patch the prelink source to get this done. > > HTH. > > -JC > > > > On Fri, Dec 5, 2014 at 7:41 AM, Qiang Yu wrote: > >> Hi all, >> >> I'm building a image with local.conf: >> USER_CLASSES

[yocto] prelink & mklibs problem

Hi all, I'm building a image with local.conf: USER_CLASSES ?= "buildstats image-mklibs image-prelink" but I think prelink does nothing on my image, because the MD5SUM is the same before and after the prelink stage. The mklibs stage is also strange not print anything. How to make prelink and mklib

Re: [yocto] When to create a new build directory for yocto?

all, you could clean up the tmp dir and do a rebuild any time you > like ...) > > But if you are maintaining products, you'd better separate build > directories. > > Regards, > Chen Qi > > > On 12/01/2014 03:04 PM, Qiang Yu wrote: > > What about MACHINE_FEATUR

Re: [yocto] When to create a new build directory for yocto?

What about MACHINE_FEATURES and IMAGE_FEATURES? On Mon, Dec 1, 2014 at 1:28 PM, ChenQi wrote: > On 12/01/2014 12:45 PM, Qiang Yu wrote: > > >> It's possible that you are using (or might use) different layer >> configurations for different builds. >> One build

Re: [yocto] When to create a new build directory for yocto?

> > > It's possible that you are using (or might use) different layer > configurations for different builds. > One build might have a bbappend file that another build doesn't need. > Yes, you are right. I use different conf/bblayers.conf for different SOC. But within the same SOC's different output

Re: [yocto] When to create a new build directory for yocto?

ing sstate is safe and efficient. > sstate does not contain any package. > > Regards, > Chen Qi > > > On 11/30/2014 10:28 PM, Qiang Yu wrote: > > Why share the sstate? Does it contain previously build ipk packages in > other build directories for reuse? > > Regards

Re: [yocto] When to create a new build directory for yocto?

e best way? Regards, Qiang On Sun, Nov 30, 2014 at 10:28 PM, Qiang Yu wrote: > Why share the sstate? Does it contain previously build ipk packages in > other build directories for reuse? > > Regards, > Qiang > > On Sun, Nov 30, 2014 at 4:03 PM, ChenQi wrote: > >>

Re: [yocto] When to create a new build directory for yocto?

ards, > Chen Qi > > > On 11/30/2014 12:49 PM, Qiang Yu wrote: > > Hi all, > > I'm maintaining a Yocto build system to produce these outputs: > > 1. ARM SOC 1 > 1). board 1 image > 2). board 2 image > 3). SDK for i686 > 4). SDK for x86_64 >

[yocto] When to create a new build directory for yocto?

Hi all, I'm maintaining a Yocto build system to produce these outputs: 1. ARM SOC 1 1). board 1 image 2). board 2 image 3). SDK for i686 4). SDK for x86_64 2. ARM SOC 2 1). board 3 image 2). board 4 image 3). SDK for i686 4). SDK for x86_64 Now I don't know the right way to creat