**** BEGIN LOGGING AT Wed Nov 19 02:59:59 2014 Nov 19 03:12:48 Hi All Nov 19 03:14:32 I have a custom git repo with submodules, I am using SRC_URI_prepend="ssh://server/path/to/git;protocol=ssh;branch=some" Nov 19 03:14:42 is there a way to clone recursively ? Nov 19 03:18:26 that's not a correct url Nov 19 03:18:39 the url scheme deteremines which bitbake fetcher is used, and hence, which command is run Nov 19 03:18:44 if you want to run git clone, you need git:// Nov 19 03:18:51 the protocol=ssh will take care of hte underlying protocol Nov 19 03:18:56 but in this case, you want gitsm:// Nov 19 03:19:01 thats the submodule handling at hte moment Nov 19 03:21:42 kergoth: I shall try that Nov 19 08:11:46 good morning Nov 19 08:37:33 morning all Nov 19 10:27:26 how can i install recursively headers that are in subdirs like /include/subdir1, include/subdir2 .. in do install ? Nov 19 10:28:18 wahwah: I think you need to use cp for that, the install command can't do that AFAIK Nov 19 10:29:42 ok like cp -r ${WORKDIR}/include/ ${D}${includedir} ? Nov 19 10:36:56 wahwah: yes, something like that Nov 19 11:47:43 does someone know how I can determine in a bb file if the build is run for x86-based architectures? Nov 19 11:50:26 jaeckel: typically we handle those sorts of things with overrides Nov 19 11:51:04 e.g. to add a configure param for x86 only you'd do EXTRA_OECONF_append_x86 = " --some-x86-specific-option" Nov 19 11:51:24 you can do similar things with task functions Nov 19 11:55:45 Hi quys. I am new in OE and bitbake. and I have a questions. 1. Do bitbake make physically a sysroot copy on my disk before it creates .tar.gz packages? 2. Is it a easy way to add package to my sysroot and not to have to compile whole image? Nov 19 11:56:12 I am using angstrom 2013.12 Nov 19 11:57:54 spaszkoPL: hi Nov 19 11:58:21 yes, OE handles the sysroot (tmp/sysroots/...) separately from packaged files Nov 19 11:59:14 you only need to build what is required to satisfy dependencies; the build system will take care of that for you (as long as you declare dependencies in your recipe, of course) Nov 19 11:59:33 assuming I understood your question correctly Nov 19 12:00:19 ok. So for example if i have a recipe xtrans_1.2.7.bb if a put a command "bitbake xtrans" it will make only this recipe and install it on my syroot, yes? Nov 19 12:01:02 spaszkoPL: correct yes, it'll also build packages for xtrans too Nov 19 12:01:04 Then I can copy sysroot folder to SD and it will work, instead of building whole image and gz files? Nov 19 12:01:26 well, the sysroot is for the build system, not for the target Nov 19 12:01:39 you can copy package files to the target and install them Nov 19 12:02:01 You mean install using opkg? Nov 19 12:02:10 yes, assuming you're using that Nov 19 12:03:08 Ok, soo the last question is where i can find builded opkg packages, are they in my sysroot or in another folder? Nov 19 12:04:10 spaszkoPL: they will be written out under tmp/deploy/ipk Nov 19 12:04:16 Anyway i can find it using "find" or grep so i can answer myself. Nov 19 12:04:41 might be tmp-eglibc/deploy/ipk with angstrom, not sure Nov 19 12:05:48 Yeah you're right. In my angstrom it is ./deploy/eglibc/ipk/{imagename} Nov 19 12:05:56 Thx a lot. Nov 19 12:05:58 ah right yes Nov 19 12:05:59 np Nov 19 12:11:09 Hmmm. I've compiled xtrans and .ipk location is here ./deploy/eglibc/ipk/armv7ahf-vfp-neon/xtrans-dev_1.2.7-r0.0_armv7ahf-vfp-neon.ipk Nov 19 12:11:58 spaszkoPL: that's xtrans-dev, so that'll be just the headers and unversioned .so symlink(s) Nov 19 12:12:21 assuming it's not just empty Nov 19 12:12:24 Yeah, but i cannot see xtrans.ipk Nov 19 12:13:11 you may be missing something in the install part - if your recipe doesn't inherit the autotools or cmake classes then you'll need to define your own do_install which does whatever is needed to install files into ${D} Nov 19 12:13:41 (and you'd only inherit autotools or cmake if the software uses autoconf+automake or cmake respectively as you might imagine) Nov 19 12:25:40 bluelightning, is it easy to remove the meta-webos-? from the dupe check page? Nov 19 12:27:23 bluelightning: okay, so I want to build OpenCV for arm, and by default it tries to pull in the ipp library that only supports x86... I was going to extend http://cgit.openembedded.org/meta-openembedded/tree/meta-oe/recipes-support/opencv/opencv_3.0.0.bb?h=jansa/master#n26 by something like already done in L30 Nov 19 12:28:37 but I suppose you know the right way how it should be done? ;-) Nov 19 13:14:43 Crofton|work: just use the Filter button at the top right, then the Select All button, then untick the ones you don't want Nov 19 13:15:45 jaeckel: do you know what the connection to ipp is? I don't see a reference in there Nov 19 13:16:25 it's handled in the cmake process of opencv Nov 19 13:17:53 so that would be an undeclared dependency then Nov 19 13:18:12 well, cmake resolves the dependancy itself Nov 19 13:18:16 you'd need to find a way of telling that process to explicitly disable that dependency Nov 19 13:18:18 if you don' Nov 19 13:18:29 t disable it it will download it and link against it Nov 19 13:18:42 yeah, I know that Nov 19 13:18:58 I wanted to something like ${@bb.utils.contains("SOME_ENVIRONMENT_VAR", "x86", "-DWITH_IPP=ON", "-DWITH_IPP=OFF", d)} Nov 19 13:19:10 or similar Nov 19 13:19:50 but I can't find a useful list of all the environment variables and what they contain Nov 19 13:24:19 or as alternative to follow your approach, is there something like EXTRA_OECMAKE_append_not_x86 ? Nov 19 13:27:15 one moment Nov 19 13:28:20 thanks Nov 19 13:29:40 I would suggest the way to handle this would be: Nov 19 13:29:42 PACKAGECONFIG[ipp] = "-DWITH_IPP=ON,-DWITH_IPP=OFF,ipp" Nov 19 13:29:49 IPPOPTION_x86 = "ipp" Nov 19 13:29:55 IPPOPTION = "" Nov 19 13:30:05 nice Nov 19 13:30:06 then add ${IPPOPTION} to the default PACKAGECONFIG value Nov 19 13:30:10 and that should work Nov 19 13:40:23 does the _x86 also handle x86_64? Nov 19 14:11:44 jaeckel: ah, actually no, you'd also need IPPOPTION_x86-64 = "ipp" Nov 19 14:20:42 JaMa: wrt world-build did you pull the klibc fix committed on 17 nov ? Nov 19 15:10:18 sigh.. cherry-picking from patchwork with so many duplicates again :/ Nov 19 16:46:56 hi Nov 19 16:48:06 if i include a lib recipe (lib derived with autotools), am i right that i still have to provide the regarding linker flags (i.e. they are NOT included into ${LDFLAGS} by OE)? Nov 19 16:49:37 OE doesn't replace your buildsystem (make, etc) Nov 19 16:49:41 it sits above that, and calls it Nov 19 16:50:20 ah i see Nov 19 16:50:30 thx Nov 19 16:50:48 so short answer: yes Nov 19 16:50:49 np Nov 19 19:04:07 fark, what is the name of the env file I need to source to do a native compile of a qqt thing? Nov 19 19:07:10 environment-setup Nov 19 19:08:04 :) Nov 19 19:29:00 in the oe-classic world, if I wanted a clean build, I just nuked the tmp/ directory. Has this changed in the oe-core world? Nov 19 19:31:22 you might need to wack the sstate dir also Nov 19 19:36:22 it really depends on what you mean by a "clean build" Nov 19 19:37:26 I was just usin ghis definition of nuking tmp Nov 19 19:39:14 kergoth: clean. start all over. nuke it from orbit Nov 19 19:40:00 rebuilding from source when you have matching sstate really doesn't accomplish anything, not much point to it, but yes, you can wipe the sstate cache or build with —no-setscene to do so Nov 19 21:30:39 DOes Holger Behrens ever hang out here? Nov 19 21:31:10 hi crofton Nov 19 21:33:07 hey woglinde **** ENDING LOGGING AT Thu Nov 20 02:59:58 2014