**** BEGIN LOGGING AT Fri Jan 23 02:59:59 2015 **** BEGIN LOGGING AT Fri Jan 23 08:40:48 2015 Jan 23 09:26:04 morning all Jan 23 09:49:53 good morning Jan 23 09:50:12 hi mckoan Jan 23 09:50:35 hi bluelightning Jan 23 09:57:56 I had a problem. I wrote "bitbake meta-toolchain-qt5", but it ended with annot satisfy the following dependencies for packagegroup-qt5-toolchain-target: Jan 23 09:57:56 * qtwebkit (= 5.3.2-r0.3) * qtwebkit-mkspecs * qtwebkit-qmlplugins * . So i checked for this recipes, but when i for example write "bitbake qtwebkit-dev" system says "ERROR: Nothing PROVIDES 'qtwebkit-dev'. Close matches:". Do anyobody know the solution? Jan 23 10:07:13 spaszkoPL: I'm not sure but the former error happens when a recipe claims to produce a package and doesn't - perhaps the right configuration wasn't enabled in order to build qtwebkit? Jan 23 10:07:45 spaszkoPL: I think the meta-qt5 README has documentation on how to enable appropriate configuration Jan 23 10:08:49 spaszkoPL: the second error is expected because you're passing a package name rather than a recipe name to bitbake, it only accepts recipe names (well, build-time targets, to be precise) on the command line Jan 23 10:16:17 thx, i will look into it. Moment ago, i had a blink of brilliant idea to read qt5 README and there was advice to properly configure qtbase, so maybe this is the reason. Jan 23 11:35:00 is there some fetcher which can be used to extract git bundles? Jan 23 11:36:44 ensc|w: not that I know of... is someone actually using those as a general source distribution mechanism? Jan 23 11:38:20 I am using to deliver stuff to customers; it is very nice e.g. to send changes of the linux kernel Jan 23 11:43:28 I'm having trouble developing a recipe using git to fetch sources. If I don't specify S in the recipe, bitbake will checkout files into ${WORKDIR}/git, but then attempt to build in ${WORKDIR}/${PN}-${PV}. That obviously fails, because the sources were not checked out there. If I do specify S="${WORKDIR}/git", bitbake completely skips fetch, unpack, configure etc. and happily builds empty -dev and -dbg packages with no application package. The program is based Jan 23 11:43:28 on Qt5 and I have inherit qmake5 in the recipe. Jan 23 11:45:19 gm Jan 23 11:46:29 uh? Jan 23 11:50:07 DataBeaver: you do need to specify S = "${WORKDIR}/git" for a recipe that fetches from git Jan 23 11:50:30 bluelightning: To be honest, I have no idea. Other recipes that use git seem to specify that. Jan 23 11:50:50 DataBeaver: they do yes, it is needed Jan 23 11:51:06 Right, yes, I misread your sentence as a question. Jan 23 11:51:12 So why doesn't it work then? Jan 23 11:51:15 DataBeaver: the empty packages issue is unrelated, that will be due to not having a do_install (or if there is a do_install, it isn't doing the right thing) Jan 23 11:52:48 hmm, so the qmake5 class does in fact have a do_install implementation Jan 23 11:52:57 qmake5.bbclass does have do_install and do_configure. How could the presence of the S variable cause them to not be called? Jan 23 11:53:20 setting S to the correct value is not doing that Jan 23 11:54:04 how are you determining that those tasks are being skipped? Jan 23 11:55:07 No logs for them appear in tmp-glibc/work/i586-oe-linux/helloqt/0.1-r0/temp, and the source code is not present in tmp-glibc/work/i586-oe-linux/helloqt/0.1-r0/git Jan 23 11:56:30 try bitbake -c cleansstate helloqt and then build it again Jan 23 11:58:07 That seems to have done the trick. Jan 23 11:58:54 What does -c cleansstate clean that -c clean does not? Jan 23 11:59:06 removes shared state Jan 23 11:59:11 so it gets rebuilt Jan 23 11:59:19 otherwise it is just copied Jan 23 12:02:40 And what exactly is being stored there that can cause this type of problem? Bitbake can detect changes to the .bb files, so I assume it's not that. And if it doesn't even try to fetch the source code, I would assume it's not the source code either. So what then? Jan 23 12:04:36 DataBeaver Jan 23 12:07:18 DataBeaver: I'm not sure in this specific instance to be honest, but yes it does have to do with the build system thinking nothing has changed and therefore using the cached output from a previous invocation Jan 23 12:11:25 databeaver, there is a way in which you can specify where the SRC_URI get's unpacked Jan 23 12:12:37 pompomJuice: I was under the impression that the S variable is that way. It's not then? Jan 23 12:12:50 No Jan 23 12:13:38 I am trying to find a recipy with an example, but somehow I can find one. Let me find it inside the dox Jan 23 12:13:55 S points to where the source has been unpacked, it doesn't influence where it gets unpacked Jan 23 12:14:31 I am guessing if you do something like SRC_URI="git://foo.git;source=${PN}-${PV}" Jan 23 12:14:47 note the source spesifier Jan 23 12:15:53 source or suffix Jan 23 12:15:56 I cant remember Jan 23 12:16:00 it might be suffix Jan 23 12:16:44 subdir - Places the file (or extracts its contents) into the specified subdirectory of WORKDIR. This option is useful for unusual tarballs or other archives that do not have their files already in a subdirectory within the archive. Jan 23 12:16:54 thats the one Jan 23 12:16:58 subDir Jan 23 12:17:31 therefore just add a subdir=${PN}-${PV} Jan 23 12:17:41 Right. Why isn't S automatically kept in sync with the unpack location? Jan 23 12:18:06 because at least for archives it doesn't intrinsically know where the source has been unpacked Jan 23 12:18:24 i.e. it's specified within the archive, might have more than one subdirectory, etc. Jan 23 12:18:37 you could argue it could be smarter, and I wouldn't disagree Jan 23 12:19:09 Okay, that makes sense for tarballs, but not so much for git and other version control systems. Jan 23 12:19:43 your S might be somewhere else inside the extraction Jan 23 12:19:47 that is why they are not linked Jan 23 12:19:50 At least in the vast majority of cases the root of the git repository is the correct place. Jan 23 12:20:50 And in fact tarballs and other archives could also be inspected for a single toplevel directory, which could then be used by default. Jan 23 13:17:19 JaMa, one question : When i run "bitbake meta-toolchain-qt" it provides a shell script in my deploy folder. But when i run "bitbake meta-toolchain-qt5" it's not. I hardly see any script file with sdk? Do you know what's wrong? Jan 23 13:18:31 spaszkoPL: ask otavio, I don't use sdk Jan 23 13:18:46 otavio, one question : When i run "bitbake meta-toolchain-qt" it provides a shell script in my deploy folder. But when i run "bitbake meta-toolchain-qt5" it's not. I hardly see any script file with sdk? Do you know what's wrong? Jan 23 15:55:04 http://sfconservancy.org/news/2015/jan/20/supporter-night-2015/ Jan 23 18:35:48 https://events.titanpad.com/41? Jan 23 18:39:24 * kergoth runs a little script which runs recipetool create on every python recipe and shows 1) the generated PACKAGECONFIG and 2) any detected rdeps that weren't already in the recipe **** ENDING LOGGING AT Sat Jan 24 02:59:59 2015