**** BEGIN LOGGING AT Thu Mar 28 02:59:58 2013 Mar 28 03:40:39 Hi Mar 28 03:40:47 Good morning all Mar 28 04:21:21 hello everybody.. Mar 28 04:26:10 hello Mar 28 04:29:04 ahoy Mar 28 04:29:48 i have some problem in giving depends in bb file.. can any body help me? Mar 28 04:30:20 i'm writing a .bb file for some module which is generelized for two machin archs... one is arm and one more is x86 Mar 28 04:31:11 i need Different DEPENDS for these machine archs.. but i'm unable to give the DEPENDS specific to machin archs!! Mar 28 04:31:28 any body know how to generalize my bb to work for both? Mar 28 04:42:46 Sj, the way I do it is to set up different BSPs for different machines and include any machine-specific information in a .bbappend in that machine's BSP layer Mar 28 04:44:08 ohh ok.. but one .bbappend file for evry module will you use? Mar 28 04:44:17 Sj: but you could also try something like using "DEPENDS_archname1 = ..." and "DEPENDS_archname2 = ..." Mar 28 04:44:41 Sj : use switch case for TARGET_ARCH in bb file there add depends in corresponding case Mar 28 04:45:11 is there any way to mention that in .bb file itself i mean write a condition like if ${MACHINE} is arm then DEPENDS will be different.. like that? Mar 28 04:45:55 switch case works only in fucntions? Mar 28 04:48:46 Sj: I think maybe bhaskar means something like DEPENDS = "@base_contains('TARGET_ARCH', 'machine_name', 'packge_if_true', 'package_if_fals')" but I could be wrong... Mar 28 04:49:05 bhaskar: can you link to an example in a repository showing how to do what you are talking about? Mar 28 04:53:41 Sj : is correct it will work only in functions Mar 28 05:14:02 Thanks waynr.... DEPENDS_archname works fine for me.. :-) Mar 28 07:04:59 1 Mar 28 07:07:03 1 Mar 28 07:23:27 When building with externel tool chain in work directory creating two different folders and building with same tool chain Mar 28 07:23:34 what can be the problem? Mar 28 07:23:48 did any one build qtbase? Mar 28 07:23:51 qt 5 Mar 28 07:24:48 and webkit Mar 28 07:25:44 by using externel toolchain? Mar 28 09:13:21 morning all Mar 28 09:25:41 morning silvio_, all Mar 28 09:27:15 hi bluelightning , hi all Mar 28 09:42:18 hmm, are .debug dires somehow handled outside of the standard PACKAGES logic? I get ptest .debug dirs put into the core package even when ${PN}-ptest is first in PACKAGES Mar 28 10:22:59 adding 'echo "HRW[1-9]"' in random places of configure suxx Mar 28 10:34:56 hrw: set +ex? Mar 28 10:35:19 zecke: I want info only in few places :) Mar 28 10:44:49 + - :) Mar 28 10:44:56 but yeah, I feel the pain Mar 28 10:54:39 adding debug outputs in package.bbclass is even worse. *everything* wants to rebuild... Mar 28 11:03:49 configure:10388: checking dynamic linker characteristics Mar 28 11:04:07 configure:10829: error: Link tests are not allowed after GCC_NO_EXECUTABLES. Mar 28 11:04:14 die gcc 4.8! Mar 28 11:04:15 ;D Mar 28 11:06:33 ahhh, solved it! glob.glob(file) doesn't see .debug dirs. removing /* from the FILES variable fixed by problem. **** BEGIN LOGGING AT Thu Mar 28 11:23:00 2013 **** BEGIN LOGGING AT Thu Mar 28 11:31:15 2013 Mar 28 13:58:38 XorA|gone: http://yerzmyey.i-demo.pl/yerzmyey-astral_combat2013.zip Mar 28 14:02:00 do i need to use a bbappend to build package with an older PV, I tried setting preferred version in local but now such joy. Mar 28 14:02:26 you need .bb Mar 28 14:03:11 because setting PV = "1.0" in foo_2.0.bbappend would be ugly Mar 28 14:03:34 i have the .bb just bitbake keeps building newer PV Mar 28 14:03:48 agree on the ugly Mar 28 14:03:52 .bb + P_V Mar 28 14:04:37 and .bb in layer with higher priority should win even if it has lower version Mar 28 14:08:21 my layer is set to 9 with oe-core set to 5 Mar 28 14:16:13 OWayne: does it get listed by: bitbake-layers show-overlayed Mar 28 14:24:47 bluelightning: it does, last in the list out of three versions Mar 28 14:25:33 OWayne: ok... you should be able to use PREFERRED_VERSION to select it Mar 28 14:26:25 uf. with some hacking I got gcc-runtime 4.8 built for aarch64 Mar 28 14:27:53 and does that go into local? Mar 28 14:32:40 OWayne: yes, local.conf or your custom distro config if you have one Mar 28 14:38:10 bluelightning: the format being PREFERRED_VERSION_XXX="nnn"? I did try that in local but did not work, will try a custom distro file instead Mar 28 14:41:14 I try to build my own sdk, but I have some trouble during rootfs, but I can t understand why Mar 28 14:42:11 OWayne: I suspect maybe there is already a PREFERRED_VERSION setting for that recipe Mar 28 14:42:41 OWayne: you can tell by doing bitbake -e | grep ^PREFERRED_VERSION_yourrecipe Mar 28 14:43:37 ahh there we go Mar 28 14:45:12 OWayne: at some point you probably want to have your own custom distro config anyway Mar 28 14:45:46 OWayne: however if you just want to test things temporarily you should be able to add _forcevariable to the end of the variable name in order to override the existing value Mar 28 14:47:05 thats all I am wanting is to test a rollback to see if some bugs are present Mar 28 14:47:53 I have this error but the packages are present: Mar 28 14:47:55 | * satisfy_dependencies_for: Cannot satisfy the following dependencies for task-core-standalone-btw-sdk-target-dbg: Mar 28 14:47:55 | * task-qt4-toolchain-host-nativesdk * Mar 28 14:50:45 bluelightning: thanks for tip on the forcevariable, that has done the job. Mar 28 14:53:19 OWayne: np Mar 28 14:54:03 silvio_: that happens when something claims it provides something and then no package gets created for it Mar 28 14:54:19 silvio_: e.g. because the resulting package is empty Mar 28 14:56:01 bluelightning, but I used 'ALLOW_EMPTY = "1" ' Mar 28 14:56:27 silvio_: of which? task-qt4-toolchain-host-nativesdk ? Mar 28 14:56:40 that is the one that doesn't exist Mar 28 15:11:58 bluelightning, yes, I have too comment it? Mar 28 15:12:29 to* Mar 28 15:14:56 bluelightning, I try removing 'ALLOW_EMPTY' fro both and one and other but nothing change Mar 28 15:15:30 silvio_: ALLOW_EMPTY_${PN}-dbg Mar 28 15:15:47 silvio_: ALLOW_EMPTY means that the package should be created even if there is no contents Mar 28 15:17:47 JaMa, ok i lost -dbg Mar 28 15:21:04 silvio_: I read it incorrectly -dbg is not needed Mar 28 15:21:22 silvio_: but _ is Mar 28 15:22:52 bluelightning, JaMa, Done ALLOW_EMPTY_${PN} = "1" still somethn does not work Mar 28 15:23:04 something* Mar 28 16:50:04 can SSTATETASKS only be used in global classes? E.g. when having a recipe like in http://pastebin.com/raw.php?i=Qgimajju Mar 28 16:50:21 the file tmp/foo won't be regenerated from sstate Mar 28 16:51:04 adding the _setscene task raises an exception Mar 28 16:53:01 for things that directly manipulate the sysroot, you need to let the setscene stuff call -you- Mar 28 16:53:13 * fray goes to find an example Mar 28 16:54:49 look at 'base-passwd' in meta/recipes-core Mar 28 16:55:03 SSTATEPOSTINSTFUNCS += "base_passwd_sstate_postinst" Mar 28 16:55:18 base_passwd_sstate_postinst() { Mar 28 16:55:18 if [ "${BB_CURRENTTASK}" = "populate_sysroot" -o "${BB_CURRENTTASK}" = "populate_sysroot_setscene" ] Mar 28 16:55:18 then Mar 28 16:55:18 # Staging does not copy ${sysconfdir} files into the Mar 28 16:55:19 ... Mar 28 16:55:20 } Mar 28 16:58:00 fray: how do I tell the staging in this case that ${TMPDIR}/foo belongs to the package (and shall e.g. be removed by -c clean)? Mar 28 16:58:18 you don't.. Mar 28 16:58:20 that's invalid Mar 28 16:58:31 the stuff has to be installed into one of the normal directories Mar 28 16:58:54 via do_install Mar 28 16:58:57 into ${D} Mar 28 16:59:04 If you want to write stuff in non-standard locations, your best bet is either a class or something like that... Mar 28 16:59:16 bluelightning I'm reading it as he wants to write to 'tmpdir', now WORKDIR/packaging Mar 28 16:59:18 fray: kernel deploy installs files outside of normal sysroot too Mar 28 16:59:30 they use a deployment class for that.. Mar 28 16:59:48 but the deploy.bbclass does not make more than my recipe Mar 28 16:59:48 you can do it.. but the setscene and packaging stuff only knows about things that end up in the sysroot.. if you deviate from that you have to write custom code.. Mar 28 17:01:02 I'm not sure I understand what you are trying to do.. There are ways to tag recipes and not writing stamps, so they are always run (like image recipes) Mar 28 17:01:10 maybe that is more what you need Mar 28 17:01:59 fray: I want to create a custom file (which is used from foreign scripts which do not know about target archs or so) directly under ${TMPDIR}/ Mar 28 17:02:19 ya.. so you want a way to easily place files outside of the normal bitbake control.. Mar 28 17:02:40 fray: no; I want bitbake to know about them Mar 28 17:03:03 you best approach then is to avoid the setscene, packaging, etc and just set something up to copy it there.. For the few things that I need to do that with, I use a bbclass that configures the stuff very early... and makes sure htey are in place.. if you want to do it via a recipe, you'll have to avoid the stamps or similar.. Mar 28 17:03:11 since you can't package up things outside of the sysroots and such Mar 28 17:03:43 I do not need to package these files Mar 28 17:04:22 so either write a recipe that just does what you need and don't write the stamps.. or create a class that creates/copies the files early in the build process (you can set it to do so even befor ethe recipe build has started) Mar 28 17:04:31 but I want that '-c clean' removes the file Mar 28 17:04:42 [nostamp] = "1" Mar 28 17:04:47 write your own do_clean Mar 28 17:05:06 do_my_clean() { Mar 28 17:05:07 delete my files Mar 28 17:05:07 } Mar 28 17:05:08 addtask do_my_clean before do_clean Mar 28 17:05:54 do_setup_ipkg[nostamp] = "1" Mar 28 17:05:56 does not help Mar 28 17:06:17 you need to set the nostamp on all of the items in yoru recipe, this will trigger a -rebuild- each time.. Mar 28 17:06:36 at a minimum do_package... Mar 28 17:06:42 fray: what are "all items"? Mar 28 17:06:59 all of hte tasks you need to run.. Mar 28 17:07:38 atm, it works when task is added with 'before do_build' Mar 28 17:07:53 addtask do_setup_ipkg before do_populate_sysroot after do_configure Mar 28 17:08:08 you need to set the 'before' item(s) as nostamps Mar 28 17:08:50 it can be done, you just have to figure out the right order for your tasks to run in, and what to set as nostamp -- which again will cause it to run every time the package is evaluated Mar 28 17:09:00 'er.. not evaluated, but dependend on Mar 28 17:10:20 honestly I'd suggest using sstate to your advantage rather than working around it Mar 28 17:10:21 http://www.yoctoproject.org/docs/latest/poky-ref-manual/poky-ref-manual.html#tips-and-tricks Mar 28 17:10:53 not everything is documented there but at least preservation of additional files is Mar 28 17:13:33 bluelightning the key is that this stuff is stagged outside of the sysroots.. so I don't think the sstate can even handle it.. Mar 28 17:13:47 I'd certainly advise against that behavior, but I understand why it may be needed.. Mar 28 17:14:45 bluelightning, I've started unbreaking meta-ettus Mar 28 17:15:05 I'll push something when it buiklds something that boots Mar 28 17:16:02 fray: I think you can, see usage of sstate-inputdirs and sstate-outputdirs Mar 28 17:16:45 Crofton|work: nice Mar 28 17:16:49 * mr_science waits for the other shoe to drop Mar 28 17:17:09 things are going much too smoothly so far today... Mar 28 17:25:41 have a nice Easter/weekend guys Mar 28 17:26:56 hrw: hi hrw - same to you! Mar 28 17:37:04 How can I specify LICENSE for a sofware which can be GPLv2 or GPLv3? Mar 28 17:37:55 mario-goulart: you mean you have a choice of licenses? Mar 28 17:38:10 bluelightning: yes Mar 28 17:38:24 mario-goulart: LICENSE = "GPLv2 | GPLv3" Mar 28 17:38:55 Great. Thanks, bluelightning. Mar 28 17:39:00 np Mar 28 19:24:03 that reminds me, i really want to integrate my license priority flattening thing Mar 28 19:25:10 how does one pre-configure which keyboard layout Xorg should use ? Mar 28 19:28:17 other than putting it in a xorg.conf snippet, not sure... Mar 28 19:36:54 mr_science, ok, i did create an xorg.conf snippet, it X complained that it couldnt find the corresponding .xkm-file Mar 28 19:37:48 do I need a special package for my countries keyboard layout installed ? Mar 28 21:54:20 I was told that DEFAULTTUNE should not be set by machine conf, but by the distro. but for some machines, this does not make sense, because for example only "armv7ahf" will work. some closed-source binaries are built only for this arch etc. Mar 28 21:55:02 same goes for the xorg driver. sometimes, only one machine-specific xorg driver will work, so letting the distro choose makes no sense Mar 28 21:55:03 that's not right, the machine is responsible for that Mar 28 21:55:05 the machine should select the tunes that are compatible with that machine.. (via includes) Mar 28 21:55:16 the machine should also section the defaulttune to use, but in a way it can be overriden.. Mar 28 21:55:29 the user then has the ability to set their own version in local.conf (or another .conf file as necessary) Mar 28 21:55:36 so the machine is something like: Mar 28 21:55:50 include .../tune-x86_64.conf Mar 28 21:55:57 DEFAULTTUNE ?= "core2" Mar 28 21:56:09 oh, alright Mar 28 21:56:20 DEFAULTTUNE should be set before teh include, though :) Mar 28 21:56:27 then if the user really wants "x86_64" they can do that as well.. Mar 28 21:56:30 same goes for the XSERVER variable, I take it? Mar 28 21:56:32 kergoth yes you are right Mar 28 21:57:34 hmm right now I do: Mar 28 21:57:36 require conf/machine/include/arm/arch-armv7a.inc Mar 28 21:57:44 DEFAULTTUNE="armv7ahf" Mar 28 21:57:52 so change the latter to =? and it is fine? Mar 28 21:58:00 should be ebfore the include/require Mar 28 21:58:02 and be ?= Mar 28 21:58:09 the ?= says, if not already set.. set it to .... Mar 28 21:58:09 err yes ?= Mar 28 21:58:15 this way it can be overridden by the user Mar 28 21:58:21 but the arch require is fine? Mar 28 21:58:24 yes Mar 28 21:58:59 okay,then do the same to XSERVER as well, that is, XSERVER ?= "xserver-xorg " Mar 28 21:59:18 sorry, not enough experience with that to comment Mar 28 22:00:38 XSERVER is used only in MACHINE_ARCH recipe Mar 28 22:00:46 so it's fine with = Mar 28 22:01:02 is there a list of what is used in MACHINE_ARCH recipes and what isnt? Mar 28 22:04:17 dv_: "git grep" and experience only Mar 28 23:43:00 can arguments be passed to an OE recipe function? Mar 28 23:44:44 that depends. one shell function can call another shell function that has arguments. that's about teh only case it'll work. if you need to pass args to python, use the def syntax, not function syntax Mar 28 23:46:03 so, with a shell function, inside the function, I just use $1 $2 etc.? Mar 28 23:46:25 it's just a shell function. in the emitted shell script, it's like any other shell function Mar 28 23:46:33 right, thanks Mar 28 23:46:53 also, for example, a python function calling a shell function (and vice versa), can this even work? Mar 28 23:47:22 python can use the bb.build api to exec a shell or python function/task but can't pass args to it. shell can't call python at all Mar 28 23:48:03 so the safest bet would be to define a shell function and pass arguments by using env variables Mar 29 02:00:57 hiya mwester Mar 29 02:01:00 mwester2 Mar 29 02:13:31 * nerdboy testing the camera in my living room Mar 29 02:13:52 looks nice on a 42" HD display Mar 29 02:34:49 nerdboy, what camera? Mar 29 02:35:54 the synergy thing Mar 29 02:39:49 i had to go to the dentist earlier, but apparently that doesn't get me out of running tests... Mar 29 02:40:25 doing a ~30 min recording w/audio Mar 29 02:55:27 **** ENDING LOGGING AT Fri Mar 29 02:59:59 2013