*** evanp <evanp!~evan@134.134.137.75> has quit IRC | 18:23 | |
*** davest1 is now known as davest | 18:24 | |
*** evanp <evanp!evan@nat/intel/x-pslsjelultotsgfi> has joined #yocto | 18:25 | |
blloyd_ | thanks everyone on feedback. Hadn't considered 3 partitions so always have one root partition that isn't being updated. I had considered 2 where the running partition updated the other partition. | 18:26 |
---|---|---|
*** darknighte is now known as darknighte_afk | 18:27 | |
-yocto-ab-bot- build #280 of p1022ds is complete: Success [build successful] Build details are at http://autobuilder.yoctoproject.org:8010/builders/p1022ds/builds/280 | 18:30 | |
*** tinti_ <tinti_!~tinti@pdpc/supporter/student/tinti> has quit IRC | 18:36 | |
*** tinti_ <tinti_!~tinti@pdpc/supporter/student/tinti> has joined #yocto | 18:38 | |
*** bdholt1_ <bdholt1_!~bdholt1@62.6.189.26> has quit IRC | 18:39 | |
-yocto-ab-bot- build #275 of nightly-x86-lsb is complete: Success [build successful] Build details are at http://autobuilder.yoctoproject.org:8010/builders/nightly-x86-lsb/builds/275 | 18:59 | |
*** rcw <rcw!~rwoolley@128.224.252.2> has quit IRC | 19:01 | |
*** denisATeukrea <denisATeukrea!~GNUtoo@95.236.142.108> has quit IRC | 19:05 | |
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has quit IRC | 19:06 | |
*** RP <RP!~richard@93-97-173-237.zone5.bethere.co.uk> has joined #yocto | 19:09 | |
*** JDuke128 <JDuke128!~kadirbaso@95.65.133.227> has joined #yocto | 19:18 | |
*** sameo_ <sameo_!samuel@nat/intel/x-tfkthqmrsruhzgaz> has quit IRC | 19:21 | |
*** rcw <rcw!~rwoolley@128.224.252.2> has joined #yocto | 19:38 | |
*** smartin <smartin!~smartin@140-85-190-109.dsl.ovh.fr> has quit IRC | 19:39 | |
*** smartin <smartin!~smartin@140-85-190-109.dsl.ovh.fr> has joined #yocto | 19:43 | |
zibri | rp: i've made some changes to the bb.fetch2.URI class, that among other things, addresses the issues we discussed during ELC. but otoh perhaps the whole idea was a bit naive on my part, perhaps too much work to use urlparse. | 19:48 |
zibri | will send it to the mailing list for comments, tomorrow or so. | 19:48 |
*** sameo <sameo!~samuel@192.55.54.42> has joined #yocto | 19:56 | |
*** ccssnet <ccssnet!~ccssnet@98.216.141.157> has quit IRC | 20:01 | |
*** ccssnet <ccssnet!~ccssnet@98.216.141.157> has joined #yocto | 20:04 | |
kergoth | disabling the external toolchain causes my -natives to rebuild? | 20:17 |
kergoth | ugh | 20:17 |
* kergoth adds todo | 20:17 | |
*** tor <tor!~tor@c-ef66e655.125-1-64736c10.cust.bredbandsbolaget.se> has quit IRC | 20:22 | |
*** JimNH2 <JimNH2!~jmchale@23-25-235-113-static.hfc.comcastbusiness.net> has joined #yocto | 20:25 | |
*** JimNH <JimNH!~jmchale@23-25-235-113-static.hfc.comcastbusiness.net> has quit IRC | 20:27 | |
*** sameo <sameo!~samuel@192.55.54.42> has quit IRC | 20:42 | |
*** RP <RP!~richard@93-97-173-237.zone5.bethere.co.uk> has quit IRC | 20:43 | |
*** _Lucretia__ <_Lucretia__!~munkee@b0fd0f8f.bb.sky.com> has joined #yocto | 20:45 | |
*** _Lucretia_ <_Lucretia_!~munkee@pdpc/supporter/active/lucretia> has quit IRC | 20:46 | |
Crofton|work | ok, I've relaized I just need to install this eclipse thing | 20:47 |
Crofton|work | now, I am trying to working out how to configure the sdk plugin to use the toolcahin in /usr/local | 20:47 |
* walters reads the comments in boost.inc and laughs | 21:00 | |
*** JDuke128 <JDuke128!~kadirbaso@95.65.133.227> has quit IRC | 21:02 | |
Crofton|work | those come fro the oe-classic recipe | 21:04 |
*** tinti_ <tinti_!~tinti@pdpc/supporter/student/tinti> has quit IRC | 21:25 | |
Garibald1 | Suppose that I'm generating an SDK using bitbake -c populate_sdk <target>. How do I engineer a recipe to get included in the generated SDK? | 21:31 |
Garibald1 | I tried adding a line 'BBCLASSEXTEND = "nativesdk"' to my recipe, but the files associated with that package didn't get included in the SDK | 21:33 |
zibri | walters: haha... nice stuff :) | 21:34 |
Garibald1 | (and my package inherits 'native') | 21:37 |
Crofton|work | arg, why isn't eclipse using the cross compiler | 21:39 |
*** bluelightning <bluelightning!~paul@cpc13-lewi17-2-0-cust74.2-4.cable.virginmedia.com> has joined #yocto | 21:45 | |
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has joined #yocto | 21:45 | |
rburton | walters: lets just say there's a lot of legacy. i found myself cleaning up a fontconfig recipe that was full of crazy, introduced by my misguided and innocent self 6 years ago | 21:50 |
*** mthalmei_away is now known as mthalmei | 21:50 | |
kergoth | Garibald1: bbclassextend just makes a nativesdk version available, it won't magically also add that new recipe's packages to the sdk. populate_sdk operates based on the image target you select. you could set a variable, i forget what it's called, to adjust the package set just for the sdk, or you could just create a new image. the whole point of populate_sdk is to create an sdk corresopnding to an image, so its packages are governed primarily by that | 21:56 |
*** shoragan <shoragan!~jlu@debian/developer/shoragan> has quit IRC | 21:57 | |
*** shoragan <shoragan!~jlu@debian/developer/shoragan> has joined #yocto | 21:57 | |
Garibald1 | kergoth: so I have a target that pulls in a native package, and some of my recipes are able to successfully use the content provided by the native package, but when I do 'bitbake -c populate_sdk <that_target>' the same content doesn't appear in the generated sdk. | 21:58 |
*** mthalmei is now known as mthalmei_away | 21:58 | |
kergoth | Garibald1: and "pulls in" means what exactly? | 21:59 |
Garibald1 | kergoth: meaning the native package is installed | 21:59 |
Garibald1 | gets put in temp/sysroots/x86_64-linux | 22:00 |
Garibald1 | s/temp/tmp/ | 22:00 |
*** zenlinux_ <zenlinux_!~sgarman@c-76-105-137-48.hsd1.or.comcast.net> has quit IRC | 22:00 | |
kergoth | again, populate_sdk has meaning when run based on an image, not a random recipe | 22:01 |
Garibald1 | hum... let me see if I can explain more clealry | 22:01 |
Garibald1 | I have a recipe core-image-foo that DEPENDS on my-package-native. 'bitbake core-image-foo' generates an image, using the tools provided by 'my-package-native'; 'my-package-native' files appear in tmp/sysroots/x86_64-linux. 'bitbake -c populate_sdk core-image-foo' generates an SDK, but that SDK doesn't include the 'my-package-native' content. | 22:04 |
Garibald1 | so my application of populate_sdk is on an image | 22:06 |
Garibald1 | no? | 22:06 |
*** RP <RP!~richard@dan.rpsys.net> has joined #yocto | 22:07 | |
*** foerster <foerster!~foerster@cpe-173-89-224-99.neo.res.rr.com> has joined #yocto | 22:09 | |
Garibald1 | ah, I should also mention that 'my-package-native' content also appears in tmp/work/x86_64-linux/my-package-native-1.0-r0/sysroot-destdir/absolute/path/to/where/tmp/sysroots/x86_64-linux/is/path/to/content | 22:09 |
kergoth | DEPENDS isn't what you want. populate_sdk populates an sdk based on *what goes into the image* | 22:09 |
kergoth | the sysroots aren't relevant | 22:09 |
kergoth | e.g. if you want bash-nativesdk in populate_sdk, one way to get it is to add bash to IMAGE_INSTALL for tha timage. | 22:09 |
*** walters <walters!~walters@conductor.verbum.org> has quit IRC | 22:10 | |
kergoth | i think there's another variable to control it directly, but i can't recall it offhand, i'd suggest reading image.bbclass for details | 22:10 |
*** sameo <sameo!~samuel@192.55.54.42> has joined #yocto | 22:14 | |
Garibald1 | then I'm very confused. | 22:21 |
*** foerster <foerster!~foerster@cpe-173-89-224-99.neo.res.rr.com> has quit IRC | 22:21 | |
Garibald1 | I thought the SDK was the toolchain used on the host to build apps for the distro | 22:21 |
kergoth | nope. the sdk is the production of a *standalone* development environment and toolchain which you use to build stuff outside of yocto | 22:22 |
Garibald1 | yeah, exactly | 22:22 |
kergoth | and that environment by default is produced based on what goes into the root filesystem of an image, as mentioned earlier | 22:22 |
kergoth | (if you use populate_sdk, rather than an sdk recipe) | 22:22 |
Garibald1 | so if I have a distro for ARM, but I'm building on x86_64, I need a cross-compiler compiled for x86_64 that can compile images for arm | 22:23 |
Garibald1 | doesn't make sense that the SDK would include stuff that went into the arm distro | 22:23 |
kergoth | assuming you want to do builds outside of yocto, sure. the toolchain built internally to build recipes is separate from the sdk | 22:23 |
kergoth | no, let me try to explain again | 22:23 |
kergoth | lets say someone wants a rootfs that includes ncurses. doesn't it also makme sense they'd want to be able to link against ncurses to compile their software on the host? | 22:24 |
Garibald1 | yep | 22:24 |
kergoth | so thats what i'm talking about. | 22:24 |
kergoth | poulate_sdk populates an sdk based on what's in the rootfs for the image | 22:24 |
kergoth | only they're nativesdk versions of the recipes | 22:24 |
*** ant_home <ant_home!~andrea@host186-50-dynamic.5-87-r.retail.telecomitalia.it> has joined #yocto | 22:24 | |
kergoth | that's my understanding of it, anyway. I've only rarely built with populate_sdk personally | 22:24 |
*** foerster <foerster!~foerster@cpe-173-89-224-99.neo.res.rr.com> has joined #yocto | 22:25 | |
Garibald1 | but suppose someone wants a rootfs for a ARM processor. Doesn't it make sense they'd need a native compiler that could produce ARM binaries. Wouldn't that also go in the SDK? | 22:25 |
Garibald1 | and the distro might not even have a compiler | 22:25 |
kergoth | yes, the sdk also builds a toolchain, the packages for the toolchain are in the aforementioned separate variables to control what else goes into the sdk other than what went into the image | 22:26 |
kergoth | as i said, see image.bbclass for the exact variable names | 22:26 |
Garibald1 | ok, will do | 22:26 |
kergoth | specifically, line 8 of image.bbclass and line 10 of populate_sdk_base.bbclass | 22:27 |
Garibald1 | (WRT the libs, isn't that why you also need a copy of the rootfs? Doesn't the native tools pick up the libs from that rootfs and not from within the SDK itself?) | 22:27 |
kergoth | the former being the target packages, the latter being the host packages | 22:27 |
*** rcw <rcw!~rwoolley@128.224.252.2> has quit IRC | 22:27 | |
kergoth | ? | 22:27 |
Garibald1 | you mentioned ncurses | 22:27 |
kergoth | unless you're using montavista or something, no crosscompiler/sdk you find is going to include a rootfs | 22:27 |
kergoth | the toolchain has its own sysroot(s) | 22:27 |
Garibald1 | wouldn't the ncurses libs be on the rootfs, not on the sdk? | 22:27 |
Garibald1 | s/on the sdk/in the sdk/ | 22:28 |
kergoth | yes, it will be in the rootfs, and populate_sdk will also add it to the sdk, because the crosscompiler isn't going to magically look in a rootfs running on a remote device somewhere to find the lib | 22:28 |
Garibald1 | the sdk doesn't include the rootfs, you download it separately | 22:28 |
kergoth | the rootfs goe son the device. the crosscompiler has *zero* knowledge of it | 22:28 |
kergoth | the fact hat ncruses is in the rootfs isn't going to magically make you able to link against ncurses with the crosscompiler | 22:28 |
kergoth | libncurses would have to go into the sdk for that | 22:29 |
kergoth | which is what populate_sdk *does* | 22:29 |
Garibald1 | the rootfs goes on the device, no doubt, but you can also use a copy of that on the host for libs and the like. The Yocto ADT plugin for eclipse, for example, requires you to give it a path to a rootfs | 22:30 |
*** kmacleod <kmacleod!~ken@mail.trafficware.com> has quit IRC | 22:30 | |
kergoth | don't know or care about the adt, personally. the sdk created by populate_sdk works with or without the adt | 22:30 |
kergoth | and works without a rootfs | 22:30 |
kergoth | but regardless, the sdk creation process has multiple aspects. it builds nativesdk packages for the host, and it adds target packages to the sdk sysroot based on what goes into the image (IMAEG_INSTALL/PACKAGE_INSTALL) | 22:31 |
Garibald1 | well, I'll the variables you pointed me to | 22:31 |
kergoth | the former is likely what you want, which means you likely want to add to the variabel i pointed you to earlier in populate_sdk_base | 22:31 |
Garibald1 | yeah, agreed | 22:31 |
Garibald1 | thanks for the suggestions | 22:32 |
jstashluk | | Computing transaction...error: Can't install gst-plugins-gl-meta-0.10.3-r2@armv7a_vfp_neon: no package provides gst-plugins-gl-apps | 22:33 |
jstashluk | My do_rootfs for my image used to work, any ideas on what this means? | 22:34 |
kergoth | np | 22:36 |
*** kmacleod <kmacleod!~ken@mail.trafficware.com> has joined #yocto | 22:37 | |
*** jstashluk <jstashluk!~jstashluk@gateway/tor-sasl/jstashluk> has quit IRC | 22:41 | |
*** himamura <himamura!~himamura@p93aea0.ibrknt01.ap.so-net.ne.jp> has quit IRC | 22:43 | |
*** Bagder <Bagder!~daniel@www.haxx.se> has quit IRC | 23:05 | |
*** Bagder <Bagder!~daniel@www.haxx.se> has joined #yocto | 23:06 | |
*** eren <eren!~eren@unaffiliated/eren> has quit IRC | 23:06 | |
ftonello | i don't understand why sometimes bitbake create packages different then PACKAGES variable | 23:16 |
ftonello | why does that happens? | 23:16 |
kergoth | PACKAGES_DYNAMIC holds patterns of what packages other than PACKAGES may be created | 23:16 |
kergoth | it's used to handle creation of packages dynamically based on what comes out of the build | 23:17 |
kergoth | it's used for locales, etc | 23:17 |
ftonello | the problem is that it's not creating the ones that I want to.. is there anyway to disable that? | 23:18 |
kergoth | what do you mean by that? | 23:18 |
kergoth | every package listed in PACKAGES will be created unless no files will go into it (unless ALLOW_EMPTY_<pkg> is defined, in which case it gets created even if empty) | 23:19 |
ftonello | i have a recipe which has several libraries (pre-built) I want to create a package for each library, i do it but the deploy-<package> direcotry inside the ${WORKDIR} lists one package, which in fact it's not in PACKAGES. | 23:19 |
ftonello | another example, im appending the qt-mobility-x11 recipes | 23:20 |
ftonello | I have a PACKAGES += "${PN}-publishsubscribe" and I do a FILE_${PN}-publishsubscribe += "..." but it doesn't create it | 23:21 |
ftonello | although it creates a libqtpublishsubscribe1 package.. | 23:22 |
ftonello | which is definitely not what i want.. | 23:22 |
ftonello | is there any way to disable this dynamic package creation? | 23:22 |
ftonello | for a specific recipe | 23:22 |
kergoth | it's likely you're just encountering teh automatic package renaming based on shlibs | 23:23 |
kergoth | the same packages are emitted, just with different names. | 23:23 |
*** jbaxter <jbaxter!~jbaxter@jimbax.plus.com> has quit IRC | 23:23 | |
kergoth | see debian.bbclass | 23:23 |
Garibald1 | :q | 23:23 |
ftonello | in my case is rpm | 23:24 |
kergoth | package manager is irrelevent | 23:24 |
ftonello | kergoth: but still.. its not the case.. the contents are different.. and when I saw the do_package_write_rpm log | 23:24 |
ftonello | it looks like it changes the ${PN} | 23:24 |
ftonello | NOTE: Creating RPM package for libqtpublishsubscribe1 | 23:25 |
kergoth | first of all, its FILES_, not FILE_ | 23:25 |
ftonello | NOTE: Not creating empty RPM package for libqtpublishsubscribe-publishsubscribe | 23:25 |
kergoth | second, bitbake only emits the binary packages listed in packages and those created dynamically with do_split_packages, it doesn't pull them out of thin air | 23:25 |
kergoth | yes, that means your FILES doesn't match reality, as i said earlier, it doesn't create empty packages unless you set ALLOW_EMPTY | 23:25 |
kergoth | you just need to use bitbake -e to make sure the variables are set to what you think they are | 23:25 |
ftonello | kergoth: i know.. but when I do bitbake -e and I check the variables, they are correct | 23:26 |
kergoth | well, bitbake isn't going to emit an empty package. fix your do_install, or fix your FILES variables. | 23:26 |
kergoth | this is a lot simpler than you seem to think | 23:26 |
*** munch <munch!~mark@c-67-184-166-69.hsd1.il.comcast.net> has quit IRC | 23:26 | |
ftonello | ok.. i will make sure of something | 23:27 |
kergoth | whenever i see something seemingly inexplicable happening, it's almost always a mismatch between my expectations and reality, and bitbake -e and other similar mechanimss are invaluable for checking those assumptions | 23:27 |
*** tinti <tinti!~tinti@pdpc/supporter/student/tinti> has quit IRC | 23:28 | |
*** tinti <tinti!~tinti@pdpc/supporter/student/tinti> has joined #yocto | 23:29 | |
*** kmacleod <kmacleod!~ken@mail.trafficware.com> has quit IRC | 23:30 | |
kergoth | if you're really curious about what's going on, you can always read the tasks in the bbclasses and see exactly what's going on. its easier if you know python, but you'll probably get the gist even without that | 23:30 |
ftonello | kergoth: this is what is inside image/ http://paste.kde.org/689966/ | 23:32 |
*** kmacleod <kmacleod!~ken@mail.trafficware.com> has joined #yocto | 23:32 | |
kergoth | yeah, that's what do_install puts there. what about it? | 23:32 |
ftonello | i wnat to show you that the paths are correct | 23:33 |
kergoth | again, debian.bbclass renames packages based on the shared library the package includes. if your package includes libqtpublishsubscribe, then yes, it will rename it to libqtpublishsubscribe1. | 23:33 |
ftonello | the packages shouldn't be empty | 23:33 |
kergoth | i just told you, either do_install is wrong *OR* the fiels variables are wrong | 23:33 |
kergoth | i didn't say i was going to figure out which wa sthe case for you | 23:33 |
ftonello | bitbake -e http://paste.kde.org/689972/ | 23:34 |
ftonello | im not asking that | 23:34 |
ftonello | im just trying to understand why this is not working | 23:34 |
*** michael_e_brown <michael_e_brown!~michaeleb@143.166.116.80> has quit IRC | 23:40 | |
evanp | ftonello: the libqtpublishsubscribe1 thing sounds like the debian package rename hook | 23:49 |
evanp | ftonello: meaning, it _is_ your ${PN}-publishsubscribe package | 23:50 |
evanp | ftonello: but the hook changed the file name | 23:50 |
ftonello | evanp: I tink the hook changed the ${PN} package file name | 23:50 |
ftonello | see the from the do_package_write_rpm | 23:50 |
evanp | ftonello: yes, exactly | 23:50 |
ftonello | NOTE: Not creating empty RPM package for libqtpublishsubscribe-publishsubscribe | 23:51 |
ftonello | but thats the thing | 23:51 |
ftonello | I don't want that behavior.. is there anyway to disable that? | 23:51 |
evanp | you mean you want it to create an empty package? like kergoth said, ALLOW_EMPTY | 23:53 |
evanp | or do you mean you want your package to be named libqt-publishsubscribe? you'll have to figure out a way to change the debian rename hook to do that. disabling it globally'll probably break other stuff. | 23:54 |
Generated by irclog2html.py 2.11.0 by Marius Gedminas - find it at mg.pov.lt!