**** BEGIN LOGGING AT Sat Oct 24 02:59:59 2015 Oct 24 10:37:23 in which package is qmake, if i want it to install into the fsl-image-x11? Oct 24 12:18:22 <[Sno]> JaMa: since you sent around meta-oe report and have some meta-perl recipes failing - did you take a look at https://github.com/rehsack/poky/commits/master-perl (maybe one of those help at the failures ...) or whether it can supported via meta-cpan ;) Oct 24 12:29:49 current report doesn't have any failures for perl recipes Oct 24 12:30:22 are we looking at the same report? Oct 24 13:11:13 <[Sno]> JaMa: I was looking at [OE-core] State of bitbake world, Failed tasks 2015-10-22 Oct 24 13:13:07 do you see meta-perl failure there? or are you talking about that PNBLACKLISTed one? Oct 24 13:17:09 <[Sno]> JaMa: the blacklisted ones, sorry - I just grepped over perl because checking Jeremy's patch Oct 24 14:25:04 qknight: qtbase from meta-qt5, I think. Oct 24 21:40:17 neverpanic: i've tried qtbase from meta-qt5 but no qmake in the final image then.... Oct 24 21:41:01 it's somewhere in meta-qt5, if not in qtbase then in qtbase-dev or qtbase-tools or something Oct 24 21:41:19 try grepping the layer; can't check because my machine that has it is at work Oct 24 21:43:17 Question, if I want to install a file directly from the meta-folder (file://) how do I do this? When I try install -m 0644 file://myfile -> I get file://myfile No such directory .... Oct 24 21:43:47 Christian___: there should be plenty of examples in the source for what you are doing Oct 24 21:44:12 hmm ok ... the question is how to search for it ... Oct 24 21:44:35 install and file:// will get a lot of results ... but most of them do not do this ... Oct 24 21:45:02 Christian___: true Oct 24 21:45:16 Christian___: list it in SRC_URI, install from ${WORKDIR} Oct 24 21:47:54 neverpanic: ah. maybe i should make this clear: i want qmake to be 'working' on the 'target' machine and not in a cross compiler setup Oct 24 21:48:07 * qknight also wants the cross-compiler setup but that will come later.. Oct 24 21:48:52 qknight: isn't that just a matter of adding the package that contains it to IMAGE_INSTALL? Oct 24 21:49:20 neverpanic: yes, so it would seem. i will paste my config, wait a sec Oct 24 21:51:52 neverpanic: like SRC_URI="... file://myfile" .... install -m 644 ${WORKDIR}/myfile ? Oct 24 21:52:30 neverpanic: http://paste.ubuntu.com/12931796/ i'm trying with this config Oct 24 21:53:12 qknight: as I see it, qmake should be in qtbase-tools Oct 24 21:53:26 neverpanic: the only new thing i've not evaluated but which is already in the config is the packagegroup-qt5-qtcreator-debug \ but i doubt this will bring qmake/moc when qtbase is included Oct 24 21:53:50 neverpanic: but bitbake -s does not show such a package Oct 24 21:55:15 qknight: bitbake -s shows recipe versions, not packages, right? Oct 24 21:55:29 neverpanic: yes! Oct 24 21:55:43 neverpanic: is there a way to show all packages? Oct 24 21:56:10 well, the qtbase *recipe* generates the *package* qtbase-tools in my copy of meta-qt5 (which may be outdated, though) Oct 24 21:57:00 Christian___: yes Oct 24 21:57:57 neverpanic: here it is called nativesdk-qtbase-tools maybe? Oct 24 21:58:17 neverpanic: ah, i have to informm you i'm on daisy Oct 24 21:58:21 neverpanic: so pretty old stuff Oct 24 21:58:34 qknight: I don't know. Theoretically, you should be able to grab the PACKAGES variable from each recipe, but that may include empty packages. bitbake doesn't really know if a package is empty or not until is has been built Oct 24 21:59:14 qknight: that's qmake for the SDK; I have a recipe qtbase_git.bb that should also generate qtbase-tools from the looks of it Oct 24 22:00:50 neverpanic: you are on master? or which branch? Oct 24 22:05:38 qknight: dizzy Oct 24 22:05:52 neverpanic: maybe that is the difference between the repos Oct 24 22:06:17 neverpanic: on daisy the qtbase_git.bb actually is really short with 6 lines Oct 24 22:08:22 Oh yeah, https://github.com/meta-qt5/meta-qt5/blob/daisy/recipes-qt/qt5/qtbase.inc#L202 looks like it's what you're looking for Oct 24 22:09:38 neverpanic: Thanks Oct 24 22:09:45 Hm, but dizzy doesn't have that either Oct 24 22:16:44 qknight: Hm, I think we're actually using meta-qt5 master with poky dizzy Oct 24 22:17:10 Which does not sound like a good idea to me… should have caught that in review... Oct 24 22:17:25 neverpanic: i was a bit more conservative and was using meta-qt5 dizzy with all the other dizzy userland tools Oct 24 22:27:05 neverpanic: # Disable for now, because doesn't work well with separate ${B} Oct 24 22:27:12 neverpanic: so you think master would also work? Oct 24 22:27:48 I know that we use master, possibly with additional fixes on top in a different layer, though. I also don't know the details of it, because mainly somebody else was working on this. Oct 24 22:29:06 neverpanic: https://github.com/meta-qt5/meta-qt5/blob/master/recipes-qt/qt5/qtbase_git.bb#L210 <- because here it seems to include qmake Oct 24 22:29:09 i wonder about moc Oct 24 22:30:16 neverpanic: https://youtu.be/0HaYZsc66Bk?t=131 <- that is how i feel Oct 24 22:30:44 neverpanic: but now i know that i 'have to port yet another qt5 to that yocto' ;-) Oct 24 22:31:06 A great game. Oct 24 22:40:18 does anybody know how to make two partitions boot and rootfs and how to define which files go there? like boot.scr and kernel to boot and the other stuff to rootfs partition? Oct 24 22:40:40 Christian___: you are using sdcard target? Oct 24 22:41:41 Exactly. Oct 24 22:43:09 neverpanic: thanks for all your help! Oct 24 22:43:23 neverpanic: that saved me probably a few hours of searching Oct 24 22:44:49 Christian___: maybe you can define your own target, see http://docs.openembedded.ru/image_types.html with 'custom image types' Oct 24 22:46:22 Christian___: http://git.yoctoproject.org/cgit.cgi/poky/plain/meta/classes/image_types.bbclass <- here is how it works Oct 24 22:54:44 qknight: Thanks so far ... seems a little complicated to me ... well ... lets try ... Oct 24 22:55:30 Christian___: i would first do all the steps on a shell manually and then when you know your tools, integrate it there Oct 24 23:07:56 qknight: If I see it right, probably multiubi is what I am looking for ... Oct 24 23:09:18 qknight: Now a usage example would be nice ... unfortunately the class file is the only thing in there having that command Oct 24 23:10:58 Christian___: no usage example founds Oct 24 23:12:22 qknight: me neither ... inside the tree ... only some outside yocto stuff (or maybe not, at least there is a link to yocto on the side of the page) http://free-electrons.com/blog/creating-flashing-ubi-ubifs-images/ Oct 24 23:14:32 qknight: on google "multiubi yocto" -> overwhelming 7 results for me ... Oct 24 23:18:51 Christian___: so we conclude: this must be the most popular way to install yocto Oct 24 23:19:15 Christian___: probably a userbase of 2 users, maybe it was used for a space shuttle mission ;-) Oct 24 23:19:28 maybe the one which failed... Oct 24 23:19:35 who knows? ;-) Oct 24 23:20:25 qknight: yep lol! But I am in doubt that it's so uncommon ... I have seen that method really often to have the kernel separated in a fat16 (or fat32) partition because of some old bootloaders ... well maybe that is the problem "OLD BOOTLOADERS" Oct 24 23:21:24 I read that they use that on ev3dev for the old not upgraded firmwares still out there (like on mine I guess :D ) ... the ev3 software did fail to update it inside my Windows VM Oct 24 23:22:07 Christian___: i'm just kiddin Oct 24 23:22:56 qknight: Yeah I know, I found a bit more with out "multi" Oct 24 23:28:52 here is something https://github.com/Freescale/meta-fsl-arm/blob/master/conf/machine/imx28evk.conf Oct 25 00:07:17 how come recipes can include/require files from the same directory? is the search path the current directory + BBPATH? i don't see the current directory in BBATH. Oct 25 00:07:28 *BBPATH Oct 25 00:28:35 seems to implicitly include the current directory from looking at include() in parse/parse_py/ConfHandler.py **** ENDING LOGGING AT Sun Oct 25 02:59:58 2015