[yocto] clone multiple git source repository from single recipe file
Hello All,
How can we checkout two git repo into work directory?
In SVN we do something like below:
SRC_URI = svn://
example.com/trunk/OneDirectory;module=SubDirectory1;protocol=http;user=theuser;pswd=thepassword
\
svn://
example.com/trunk/OneDirectory;module=SubDirectory2;protocol=http;user=theuser;pswd=thepassword
SRCREV_default_pn-${BPN} = svn-rev-no
But now I would like to clone two git repository, which of course have
different hash value to be checked-out. Is it possible to do that in yocto?
Best Regards,
Anooj Gopi
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] Build dts alone
Hello, After changing the kernel dts file (directly in work directory) I would like to build just the dtb file from yocto (without rebuilding entire virtual/kernel target). Is it possible to do so? Regards, Anooj -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Build dts alone
Thank you very much... devshell is really cool. It would be nice if we could mention this info some where in http://www.yoctoproject.org/docs/current/kernel-dev/kernel-dev.html On Wed, Aug 27, 2014 at 4:05 PM, Maciej Borzecki maciej.borze...@open-rnd.pl wrote: On Wednesday 27 of August 2014 15:57:40 Anooj Gopi wrote: Hello, After changing the kernel dts file (directly in work directory) I would like to build just the dtb file from yocto (without rebuilding entire virtual/kernel target). Is it possible to do so? First: bitbake -c devshell virtual/kernel Within the shell: make dtbs Or just build particular dtb if you know the name. -- Maciej Borzęcki Senior Software Engineer Open-RnD Sp. z o.o. www.open-rnd.pl, Facebook, Twitter mobile: +48 telefon, fax: +48 42 657 9079 Niniejsza wiadomość wraz z załącznikami może zawierać chronione prawem lub poufne informacje i została wysłana wyłącznie do wiadomości i użytku osób, do których została zaadresowana. Jeśli wiadomość została otrzymana przypadkowo zabrania się jej kopiowania lub rozsyłania do osób trzecich. W takim przypadku uprasza się o natychmiastowe zniszczenie wiadomości oraz poinformowanie nadawcy o zaistniałej sytuacji za pomocą wiadomości zwrotnej. Dziękujemy. This message, including any attachments hereto, may contain privileged or confidential information and is sent solely for the attention and use of the intended addressee(s). If you are not an intended addressee, you may neither use this message nor copy or deliver it to anyone. In such case, you should immediately destroy this message and kindly notify the sender by reply email. Thank you. -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] best bet for WiFi Yocto experience?
http://www.udoo.org/downloads/ has one unofficial version with yocto. On Tue, Aug 26, 2014 at 2:27 AM, Khem Raj raj.k...@gmail.com wrote: On 14-08-25 13:53:01, Rudolf Streif wrote: Hi Pete, Please provide a recommendation for a low cost, out of the box WiFi (802.11n) experience using Yocto. Are you looking for a board that has WiFi on board? The Wandboard ( http://www.wandboard.org/) or the Cubietruck ( http://www.cubietruck.com/products/cubietruck-cubieboard3-cortex-a7-dual-core-2gb-ram-8gb-flash-with-wifi-bt-1 ) have that for example. a bit expensive but well supported in OE/YP universe https://store.gumstix.com/index.php/products/526/ -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] best bet for WiFi Yocto experience?
May be this helps: http://www.wandboard.org/ On Mon, Aug 25, 2014 at 10:53 PM, Rudolf Streif rstr...@linuxfoundation.org wrote: Hi Pete, Please provide a recommendation for a low cost, out of the box WiFi (802.11n) experience using Yocto. Are you looking for a board that has WiFi on board? The Wandboard ( http://www.wandboard.org/) or the Cubietruck ( http://www.cubietruck.com/products/cubietruck-cubieboard3-cortex-a7-dual-core-2gb-ram-8gb-flash-with-wifi-bt-1) have that for example. AFAIK, Raspberry Pi doesn't come with WiFi built in. Correct, but you could use a WiFi/BT USB dongle for a couple of bucks. I would like to spend less than $100 but could stretch it. Wandboard and Cubietruck are both less than $100. Cheers, :rjs -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] How to find the bb file from package name
Hello Belen, Toaster seems promising. But unfortunately I am currently with Yocto Project 1.5 Do you see any other possibility in 1.5? Best Regards, Anooj On Tue, Jul 22, 2014 at 11:07 AM, Barros Pena, Belen belen.barros.p...@intel.com wrote: On 21/07/2014 16:39, Anooj Gopi anoojg...@gmail.com wrote: Hello All, Could some one help me to understand how we could find the bb file which generated particular package (rpm package for eg.)? (In some cases the name of the package and recipe name differ drastically) Also is there any way to list packages (rpm) generated by particular recipe (yocto package) easily. (without looking into the PACKAGES variable). Hi Anooj, One of the ways to get this information is Toaster, a web application that collects data about your builds and presents it in a web interface. More information here https://www.yoctoproject.org/documentation/toaster-manual It's only compatible with Yocto Project 1.6 though. Cheers Belén Best Regards, Anooj Gopi -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] Fwd: How to find the bb file from package name
Yes I am trying to track down the recipe from the rpm file. In my project yocto builds the rpm package nativesdk-libqt5core-dev-5.2.1-r1.i686_nativesdk.rpm (by https://github.com/meta-qt5/meta-qt5) but it is not included in my sdk sysroot image. So I would like to see how I could include this into my sdk. For that I am tracing back the recipe which generated the rpm. I tried as you said: From the source package name I can see it is from Source RPM : nativesdk-qtbase-5.2.1-r1.src.rpm, which means bb file is https://github.com/meta-qt5/meta-qt5/blob/master/recipes-qt/qt5/nativesdk-qtbase_5.3.1.bb Now this from the bb file content I can see this file provides multiple packages, (for eg. nativesdk-qtbase-tools-dbg nativesdk-qtbase-tools-dev nativesdk-qtbase-tools-staticdev nativesdk-qtbase-tool) but I still could not find where it is configured to generate the package nativesdk-libqt5core-dev-5.2.1-r1.i686_nativesdk.rpm. As Belen in his last mail, the tools like Toaster could confirm this (by listing the packages generated from a bb file), but is there any way I can do it in Yocto Project 1.5? Regards, Anooj On Tue, Jul 22, 2014 at 11:15 AM, Burton, Ross ross.bur...@intel.com wrote: On 21 July 2014 16:39, Anooj Gopi anoojg...@gmail.com wrote: Could some one help me to understand how we could find the bb file which generated particular package (rpm package for eg.)? (In some cases the name of the package and recipe name differ drastically) Also is there any way to list packages (rpm) generated by particular recipe (yocto package) easily. (without looking into the PACKAGES variable). It's probably best if you explain exactly what you want to do. If you want to work backwards from a RPM to the recipe, then binary RPMs have a Source RPM metadata field and the srpm is named after the recipe: $ rpm -qpi connman-tests-1.24-r0.15.corei7_64.rpm | grep Source Source RPM : connman-1.24-r0.15.src.rpm Ross -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Fwd: How to find the bb file from package name
Oh sorry the link I sent was wrong. The correct one is
https://github.com/meta-qt5/meta-qt5/blob/daisy/recipes-qt/qt5/nativesdk-qtbase_5.2.1.bb
Manually searching the bb/inc file did not help until this point.
Now I enabled the build history (INHERIT += buildhistory
BUILDHISTORY_FEATURES = image package sdk) and built the packages once
again. Then searched for the package name as shown below
cd build/buildhistory/packages
grep -nri nativesdk-libqt5core-dev .
./i686-nativesdk-oesdk-linux/nativesdk-qtbase/nativesdk-qtbase-tools-dev/latest:3:PKG
= nativesdk-libqt5core-dev
which shows that the yocto package is nativesdk-qtbase-tools-dev, which
is provided by nativesdk-qtbase_5.2.1.bb.
But I'm still not able to find out where in yocto PKG variable is
configured (which changes this rpm file name from the default one).
On Tue, Jul 22, 2014 at 5:50 PM, Bharath Chandra ellurubharat...@gmail.com
wrote:
Hi Anooj,
I guess you are looking at a wrong version of the recipe file, you have to
look into version number 5.2.1 and revision r1 as your package name is
suggesting but the link which you have mentioned is for 5.3.1 . Kindly,
have a look into correct version number of recipe file and if you do not
find any package name in the recipe file then you can search in *.inc*
files which are included in that recipe file.
for eg :
require qt5-${PV}.inc
You have to check in qt5-5.2.1.inc file and see if any package is included
with the name which you are searching for.
Thanks Regards,
Bharath Chandra Elluru
On Tue, Jul 22, 2014 at 6:52 AM, Anooj Gopi anoojg...@gmail.com wrote:
Yes I am trying to track down the recipe from the rpm file. In my project
yocto builds the rpm package
nativesdk-libqt5core-dev-5.2.1-r1.i686_nativesdk.rpm (by
https://github.com/meta-qt5/meta-qt5) but it is not included in my sdk
sysroot image. So I would like to see how I could include this into my sdk.
For that I am tracing back the recipe which generated the rpm.
I tried as you said:
From the source package name I can see it is from Source RPM :
nativesdk-qtbase-5.2.1-r1.src.rpm, which means bb file is
https://github.com/meta-qt5/meta-qt5/blob/master/recipes-qt/qt5/nativesdk-qtbase_5.3.1.bb
Now this from the bb file content I can see this file provides multiple
packages, (for eg. nativesdk-qtbase-tools-dbg nativesdk-qtbase-tools-dev
nativesdk-qtbase-tools-staticdev nativesdk-qtbase-tool) but I still could
not find where it is configured to generate the package
nativesdk-libqt5core-dev-5.2.1-r1.i686_nativesdk.rpm.
As Belen in his last mail, the tools like Toaster could confirm this
(by listing the packages generated from a bb file), but is there any way I
can do it in Yocto Project 1.5?
Regards,
Anooj
On Tue, Jul 22, 2014 at 11:15 AM, Burton, Ross ross.bur...@intel.com
wrote:
On 21 July 2014 16:39, Anooj Gopi anoojg...@gmail.com wrote:
Could some one help me to understand how we could find the bb file
which
generated particular package (rpm package for eg.)?
(In some cases the name of the package and recipe name differ
drastically)
Also is there any way to list packages (rpm) generated by particular
recipe
(yocto package) easily. (without looking into the PACKAGES variable).
It's probably best if you explain exactly what you want to do.
If you want to work backwards from a RPM to the recipe, then binary
RPMs have a Source RPM metadata field and the srpm is named after the
recipe:
$ rpm -qpi connman-tests-1.24-r0.15.corei7_64.rpm | grep Source
Source RPM : connman-1.24-r0.15.src.rpm
Ross
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
--
Thanks Regards,
Bharath Chandra Elluru.
Contact Number:785-979-4875.
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Fwd: How to find the bb file from package name
Hello Bharath,
This is already known to me. The confusion mainly here was because of the
name of the rpm package. From the recipe expected name was
nativesdk-qtbase-tools-dev-5.2.1-r1.i686_nativesdk.rpm but generated
package name is nativesdk-libqt5core-dev-5.2.1-r1.i686_nativesdk.rpm
which confused me.
As Mr. Burton mentioned in his last mail, this was done by
debian.bbclass, which makes our life more difficult. So I feel a tool to
track this relations is really necessary, and I guess yocto has done this
in Yocto 1.6 with toaster
https://www.yoctoproject.org/documentation/toaster-manual (I still have
to use it and see).
Regards,
Anooj
On Tue, Jul 22, 2014 at 6:37 PM, Bharath Chandra ellurubharat...@gmail.com
wrote:
Hi,
you can find it under .inc file here
https://github.com/meta-qt5/meta-qt5/blob/daisy/recipes-qt/qt5/nativesdk-qtbase.inc
PACKAGES = ${PN}-tools-dbg *${PN}-tools-dev* ${PN}-tools-staticdev
${PN}-tools
Thanks,
Bharath
On Tue, Jul 22, 2014 at 11:19 AM, Anooj Gopi anoojg...@gmail.com wrote:
Oh sorry the link I sent was wrong. The correct one is
https://github.com/meta-qt5/meta-qt5/blob/daisy/recipes-qt/qt5/nativesdk-qtbase_5.2.1.bb
Manually searching the bb/inc file did not help until this point.
Now I enabled the build history (INHERIT += buildhistory
BUILDHISTORY_FEATURES = image package sdk) and built the packages once
again. Then searched for the package name as shown below
cd build/buildhistory/packages
grep -nri nativesdk-libqt5core-dev .
./i686-nativesdk-oesdk-linux/nativesdk-qtbase/nativesdk-qtbase-tools-dev/latest:3:PKG
= nativesdk-libqt5core-dev
which shows that the yocto package is nativesdk-qtbase-tools-dev, which
is provided by nativesdk-qtbase_5.2.1.bb.
But I'm still not able to find out where in yocto PKG variable is
configured (which changes this rpm file name from the default one).
On Tue, Jul 22, 2014 at 5:50 PM, Bharath Chandra
ellurubharat...@gmail.com wrote:
Hi Anooj,
I guess you are looking at a wrong version of the recipe file, you have
to look into version number 5.2.1 and revision r1 as your package name is
suggesting but the link which you have mentioned is for 5.3.1 . Kindly,
have a look into correct version number of recipe file and if you do not
find any package name in the recipe file then you can search in *.inc*
files which are included in that recipe file.
for eg :
require qt5-${PV}.inc
You have to check in qt5-5.2.1.inc file and see if any package is included
with the name which you are searching for.
Thanks Regards,
Bharath Chandra Elluru
On Tue, Jul 22, 2014 at 6:52 AM, Anooj Gopi anoojg...@gmail.com wrote:
Yes I am trying to track down the recipe from the rpm file. In my
project yocto builds the rpm package
nativesdk-libqt5core-dev-5.2.1-r1.i686_nativesdk.rpm (by
https://github.com/meta-qt5/meta-qt5) but it is not included in my sdk
sysroot image. So I would like to see how I could include this into my sdk.
For that I am tracing back the recipe which generated the rpm.
I tried as you said:
From the source package name I can see it is from Source RPM :
nativesdk-qtbase-5.2.1-r1.src.rpm, which means bb file is
https://github.com/meta-qt5/meta-qt5/blob/master/recipes-qt/qt5/nativesdk-qtbase_5.3.1.bb
Now this from the bb file content I can see this file provides multiple
packages, (for eg. nativesdk-qtbase-tools-dbg nativesdk-qtbase-tools-dev
nativesdk-qtbase-tools-staticdev nativesdk-qtbase-tool) but I still could
not find where it is configured to generate the package
nativesdk-libqt5core-dev-5.2.1-r1.i686_nativesdk.rpm.
As Belen in his last mail, the tools like Toaster could confirm this
(by listing the packages generated from a bb file), but is there any way I
can do it in Yocto Project 1.5?
Regards,
Anooj
On Tue, Jul 22, 2014 at 11:15 AM, Burton, Ross ross.bur...@intel.com
wrote:
On 21 July 2014 16:39, Anooj Gopi anoojg...@gmail.com wrote:
Could some one help me to understand how we could find the bb file
which
generated particular package (rpm package for eg.)?
(In some cases the name of the package and recipe name differ
drastically)
Also is there any way to list packages (rpm) generated by particular
recipe
(yocto package) easily. (without looking into the PACKAGES variable).
It's probably best if you explain exactly what you want to do.
If you want to work backwards from a RPM to the recipe, then binary
RPMs have a Source RPM metadata field and the srpm is named after the
recipe:
$ rpm -qpi connman-tests-1.24-r0.15.corei7_64.rpm | grep Source
Source RPM : connman-1.24-r0.15.src.rpm
Ross
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
--
Thanks Regards,
Bharath Chandra Elluru.
Contact Number:785-979-4875.
--
Thanks Regards,
Bharath Chandra Elluru.
Contact Number:785-979-4875
Re: [yocto] Fwd: How to find the bb file from package name
This package (nativesdk-libqt5core-dev-5.2.1-r1.i686_nativesdk.rpm) is not installed in my sdk sysroot. So I need to add it to TOOLCHAIN_HOST_TASK and see if it gets installed into my sdk sysroot But it fails with below error: Error: nativesdk-qtbase-tools-dev not found in the base feeds (i686_nativesdk noarch any all ). Any idea what is the problem here? On Tue, Jul 22, 2014 at 6:26 PM, Burton, Ross ross.bur...@intel.com wrote: On 22 July 2014 17:19, Anooj Gopi anoojg...@gmail.com wrote: But I'm still not able to find out where in yocto PKG variable is configured (which changes this rpm file name from the default one). Packages containing libraries get renamed through debian.bbclass. I'm not sure why you need to know the recipe name for adding packages to a SDK though. Ross -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Fwd: How to find the bb file from package name
I would like to generalize my last question A yocto PACKAGE, yocto package generates an rpm package, rpm package with are different names due to an inherited class setting PKG http://www.yoctoproject.org/docs/current/ref-manual/ref-manual.html#var-PKG variable. When I try to add such a package to TOOLCHAIN_HOST_TASK, it throws following error during populate_sdk Error: yocto package name not found in the base feeds (i686_nativesdk noarch any all ). Does anybody have a clue how to fix this? On Tue, Jul 22, 2014 at 7:14 PM, Anooj Gopi anoojg...@gmail.com wrote: This package (nativesdk-libqt5core-dev-5.2.1-r1.i686_nativesdk.rpm) is not installed in my sdk sysroot. So I need to add it to TOOLCHAIN_HOST_TASK and see if it gets installed into my sdk sysroot But it fails with below error: Error: nativesdk-qtbase-tools-dev not found in the base feeds (i686_nativesdk noarch any all ). Any idea what is the problem here? On Tue, Jul 22, 2014 at 6:26 PM, Burton, Ross ross.bur...@intel.com wrote: On 22 July 2014 17:19, Anooj Gopi anoojg...@gmail.com wrote: But I'm still not able to find out where in yocto PKG variable is configured (which changes this rpm file name from the default one). Packages containing libraries get renamed through debian.bbclass. I'm not sure why you need to know the recipe name for adding packages to a SDK though. Ross -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] How to find the bb file from package name
Hello All, Could some one help me to understand how we could find the bb file which generated particular package (rpm package for eg.)? (In some cases the name of the package and recipe name differ drastically) Also is there any way to list packages (rpm) generated by particular recipe (yocto package) easily. (without looking into the PACKAGES variable). Best Regards, Anooj Gopi -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] Include all the native sdk packages built into sdk install script (populate_sdk)
Hello, Which is the best way to include all the native sdk packages built during the command bitbake image -c populate_sdk into the SDK sysroots generated in the SDKMACHINE (generated by sdk installation script). For eg. I can see build/tmp/deploy/rpm/i686_nativesdk/nativesdk-libqt5core-dev-5.2.1-r1.i686_nativesdk.rpm package generated in the build machine. But it is not available by default in the sysroot generated by build/tmp/deploy/sdk/ oecore-i686-cortexa15hf-vfp-neon-toolchain-oe-core.0.sh. Best Regards, Anooj Gopi -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Detailed steps involved in populate_sdk
I think TOOLCHAIN_HOST_TASK is the one I was looking for. This variable is not been used more often. Is there any better solution available to add more package to host sdk machine's sysroot? From: Anooj Gopi anooj.g...@alpine.de To: Khem Raj raj.k...@gmail.com, Cc: yocto@yoctoproject.org yocto@yoctoproject.org Date: 04.06.2014 16:24 Subject:Re: [yocto] Detailed steps involved in populate_sdk Sent by:yocto-boun...@yoctoproject.org Hello, Could you please tell me how to control/select the packages to be installed in SDK Machine. For example I have an hmi application based on qt. I can see qmake is available in ./tmp/sysroots/i686-linux/usr/bin/qt5/qmake at Build host, but it is not available in sdk machine after installing sdk. How yocto decide which host packages to be included in sdk? Thanks in advance. Regards, Anooj Gopi From:Khem Raj raj.k...@gmail.com To:Anooj Gopi anooj.g...@alpine.de, Cc:yocto@yoctoproject.org yocto@yoctoproject.org Date:03.06.2014 21:24 Subject:Re: [yocto] Detailed steps involved in populate_sdk On Tue, Jun 3, 2014 at 5:54 AM, Anooj Gopi anooj.g...@alpine.de wrote: Would there be any option for me to tell yocto to generate all the tools and use exactly the same for 'build host' as well as 'sdk host'? I don't think so Alpine Electronics RD Europe GmbH, Vor dem Lauch 14, 70567 Stuttgart, Registergericht Stuttgart, HRB 25265 Geschaeftsfuehrer: Satoshi Soma, Shuji Taguchi Working office: Vor dem Lauch 14, 70567 Stuttgart-- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto Alpine Electronics RD Europe GmbH, Vor dem Lauch 14, 70567 Stuttgart, Registergericht Stuttgart, HRB 25265 Geschaeftsfuehrer: Satoshi Soma, Shuji Taguchi Working office: Vor dem Lauch 14, 70567 Stuttgart-- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Detailed steps involved in populate_sdk
Hello, Could you please tell me how to control/select the packages to be installed in SDK Machine. For example I have an hmi application based on qt. I can see qmake is available in ./tmp/sysroots/i686-linux/usr/bin/qt5/qmake at Build host, but it is not available in sdk machine after installing sdk. How yocto decide which host packages to be included in sdk? Thanks in advance. Regards, Anooj Gopi From: Khem Raj raj.k...@gmail.com To: Anooj Gopi anooj.g...@alpine.de, Cc: yocto@yoctoproject.org yocto@yoctoproject.org Date: 03.06.2014 21:24 Subject:Re: [yocto] Detailed steps involved in populate_sdk On Tue, Jun 3, 2014 at 5:54 AM, Anooj Gopi anooj.g...@alpine.de wrote: Would there be any option for me to tell yocto to generate all the tools and use exactly the same for 'build host' as well as 'sdk host'? I don't think so Alpine Electronics RD Europe GmbH, Vor dem Lauch 14, 70567 Stuttgart, Registergericht Stuttgart, HRB 25265 Geschaeftsfuehrer: Satoshi Soma, Shuji Taguchi Working office: Vor dem Lauch 14, 70567 Stuttgart-- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Detailed steps involved in populate_sdk
Hello Raj, Thank you for your reply. May be I because I don't know about it but I am still not convinced about the on thing. When we say 'for normal build these consideration is not needed', this means the tools used in 'build host' and 'sdk hosts' are different (may be similar versions but different binary builds) right? (Even in the case when both 'build host' and 'sdk host' are exactly same for eg. basic Ubuntu 14.04 x86_64 with basic additional tools installed as suggested in yocto user manual). Would there be any option for me to tell yocto to generate all the tools and use exactly the same for 'build host' as well as 'sdk host'? Best Regards, Anooj From: Khem Raj raj.k...@gmail.com To: Anooj Gopi anooj.g...@alpine.de, Cc: yocto@yoctoproject.org Date: 01.06.2014 04:49 Subject:Re: [yocto] Detailed steps involved in populate_sdk On May 30, 2014 7:15 AM, Anooj Gopi anooj.g...@alpine.de wrote: Hello, I am new to yocto project and learning about the project step by step for one of our project. For study purpose, I'm currently using the latest yocto git clone and built bitbake core-image-minimal successfully for beaglebone. I have got all the target images to boot. At this point I assume that all the native tool chain binaries required to build the target image is already generated by yocto. Now when I try to create the SDK with the command bitbake core-image-minimal -c populate_sdk, I can see there is again native packages being configured and compiled. As per my understanding about yocto I was expecting this would have already done during bitbake core-image-minimal because all these tools are required to build the images. In my understanding populate_sdk would just install the native package deb files already created during bitbake core-image-minimal. I know there is something wrong in my understanding. Could you please explain bit in detail. sdks are supposed to run on different hosts too which we call sdkhost there fore it has to build native sdk packages to insulate itself from build host. for normal build these consideration is not needed Best Regards, Anooj Gopi Alpine Electronics RD Europe GmbH, Vor dem Lauch 14, 70567 Stuttgart, Registergericht Stuttgart, HRB 25265 Geschaeftsfuehrer: Satoshi Soma, Shuji Taguchi Working office: Vor dem Lauch 14, 70567 Stuttgart -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto Alpine Electronics RD Europe GmbH, Vor dem Lauch 14, 70567 Stuttgart, Registergericht Stuttgart, HRB 25265 Geschaeftsfuehrer: Satoshi Soma, Shuji Taguchi Working office: Vor dem Lauch 14, 70567 Stuttgart-- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] external-linaro-sdk-toolchain.bb, do_package_write_rpm) failed with exit code '1'
When try to build in Ubuntu 14.04 x86_64 machine following failure occurs.
| error: line 24: invalid tag value(^[A-Za-z0-9+._]+$) Version: Version:
'libpseudo.so'
| error: Package has no %description:
binutils-cross-canadian-arm.x86_64_nativesdk
I doubt following part of the bitbake fails due to some unknown issue
inherit cross-canadian
# ensure variable exists to avoid build error without external toolchain
TOOLCHAIN_PATH ?=
def elt_get_bfd_version(d):
import subprocess,os,bb
if os.path.exists(d.getVar('TOOLCHAIN_PATH', d,
1)+'/bin/'+d.getVar('TARGET_PREFIX', d, 1)+'as'):
return subprocess.Popen([d.getVar('TOOLCHAIN_PATH', d,
1)+'/bin/'+d.getVar('TARGET_PREFIX', d, 1)+'as', '-v', '--version'],
stderr=subprocess.STDOUT,stdout=subprocess.PIPE).communicate()[0].splitlines()[0].split()[3]
ELT_VER_BFD := ${@elt_get_bfd_version(d)}
Is any one face this issue in the past?
Alpine Electronics RD Europe GmbH, Vor dem Lauch 14, 70567 Stuttgart,
Registergericht Stuttgart, HRB 25265
Geschaeftsfuehrer: Satoshi Soma, Shuji Taguchi
Working office: Vor dem Lauch 14, 70567 Stuttgart--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] external-linaro-sdk-toolchain.bb, do_package_write_rpm) failed with exit code '1'
Please note that the same sources when built in Ubuntu 12.04 passes
without issue. Is this anything related to python version?
Note: The yocto project I am using is not the latest.
From: Anooj Gopi anooj.g...@alpine.de
To: yocto@yoctoproject.org,
Date: 03.06.2014 17:55
Subject:[yocto] external-linaro-sdk-toolchain.bb,
do_package_write_rpm) failed with exit code '1'
Sent by:yocto-boun...@yoctoproject.org
When try to build in Ubuntu 14.04 x86_64 machine following failure occurs.
| error: line 24: invalid tag value(^[A-Za-z0-9+._]+$) Version: Version:
'libpseudo.so'
| error: Package has no %description:
binutils-cross-canadian-arm.x86_64_nativesdk
I doubt following part of the bitbake fails due to some unknown issue
inherit cross-canadian
# ensure variable exists to avoid build error without external toolchain
TOOLCHAIN_PATH ?=
def elt_get_bfd_version(d):
import subprocess,os,bb
if os.path.exists(d.getVar('TOOLCHAIN_PATH', d,
1)+'/bin/'+d.getVar('TARGET_PREFIX', d, 1)+'as'):
return subprocess.Popen([d.getVar('TOOLCHAIN_PATH', d,
1)+'/bin/'+d.getVar('TARGET_PREFIX', d, 1)+'as', '-v', '--version'],
stderr=subprocess.STDOUT,stdout=subprocess.PIPE).communicate()[0].splitlines()[0].split()[3]
ELT_VER_BFD := ${@elt_get_bfd_version(d)}
Is any one face this issue in the past?
Alpine Electronics RD Europe GmbH, Vor dem Lauch 14, 70567 Stuttgart,
Registergericht Stuttgart, HRB 25265
Geschaeftsfuehrer: Satoshi Soma, Shuji Taguchi
Working office: Vor dem Lauch 14, 70567 Stuttgart--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Alpine Electronics RD Europe GmbH, Vor dem Lauch 14, 70567 Stuttgart,
Registergericht Stuttgart, HRB 25265
Geschaeftsfuehrer: Satoshi Soma, Shuji Taguchi
Working office: Vor dem Lauch 14, 70567 Stuttgart--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] Detailed steps involved in populate_sdk
Hello, I am new to yocto project and learning about the project step by step for one of our project. For study purpose, I'm currently using the latest yocto git clone and built bitbake core-image-minimal successfully for beaglebone. I have got all the target images to boot. At this point I assume that all the native tool chain binaries required to build the target image is already generated by yocto. Now when I try to create the SDK with the command bitbake core-image-minimal -c populate_sdk, I can see there is again native packages being configured and compiled. As per my understanding about yocto I was expecting this would have already done during bitbake core-image-minimal because all these tools are required to build the images. In my understanding populate_sdk would just install the native package deb files already created during bitbake core-image-minimal. I know there is something wrong in my understanding. Could you please explain bit in detail. Best Regards, Anooj Gopi Alpine Electronics RD Europe GmbH, Vor dem Lauch 14, 70567 Stuttgart, Registergericht Stuttgart, HRB 25265 Geschaeftsfuehrer: Satoshi Soma, Shuji Taguchi Working office: Vor dem Lauch 14, 70567 Stuttgart-- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
