From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by yocto-www.yoctoproject.org (Postfix, from userid 118) id 62FEBE009A6; Thu, 8 May 2014 03:23:05 -0700 (PDT) X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on yocto-www.yoctoproject.org X-Spam-Level: * X-Spam-Status: No, score=1.3 required=5.0 tests=HTML_MESSAGE,RDNS_NONE autolearn=no version=3.3.1 X-Spam-HAM-Report: * 0.0 HTML_MESSAGE BODY: HTML included in message * 1.3 RDNS_NONE Delivered to internal network by a host with no rDNS Received: from www.dynamicdevices.co.uk (unknown [89.200.136.37]) by yocto-www.yoctoproject.org (Postfix) with ESMTP id DEAE6E006EF for ; Thu, 8 May 2014 03:23:00 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by www.dynamicdevices.co.uk (Postfix) with ESMTP id AF98C27E019; Thu, 8 May 2014 10:22:59 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at lennoab2.miniserver.com Received: from www.dynamicdevices.co.uk ([127.0.0.1]) by localhost (www.dynamicdevices.co.uk [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pNpKwLFF943b; Thu, 8 May 2014 10:22:57 +0000 (UTC) Received: from [127.0.0.1] (cpc32-live22-2-0-cust59.17-2.cable.virginm.net [82.36.253.60]) (using TLSv1 with cipher ECDHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by www.dynamicdevices.co.uk (Postfix) with ESMTPSA id CDC0327E006; Thu, 8 May 2014 10:22:56 +0000 (UTC) Message-ID: <536B5AFC.6090105@dynamicdevices.co.uk> Date: Thu, 08 May 2014 11:22:52 +0100 From: Alex J Lennon User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.5.0 MIME-Version: 1.0 To: Meenakumari Shedole References: <536903ED.1040806@dynamicdevices.co.uk> In-Reply-To: X-Enigmail-Version: 1.6 Cc: "yocto@yoctoproject.org" Subject: Re: Third Party Components Integration in Yocto X-BeenThere: yocto@yoctoproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of all things Yocto Project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 08 May 2014 10:23:05 -0000 Content-Type: multipart/alternative; boundary="------------030008040806090109010603" --------------030008040806090109010603 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Hi Meena, On 08/05/2014 11:05, Meenakumari Shedole wrote: > > Thanks Alex, > > > > Yes I installed FILES_${PN} all package folders are creating > > Tried devshell but there is no installed bb-example in > image/usr/include/...empty include folder. Bb-example is not loading > inside image/...... > > Analysed log_devshell , log_package, do_install, do_make. > OK so that's helpful. I have had similar problems myself with files that don't get installed and thus aren't packaged. In my experience it is usually to do with the path to the source file one is trying to install. i.e. So for some reason the bb-example file isn't where it should be to be copied across to the target folder in the image tree. Where does bb-example come from? Can you share the whole recipe? Can you see it where you think it should be in the devshell folder or the folder above? If you included bb-example as a file:// entry added to SRC_URI then it will be copied across to the working directory ${WORKDIR} You might want to try something like install -m 0755 ${WORKDIR}/bb-example ${D}${bindir} Alternatively if bb-example is output from a build process then it will be in the source directory ${S} In which case try install -m 0755 ${S}/bb-example ${D}${bindir} Hope this helps! Alex > > > Even I compared with other recipes folder structures it is going > right direction but only the binaries are not loading. > > > > I guess I missed something in do_install ? no proper path? > > After do_compile and make, at do_install binaries are not able to load. > > > > > > Regards > > Meena > > > > *From:*Alex J Lennon [mailto:ajlennon@dynamicdevices.co.uk] > *Sent:* Tuesday, May 06, 2014 9:17 PM > *To:* Meenakumari Shedole; yocto@yoctoproject.org; Beauchesne, Gwenole > *Subject:* Re: [yocto] Third Party Components Integration in Yocto > > > > > > On 06/05/2014 15:57, Meenakumari Shedole wrote: > > Hi, > > > > To add 3rd party components in yocto we created bb file and > modified local.conf file. > > After a yocto build, 3rd party component executing the binaries > and rpm packages but executed binaries are not loading inside the > rpm packages, rpm package is empty. > > > > Used below function in bb file. > > *do_install* () { > > install *-*d *$*{D}${bindir} > > install *-*m 0755 bb*-*example *$*{D}${bindir} > > } > > > > > Hi Meena, > > That seems a little odd as files in ${bindir} should be packaged into > the default output package as I understand it > > ref: http://www.embeddedlinux.org.cn/OEManual/recipes_packages.html > > If it were successfully installed but not packaged for any reason > (e.g. in this case not a part of FILES_${PN}) then you should see a > warning about an installed-vs-packaged file issue. > > If you enter a devshell with bitbake -c devshell recipe-foo then do > you see the installed bb-example file in within ../image/ tree? > > Have you also tried looking (from the devshell) in > ../temp/log.do_install, ../temp/log.do_xxx to see what is happening? > > Cheers, > > Alex > > > can anyone please suggest me how to move further. > > > > Regards > > Meena > > > > ::DISCLAIMER:: > ---------------------------------------------------------------------------------------------------------------------------------------------------- > > The contents of this e-mail and any attachment(s) are confidential and > intended for the named recipient(s) only. > E-mail transmission is not guaranteed to be secure or error-free as > information could be intercepted, corrupted, > lost, destroyed, arrive late or incomplete, or may contain viruses in > transmission. The e mail and its contents > (with or without referred errors) shall therefore not attach any > liability on the originator or HCL or its affiliates. > Views or opinions, if any, presented in this email are solely those of > the author and may not necessarily reflect the > views or opinions of HCL or its affiliates. Any form of reproduction, > dissemination, copying, disclosure, modification, > distribution and / or publication of this message without the prior > written consent of authorized representative of > HCL is strictly prohibited. If you have received this email in error > please delete it and notify the sender immediately. > Before opening any email and/or attachments, please check them for > viruses and other defects. > > ---------------------------------------------------------------------------------------------------------------------------------------------------- > --------------030008040806090109010603 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Hi Meena,

On 08/05/2014 11:05, Meenakumari Shedole wrote:

Thanks Alex,

 

Yes I installed  FILES_${PN} all package folders are creating

Tried devshell  but there is no installed bb-example in image/usr/include/…empty include folder. Bb-example is not loading inside image/……

Analysed  log_devshell , log_package, do_install, do_make.


OK so that's helpful. I have had similar problems myself with files that don't get installed and thus aren't packaged. In my experience it is usually to do with the path to the source file one is trying to install.

i.e. So for some reason the bb-example file isn't where it should be to be copied across to the target folder in the image tree.

Where does bb-example come from? Can you share the whole recipe? Can you see it where you think it should be in the devshell folder or the folder above?

If you included bb-example as a file:// entry added to SRC_URI then it will be copied across to the working directory ${WORKDIR}

You might want to try something like

  install -m 0755 ${WORKDIR}/bb-example ${D}${bindir}

Alternatively if bb-example is output from a build process then it will be in the source directory ${S}

In which case try

  install -m 0755 ${S}/bb-example ${D}${bindir}
 
Hope this helps!

Alex

 

Even I compared with other recipes folder structures  it is going right direction but only the binaries are not loading.

 

I guess I missed something in do_install ? no proper path?

After do_compile and make, at  do_install binaries are not able to load.

 

 

Regards

Meena

 

From: Alex J Lennon [mailto:ajlennon@dynamicdevices.co.uk]
Sent: Tuesday, May 06, 2014 9:17 PM
To: Meenakumari Shedole; yocto@yoctoproject.org; Beauchesne, Gwenole
Subject: Re: [yocto] Third Party Components Integration in Yocto

 

 

On 06/05/2014 15:57, Meenakumari Shedole wrote:

Hi,

 

To add 3rd party components in yocto we created bb file and modified local.conf file.

After a yocto build, 3rd party component executing the binaries and rpm packages but executed binaries are not loading inside the rpm packages, rpm package is empty.

 

Used below function in bb file. 

do_install () {
  install -d ${D}${bindir}
  install -m 0755 bb-example 
${D}${bindir}
}

 


Hi Meena,

That seems a little odd as files in ${bindir} should be packaged into the default output package as I understand it

ref: http://www.embeddedlinux.org.cn/OEManual/recipes_packages.html

If it were successfully installed but not packaged for any reason (e.g. in this case not a part of FILES_${PN}) then you should see a warning about an installed-vs-packaged file issue.

If you enter a devshell with bitbake -c devshell recipe-foo then do you see the installed bb-example file in within ../image/ tree?

Have you also tried looking (from the devshell) in ../temp/log.do_install, ../temp/log.do_xxx to see what is happening?

Cheers,

Alex


can anyone please suggest me how to move further.

 

Regards

Meena



::DISCLAIMER::
----------------------------------------------------------------------------------------------------------------------------------------------------

The contents of this e-mail and any attachment(s) are confidential and intended for the named recipient(s) only.
E-mail transmission is not guaranteed to be secure or error-free as information could be intercepted, corrupted,
lost, destroyed, arrive late or incomplete, or may contain viruses in transmission. The e mail and its contents
(with or without referred errors) shall therefore not attach any liability on the originator or HCL or its affiliates.
Views or opinions, if any, presented in this email are solely those of the author and may not necessarily reflect the
views or opinions of HCL or its affiliates. Any form of reproduction, dissemination, copying, disclosure, modification,
distribution and / or publication of this message without the prior written consent of authorized representative of
HCL is strictly prohibited. If you have received this email in error please delete it and notify the sender immediately.
Before opening any email and/or attachments, please check them for viruses and other defects.

----------------------------------------------------------------------------------------------------------------------------------------------------


--------------030008040806090109010603--