**** BEGIN LOGGING AT Wed Sep 11 02:59:59 2013 Sep 11 03:05:40 pev: i have submitted documentation patches against git://git.yoctoproject.org/yocto-docs in the past Sep 11 03:06:09 successfully :-) Sep 11 03:54:41 jefro tull Sep 11 06:52:13 Good morning Sep 11 06:53:17 JaMa, do you have a second? I am having some problems writting a bbappend file to add some extra configs flags to qtbase_5.1.... Sep 11 06:54:18 i have created a file called qtbase_5.1.0.bbappend in my own layer Sep 11 06:54:28 the file just contains one line: EXTRA_OECONF += "-qt-xcb -opengl" Sep 11 06:55:29 however this doesn't seem to make it to the actual configure line when building qtbase Sep 11 06:56:05 melonipoika_: I think you want to look at the PACKAGECONFIG options in qtbase.inc Sep 11 06:57:12 thanks erbo Sep 11 06:57:43 melonipoika_: remember that since qtbase.inc uses ??= when assigning PACKAGECONFIG you can't just do PACKAGECONFIG += "foo" in your bbappend Sep 11 06:58:38 so you might want to copy the default PACKAGECONFIG setup from qtbase.inc, change ??= to just = and add your own options Sep 11 06:59:22 ok, thanks. Will try that Sep 11 07:06:15 where can i find the do_configure log to see whether my options were taken? Sep 11 07:09:39 melonipoika_: tmp/work/*/qtbase/*/temp/log.do_configure Sep 11 07:11:23 hmm, i don't seem to have a do_configure log there Sep 11 07:11:50 i have log.do_package_setscne, package write, populate_sysroot... Sep 11 07:12:26 i did bitbake -c clean qtbase after modifying my bbappend Sep 11 07:12:36 and before bilding again Sep 11 07:34:31 my bad... i had the .bbappend in the wrong directory :-( Sep 11 07:36:09 now I got a new error, but this time bitbake was able to find my append file :-) Sep 11 07:37:54 melonipoika_: you might know about this already, but I'll mention it anyway. "bitbake-layers show-appends" will show all found bbappend, so one can just grep that output to make sure a newly created bbappend is found Sep 11 07:41:24 thanks erbo for the tip :-) I didn't know it Sep 11 07:41:33 i am quite new to yocto Sep 11 07:42:42 i actually believe that manually adding -opengl to my configure options is a hack, it should be added automatically since I have "gl" in my DISTRO options Sep 11 07:43:15 but it doesn't seem to work, so I decided to move on and fix this properly when I understand better what I am doing *:D Sep 11 07:45:47 :) Sep 11 07:46:03 I don't really know how to read this line Sep 11 07:46:06 PACKAGECONFIG_GL ?= "${@base_contains('DISTRO_FEATURES', 'opengl', 'gl', '', d)}" Sep 11 07:47:05 melonipoika_: that sets PACKAGECONFIG_GL to "gl" if opengl is found in DISTRO_FEATURE, if not PACKAGECONFIG_GL is set to "" Sep 11 07:47:26 thanks Sep 11 07:56:53 what about the line PACKAGECONFIG[gl] = "-opengl desktop -no-eglfs,,virtual/libgl" Sep 11 07:56:53 ? Sep 11 07:59:52 melonipoika_: that adds a PACKAGECONFIG option. so if PACKAGECONFIG contains "gl" at buildtime it will add "-opengl desktop" to configure flags and "virtual/libgl" do DEPENDS, else "". Sep 11 08:00:53 cool! Sep 11 08:00:57 many thanks :-) Sep 11 08:01:35 there's probably a nice document somewhere describing PACKAGECONFIG, it's really quite neat Sep 11 08:02:15 melonipoika_: http://www.yoctoproject.org/docs/1.4/poky-ref-manual/poky-ref-manual.html, search for PACKAGECONFIG Sep 11 08:50:13 melonipoika_: also use bitbake -e to see what is or isn't in EXTRA_OECONF, PACKAGECONFIG_append should work correctly Sep 11 08:53:36 morning all Sep 11 09:11:54 layers.openembedded.org is just awesome Sep 11 09:11:56 thanks! Sep 11 09:22:45 thanks JaMa! Sep 11 09:23:15 Now it seems to work fine, I am building my image from scratch to be sure :-) Sep 11 09:23:55 btw, is there already an option to add -qt-xcb? Or should I do that on my bbpapend? Sep 11 09:27:37 eren: you're welcome :) Sep 11 09:27:47 eren: if you have any suggestions for improvements I'd be happy to hear them Sep 11 09:28:10 bluelightning: well, some css change would be ok. I would love to see my cursor directly into the search input when the page is loaded Sep 11 09:28:17 s/css/javascript Sep 11 09:28:44 bluelightning: all the layers in layers.openembedded.org are fully yocto-compliant? Sep 11 09:29:28 n01: in terms of the Yocto Project Compatible status, no Sep 11 09:30:01 and in terms of "just working" ? :) Sep 11 09:30:25 you shouldn't have any problems, and if you do, contact the maintainer :) Sep 11 09:30:47 :D ok Sep 11 09:31:12 eren: right, we do that on other pages; the reason I haven't on the layers page is it comes up with a scrollable list to begin with and I assume people want to be able to scroll the list initially rather than type, but that might be a faulty assumption Sep 11 10:14:05 good morning, is there a way to set a preffered version in the RDEPENDS variable? because i am trying to setup a packagegroup with packages that have to have a preferred version Sep 11 10:14:35 maybe that is the wrong way to do so ... i am open to suggestions Sep 11 10:31:35 wfailla: i have seen something like this in some of our recipes: Sep 11 10:31:36 RDEPENDS_${PN} = "foobar (= ${EXTENDPKGV}) Sep 11 10:31:58 that 'stuff' gets added in the package , include the version. i suspect you can use any 'string' for the version. Sep 11 10:36:07 yep, as long as the package manager can enforce the version requirement (and we do some basic checks on the string provided before that) it will work Sep 11 10:38:36 so some thing like this should work RDEPENDS_${PN} = "test_pkg (= 0.1.1)" Sep 11 10:40:45 the question is rather opkg has this feature Sep 11 10:41:15 no it dose not work Sep 11 10:43:26 i guess to use this i need to use .deb or .rpm Sep 11 10:44:00 what 'does not work'? Sep 11 10:44:39 it will still build the newer version instead of the specified version Sep 11 10:45:12 well, that's different then. Sep 11 10:45:34 RDEPENDS is for runtime installation of pkgs. Sep 11 10:46:43 wfailla: if you haven't already you should also specify PREFERRED_VERSION_test_pkg = "0.1.1" Sep 11 10:46:48 if you want a build time dependency, you can set PREFERED_VERSION_pn-test_pkg in a conf file. but that would apply for all the build. you can't have 2 version for the same recipe Sep 11 10:47:18 oops, there is no _pn indeed. Sep 11 10:47:23 I wanted to give a try to meta-micro, but I keep getting "Your version of bblayers.conf was generated from an older/newer ...." but this is not true Sep 11 10:47:24 ndec: right, PREFERRED_VERSION_test-pkg (assuming it was called test-pkg, since test_pkg would not be a legal package name) Sep 11 10:47:55 everything seems ok, distro, bblayers.conf, etc... Sep 11 10:47:58 btw bluelightning, we faced an 'interesting' build issue which i summarized on the ML ;-) Sep 11 10:48:48 n01: have you removed meta-yocto? if so you'll need to change LCONF_VERSION from 6 to 5 in your bblayers.conf Sep 11 10:49:39 it is called opencapwap and we have opencapwap_1.1.4.bb opencapwap_1.1.5.bb opencapwap_1.1.6.bb and in the package group i want to install opencapwap 1.1.4 and in a other package group i want to install opencapwap 1.1.5 Sep 11 10:49:43 bluelightning: that's new to me ... why should I remove meta-yocto? sorry if it is a silly question Sep 11 10:49:54 n01: not that you should, just if you have Sep 11 10:50:02 I didn't Sep 11 10:50:31 n01: ah, right; I've realised, changing DISTRO is what will trigger this Sep 11 10:50:53 n01: so if you've changed DISTRO = "poky" to something else you'll need to change LCONF_VERSION as I mentioned above Sep 11 10:51:17 bluelightning: ok :( which is the rationale? Sep 11 10:52:16 n01: there's no good rationale I'm afraid; the problem is we had to bump LAYER_CONF_VERSION (which is compared to LCONF_VERSION) when the meta-yocto-bsp layer was split out of meta-yocto and poky's template bblayers.conf was changed as a result Sep 11 10:52:33 n01: thus OE-Core and poky are out of step with LAYER_CONF_VERSION Sep 11 10:52:50 perhaps we should just make a case for bumping OE-Core's version to avoid this pain Sep 11 10:53:16 bluelightning the idear is to have a packagegroup-lng_1.0 and a packagegroup-lng_2.0 bolth aving the same pkges in the rdepends but with different versions Sep 11 10:53:18 and a more explicit error message :) Sep 11 10:54:12 wfailla: well, you can't really do that in fact. Sep 11 10:54:27 you have to build 1 version of a recipe, not more. Sep 11 10:54:35 wfailla: you cannot do that with versions alone; because versioned files go into the sysroot, if you want to maintain multiple versions side-by-side you'll have to include the version in PN rather than just in PV (we do this with the "clutter" recipe and related recipes if you want to look at an example) Sep 11 10:55:07 ok Sep 11 10:55:14 i thoght so Sep 11 10:55:18 thx Sep 11 12:02:35 bluelightning: how should i deploy a group of packages with a specific version if that option is not given ? Sep 11 12:11:24 wfailla: you can just do the same thing with the packagegroups as you do with the individual recipes, i.e. have the version in the name Sep 11 12:16:57 Hi I am trying to use linux-lib-headers.inc in my new layer. but it doesnt find it Sep 11 12:17:09 I include it as follows Sep 11 12:17:13 require ${COREBASE}/meta/recipes-kernel/linux-libc-headers/linux-libc-headers.inc Sep 11 12:17:21 why doesnt it find it? Sep 11 12:21:05 Guest42914: use require meta/recipes-kernel/linux-libc-headers/linux-libc-headers.inc Sep 11 12:21:51 bluelightning : that doesn't work either Sep 11 12:22:10 Guest42914: er, that is strange, it should... Sep 11 12:22:51 yep , I donno Sep 11 12:23:54 nshould I install SYSV init script manually? Sep 11 12:24:05 I've defined INITSCRIPT_NAME and INITSCRIPT_PARAMS and inherited update-rc.d Sep 11 12:24:14 but I cannot see the initscript in the package Sep 11 12:24:14 Guest42914: ah, sorry, try require recipes-kernel/linux-libc-headers/linux-libc-headers.inc Sep 11 12:24:34 How can I make .bb recipe to download sources from local repository (located on the same filesystem)? The result should look something like 'git clone --no-hardlinks /path/to/my/other/project'. Sep 11 12:24:53 eren: you do also need to install the file within do_install if that's not already being done Sep 11 12:25:02 bluelightning: okkie Sep 11 12:25:08 so what's INITSCRIPT_NAME is used for? Sep 11 12:25:56 kbart: if you want to build a local source tree you should probably be using externalsrc.bbclass Sep 11 12:26:19 kbart: are you using master, the dylan branch, or some other branch/release? Sep 11 12:26:57 eren: that's the name that will be passed to update-rc.d in order to enable startup for the script Sep 11 12:29:18 bluelightning, I'm using danny (f00028caf257e386c0f3ae46bd4b3ba53dd0729d). Is it very bad? Sep 11 12:29:54 kbart: ok, should still work there I think Sep 11 12:29:56 bluelightning : ok I made silly mistake... Sep 11 12:30:01 thx Sep 11 12:30:02 kbart: http://www.yoctoproject.org/docs/current/dev-manual/dev-manual.html#building-software-from-an-external-source Sep 11 12:30:03 I also found an example SRC_URI = "git:///path/to/local/repo;protocol=file;branch=master" on http://yoush.homelinux.org:8079/tech/using-local-git-repository-with-openembedded. Is it a bad practice? Sep 11 12:31:16 kbart: well, the only thing I can think of is that if you're trying to build from some local source tree, wouldn't you want to be building the work-in-progress uncommitted source as opposed to the last commit? Sep 11 12:31:24 bluelightning: thanks Sep 11 12:31:42 kbart: I guess it depends on why you're building from there Sep 11 12:31:45 bluelightning, hm, that's interesting solution, but I guess it should do as I don't use other revision than HEAD much.. Sep 11 12:31:58 *revisions Sep 11 12:32:22 kbart: right, but assuming you're using this for live development, do you expect to commit every time before building? Sep 11 12:32:49 bluelightning, the motivation is that I want to maintain U-Boot and kernel as a separate projects and use oe to build complete filesystem (image) Sep 11 12:32:50 eren: np Sep 11 12:35:21 kbart: so if cloning is really what you want to do for that use case, that URL should work Sep 11 12:35:23 kbart: (the example you pasted above) Sep 11 12:38:17 bluelightning, the process usually goes like this: I do some changes in U-Boot and/or kernel (i.e. adding new kernel modules), commit changes to their repositories then use oe to rebuild everything. Which way would you recommend for such scenario? Sep 11 12:39:11 kbart: if you're prepared to make a commit every time before building, you can use the git:///path/to/local/repo approach Sep 11 12:40:08 kbart: and that sounds like your workflow, so I'd say go with that Sep 11 12:40:27 bluelightning, ok, thank you (again). Sep 11 12:40:35 np Sep 11 13:33:46 rburton: hi ! I'm trying to upgrade weston_1.1.0 to weston_1.2.0 but at build I got the following error : configure: error: Package requirements (wayland-server >= 1.1.90 pixman-1 egl >= 7.10 glesv2 xkbcommon) were not met: | | Requested 'wayland-server >= 1.1.90' but version of Wayland Server is 1.1.0 Sep 11 13:34:06 rburton: do you know how to fix this easily ? Sep 11 13:34:52 elbc_: you need to upgrade wayland too Sep 11 13:34:53 weston 1.2 needs wayland 1.2 Sep 11 13:35:00 please sent the patches when they're tested, i've been meaning to do that for *ages* Sep 11 13:35:19 rburton: ok ! Sep 11 13:43:26 has anyone used stty? Sep 11 13:43:44 I need to send an ESCAPE key to serial modem Sep 11 13:43:51 I can read the output perfectly with "cat" Sep 11 13:44:08 however, I cannot send escape character via "echo .... > /dev/ttyUSB0" Sep 11 13:44:10 any ideas? Sep 11 13:48:42 eren isnt it C-v C-] ? Sep 11 13:49:21 or C-v C-[ Sep 11 13:53:55 well I actually found it Sep 11 13:54:06 echo -en "\033@K\r" > /dev/ttYUSB0 Sep 11 13:54:51 then \033 is an escape sequence for this modem Sep 11 13:55:05 \033 is what you get with C-v C-[ Sep 11 13:55:15 afaik Sep 11 13:56:02 hexdump agrees :) Sep 11 13:57:40 jero: yeah, thanks but I needed the character code so that my machine initializes the modem :) Sep 11 14:00:24 is there any known problem in compiling uclibc with /cortexa9hf-vfp-neon? Sep 11 14:59:54 halstead: around? Sep 11 15:14:14 RP, Yes. At the datacentre at the moment. Sep 11 15:15:29 halstead: I sent email Sep 11 15:16:00 RP, I see it. I'm responding. Sep 11 15:24:34 halstead: thanks Sep 11 15:28:10 hi again, is there a way to have bitbake set different package names when using autorev and when not using autorev Sep 11 15:28:12 ? Sep 11 18:05:07 pidge: I have a problem with populate-lic sstate files not being generated using a packagegroup of native packages Sep 11 18:06:03 If I just run bitbake acl-native, the populate-lic sstate is created. But a package group with DEPENDS="acl-native" does not create them. Sep 11 20:03:43 Hi... anyone know off hand what would cause bitbake to hang on a pipe() very early on? Sep 11 20:17:59 ds2: isn't it fixed by recent fixes for bitbake - PR service interaction Sep 11 20:18:01 ? Sep 11 20:18:22 I haven't seen single hang since they were merged Sep 11 20:35:05 JaMa: Do you know if someone is working on creating a nativesdk for meta-qt5? Sep 11 20:54:12 gjohnson: few people said that maybe they will, but nobody send anything Sep 11 20:54:57 Hello. Does anyone know how to specify a source directory with SRC_URI? I've successfully used the git and tgz protocols, but no luck with directories. Sep 11 20:55:11 JaMa: I am new to yocto, if I wanted to try getting that done what would be the best way to start? Copy the native files and then change them to nativesdk? Sep 11 21:13:17 gjohnson: target recipes are closer, because native contain only the tools nothing else Sep 11 21:14:02 gjohnson: and qt5 isn't best task for newbie to be honest Sep 11 21:14:59 Jama: I know qt5 isn't for newbies but I really want to get it figured out so my company can start development with a nice SDK package. Sep 11 21:18:23 ok, fair enough **** ENDING LOGGING AT Thu Sep 12 02:59:59 2013