**** BEGIN LOGGING AT Thu Dec 28 03:00:02 2017 Dec 28 06:49:51 what is yocto's counterpart of %dir in rpm Dec 28 06:52:49 that is how to package a dir but not its content? Dec 28 08:56:35 morning Dec 28 10:28:24 Hey guys! Have anyone experienced interfacing smart package manager from a Qt/C++ software? Is there any C++ API library for it? Dec 28 10:28:43 *has anyone Dec 28 10:59:04 hey guys! I see that rocko does include dtb files now with the raspberry sd card image. But what do I do if I want additional overlays? do dtb include all of them at once or I need to append something in local.conf? Dec 28 11:07:51 Has anybody achieved booting a raspberrypi3-64 image yet ? Dec 28 11:08:07 Mine is just stuck at the rainbow screen for now. Doesn't look like the kernel even boots :< Dec 28 11:10:33 is there a kernel8.img in /boot? :-) Dec 28 11:10:47 I had my success w/o yocto with this https://github.com/drtyhlpr/rpi23-gen-image , 4.11 worked in 64 bit mode Dec 28 11:11:30 mjourdan, Dec 28 11:12:12 yup there is Dec 28 11:12:48 I tried with 2 different sd cards just in case Dec 28 11:15:18 mjourdan, are all dtbs in place? Dec 28 11:16:39 I think so. I have bcm2837-rpi-3-b.dtb, bcm2710-rpi-3-b.dtb, and a few dtbo in overlays Dec 28 11:17:03 Is there a way to get pre-kernel console on the pi ? I tried the uart on pins 8-10 but it doesn't output anything :P Dec 28 11:18:01 kernel has options like debug and earlyprintk Dec 28 11:18:22 "Show kernel log messages that precede the initialization of the traditional console" Dec 28 11:18:35 oh yeah but I meant before the kernel logs Dec 28 11:18:43 like bootloader outputs Dec 28 11:18:59 because I think my kernel isn't even booting Dec 28 11:19:10 mjourdan: Which branch are you using? master? Dec 28 11:19:20 I'm on pyro right now Dec 28 11:19:59 ok. I'd advise trying rocko if you can. We improved rpi3 64-bit support significantly during rocko development Dec 28 11:21:53 any ideas on why does ft5406 thinks of the official touchscreen as 800 by 600? :-) I think, I'm missing some dtb here, but I'm not sure :-( Dec 28 11:21:56 Sure I can try rocky but it seems almost all the importants commits were backported to pyro either way Dec 28 11:22:05 rocko* Dec 28 11:24:04 Sadly the commits which actually fix hdmi output weren't backported. There was a bunch of re-factoring and possibly breaking changes I've left them out of the backport list so far Dec 28 11:27:01 alright Dec 28 11:27:06 If for some reason you do get stuck on pyro drop me a message and I'll see if I can suggest the patches to try backporting Dec 28 11:31:30 No worries let me try rocko first Dec 28 13:15:27 paulbarker: rocko does boot in aarch64, so yay :). On to port my stuff to rocko then. Dec 28 13:16:40 ed21: hello, have any significant changes been made to how wic uses IMAGE_BOOT_FILES when transitioning from Pyro to Rocko? Because I am now porting my layer and find that wic now puts wrong files in the partition Dec 28 13:16:52 used to work fine on Pyro Dec 28 13:40:56 eduardas_m: i didn't have any trouble with wic between pyro and rocko, what is your board ? Dec 28 13:43:16 nayfe: I am using DART-MX6 from Variscite. But now I think the problem actually is that there is a default assignment of IMAGE_BOOT_FILES somewhere and the problem occured because I was using IMAGE_BOOT_FILES assignment with ?= Dec 28 13:43:55 I am currently writing my image to sdcard after fixing it Dec 28 13:44:28 will see if that is the problem Dec 28 13:45:22 ok, don't see anything in http://www.yoctoproject.org/docs/current/mega-manual/mega-manual.html#moving-to-the-yocto-project-2.4-release appart the kernel device tree stuff Dec 28 13:46:59 nayfe: yes, I've already looked at that Dec 28 13:50:18 eduardas_m: if i may ask, you add some custom files ? Dec 28 13:51:00 nayfe: yes, initrd and separate kernel + dtb for recovery mode partition Dec 28 13:51:08 that acts as fallback Dec 28 13:51:20 in case main user partition is damaged Dec 28 13:53:47 nayfe: it appears that the "problem" might be changes in meta-freescale as now a default value for IMAGE_BOOT_FILES is generated by adding dtb names to it Dec 28 13:53:50 eduardas_m: hard to tell what was changed there. I'll look at the git log. Can you give more details, please? Can you show your .wks? Dec 28 13:55:11 ed21: thank you for replying, but I can now verify that the thing that actually broke my recipe are changes in meta-freescale and not wic Dec 28 13:55:37 and I was probably doing it wrong anyway Dec 28 13:56:06 I really had to use a simple = assignment instead of ?= Dec 28 13:56:22 it now works, just checked my new image Dec 28 14:01:20 the specific commit that broke my recipe is probably this one: http://git.yoctoproject.org/cgit/cgit.cgi/meta-freescale/commit/?id=ac419895663889d65cc3828b7d6ce150199526bb Dec 28 14:03:07 eduardas_m: ok, no prob Dec 28 14:04:37 ed21: also, since you are here, I would like to ask whether there is a standard documented way of passing bitbake variable values to a wic plugin Dec 28 14:05:16 ed21: I know about get_bitbake_var, but there was a slight problem when trying to use it Dec 28 14:05:57 ed21: it appears that one has to do something like WICVARS += " SINGLE_DEPLOY_FILE" Dec 28 14:06:48 for something like the variable SINGLE_DEPLOY_FILE to be accessible in the plugin code via get_bitbake_var Dec 28 14:07:35 as far as I can tell WICVARS is not documented in the 2.4 release or earlier Dec 28 14:08:32 and that got me really confused when trying to implement a custom wic plugin Dec 28 14:14:14 the only way I actually found out about this is by doing bitbake -e | grep -i wic Dec 28 14:17:17 eduardas_m: yeah, wic documentation is far from being perfect. sorry about that. Dec 28 14:30:20 Hi, I am trying a custom NetworkManage rrecipe that was working fine with yocto 2.2 and it is failing now with yocto 2.4. It is failing on configure because of: "checking for gtk-doc... no" Dec 28 14:30:36 I tried adding 'gtk-doc-native' to DEPENDS, but it does not fix it. Any ideas? Dec 28 14:38:06 Umh I see now that that was only a WARNING. The real ERROR is : "configure: error: "--enable-introspection aims to build the settings documentation. This requires GObject introspection for python (pygobject)" Dec 28 14:38:19 I do have 'DEPENDS = " (...) python3-pygobject-native" Dec 28 15:00:03 Hey guys! Has anyone experienced interfacing smart package manager with C/C++ software? Is there any C/C++ API library for it? Dec 28 15:07:58 wanderer_: since it is a Python tool, I do not see another way than making a C/C++ program interface with the CLI... if you use Qt, QProcess is probably appropriate... though I personally have no experience with smart package manager in particular Dec 28 15:08:40 I use opkg, not sure what benefits are there in using smart package manager Dec 28 15:11:22 i am doing some progress. The check failing is: "$PYTHON" -c 'from gi.repository import GObject' Dec 28 15:11:54 https://pastebin.com/4aLrMiHj Dec 28 15:12:46 However GObject seems like it is installed: https://pastebin.com/eeFWerAB Dec 28 15:13:01 I also have 'python3-pygobject-native' in the DEPENDS list for that recipe Dec 28 15:23:07 eduardas_m: does it resolve dependencies and download necessary packages on demand? Dec 28 15:28:12 eduardas_m: Opkg attempts to resolve dependencies with packages in the repositories - if this fails, it will report an error, and abort the installation of that package. Dec 28 15:28:37 Ok, I see now. As far as it is written in C maybe it's a better choice for me (besides saving space) Dec 28 15:31:32 Oh, no, it works only with *.ipk. I need to support rpm. Thanks for help, anyways! Dec 28 16:37:44 reminder to all yocto that cmake was a TERRIBLE choice for an option for the yocto plugin, the other choice (forgot what it is now) is not much better, maybe worse Dec 28 16:54:18 reminder to all yocto that cmake was a TERRIBLE choice for an option for the yocto plugin, the other choice (forgot what it is now) is not much better, maybe worse Dec 28 17:19:14 Which mailing list could I use if I am having problems compiling a custom NetworkManager recipe? Dec 28 17:35:14 what do you mean by custom NetworkManager? you don't use the one from oe-core ? Dec 28 21:08:05 Hmm, need to add python3 support to recipetool's create python buildsystem handler. Dec 28 21:08:28 need to parse setup.py (requiring that it's parsable by python 3 regardless of which the project supports) and check the python version specifications in the classifiers Dec 28 21:39:31 Can two builds running on the same machine at the same time safely share the same sstate? Dec 28 21:41:52 I observe corrupted ipks... Dec 28 21:44:07 When builders build the same SDK, one builder occationally prints "Removing corrupt package file ..." during package installation. With what the SDK generation fails. **** ENDING LOGGING AT Fri Dec 29 03:00:02 2017