**** BEGIN LOGGING AT Thu Apr 18 02:59:57 2019 Apr 18 10:49:29 Hi all, would it be possible to apply this patch https://www.mail-archive.com/openembedded-devel@lists.openembedded.org/msg63307.html on meta-java to allow warrior builds? Apr 18 11:21:31 New news from stackoverflow: Pysqlcipher3 cannot find sqllite3 shared library Apr 18 11:49:12 how do I add files to a recipe using devtool? Apr 18 12:44:12 I created a library and I would like to know what should be in the production package FILES-${PN} versus the FILES-${PN}-dev ? From what I understand, in FILES-${PN} I have to put the (at least) the library produced by the rule "install" of the Makefile, so "{libdir}/*". However, the "install" rule of the Makefile also produces symlinks and a call to "ldconfig -n {libdir}". Is it OK ? And in FILES-${PN}-dev I have to put that the headers "{includedir}/*" Apr 18 12:44:13 right ? Apr 18 12:47:56 erakis: FILES-${PN} and FILES-${PN}-dev have default values with "standard" paths, so you don't need to modify it unless you install something in an uncommon place Apr 18 12:50:23 nayfe: For standard file put in the (rootfs) do_install (includedir, bindir, confdir, etc...), they will be copied automatically in the package ? Apr 18 12:53:15 erakis: you can see here default values for FILES_${PN} .. etc https://www.yoctoproject.org/docs/current/mega-manual/mega-manual.html#including-static-library-files Apr 18 12:53:34 erakis and yes :) Apr 18 12:55:00 ronybeck> I'm not sure you can add a file to SRC_URI with devtool (I use it only to create recipes so I may be wrong) Apr 18 13:00:19 nayfe: Really interesting :) Thank you so much, I have a meeting and I will come back, I have a question on Makefile too. Apr 18 13:14:36 nayfe: I come from the Windows world and I have basic knowledge with Makefile and GNU recommendation. Does the "install" rule of the library's Makefile should create a symlink "mylib.so" -> "mylib.so.1.1.0"? And also calling "ldconfig -n $ {bindir}" at the end ? Apr 18 13:18:07 erakis: I'm not a Makefile expert, I'm using cmake those days :) Apr 18 15:23:38 Is there a way to get a BUILD NUMBER append to the version of each recipes ? I mean, this build number must be incremented at each build, no matter if the recipe or source code has changed. I read about the PR Service but it does not seem to be what I need. Apr 18 15:36:50 RP: If you can point me toward the link for those ptest JSON results, I'll open the bugs Apr 18 15:50:58 RP: JPEW: I'll also take a look at the result for lttng-tools Apr 18 15:51:17 psrcode: I saw your question about logs, I'll send some data about that Apr 18 15:51:22 (thanks) Apr 18 15:51:24 RP: +1 Apr 18 15:58:58 psrcode: mail reply off list with the logs Apr 18 15:59:28 JPEW: mail reply on list with the links and how to get the logs. Adding the logs from the first run to the bugs would be ideal Apr 18 16:00:08 Cool, I'll work on logging them to bugs Apr 18 16:01:26 For resulttool pulling from a URL, were you thinking some sort of "this path is a URL so download it" automatic detection or something like $ resulttool report -- url http://foo/bar Apr 18 16:05:27 Joshua Watt, could you (or anyone) ping me your email address? Thanks Apr 18 16:06:06 oh, found it Apr 18 16:11:39 JPEW: yes, if it starts with http it'd be handled as a remote url Apr 18 16:11:43 erakis> you can add inherit image-buildinfo but it creates more than just a number Apr 18 16:17:03 erakis> otherwise if you use jenkins or equivalent, you can add job number in local.conf and then use ROOTFS_POSTPROCESS_COMMAND hook to create a file with that variable Apr 18 16:17:31 there is also /etc/version file that matches a specific build Apr 18 16:21:36 ouch I'm offtopic, I don't see any reason to change version of a recipe that does not change? Apr 18 16:34:51 nayfe: I'm using Gitlab, they have a JOB_ID through their runner. But for now we did not setup a gitlab ro run our Yocto build machine. Maybe later... I was not aware of image-buildinfo, I'm going to read about it. Thanks Apr 18 16:37:31 I have a partition that's volatile made by yocto. How do I make it non-volatile? Apr 18 16:42:51 noway96> do you use systemd? Apr 18 16:43:14 yes Apr 18 16:43:36 what is your volatile partition? Apr 18 16:44:04 it's /var/log Apr 18 16:44:12 I want to make that persist on reboots Apr 18 16:44:14 then you should look at https://www.yoctoproject.org/docs/current/mega-manual/mega-manual.html#var-VOLATILE_LOG_DIR Apr 18 16:45:49 hmm doesn't jump to the section with # Apr 18 16:46:07 but thank you! Apr 18 16:46:24 how do I increase the size of the partition? Apr 18 16:54:07 noway96: you have to put VOLATILE_LOG_DIR = "no" if you want /var/log to be persistant Apr 18 16:54:25 in local.conf or distro conf Apr 18 16:56:51 For rootfs size, you have to set IMAGE_ROOTFS_SIZE but it will not be the exact size, so you have to add IMAGE_ROOTFS_MAXSIZE, IMAGE_ROOTFS_EXTRA_SPACE = "0" , IMAGE_OVERHEAD_FACTOR = "1.0" variables Apr 18 16:58:19 "Section 36.19. How do I create images with more free space" on manual Apr 18 17:01:54 so what is local.conf for exactly? Apr 18 17:03:13 local configuration. Apr 18 17:03:18 local to the build, that is Apr 18 17:03:23 hence the name Apr 18 17:05:00 vs what? Apr 18 17:06:05 so yocto has a generic .conf file and my local.conf has higher precedence? Apr 18 17:07:26 noway96> It is useful to temporary modify Yocto environment, then you can integrate those changes into custom machine/distribution configuration Apr 18 17:08:44 noway96, see openembedded-core/meta/conf/bitbake.conf, thats where all the big includes are being done Apr 18 17:38:05 RP: thanks for the link, still 781a947a5973553bb529c4b189a6ea7bca596749 does not seems to exist in poky/master-next, am I looking at the right git tree? Apr 18 17:42:49 RP: i'll try with poky/master-next for now Apr 18 17:52:45 New news from stackoverflow: Yocto CI Build number ? PR Service do not increment ${PR} Apr 18 18:06:17 nayfe: About the "image-buildinfo", from what I've understand so far, it give me the distro version, layers version, etc... but not a global build number that increment at each build. Did I miss something ? Apr 18 18:07:39 nayfe: What I need is a sequential build number (CI) that I can inject in a version.h from the do_compile_prepend or do_configure of a recipe. Apr 18 18:12:31 anyone have instructions to use qemu to load up an arm-based raspberrypi yocto image? Apr 18 18:24:45 erakis: so you can create custom variable, in local.conf or directly in bitbake command, like MY_VERSION, then in your recipe you can add MY_VERSION as a CFLAGS, then in version.h you use that variable as a #define Apr 18 18:26:05 nayfe: I could create a custom variable, in local.conf but how will it be auto incremented at each build ? This is what I don't understand :( Apr 18 18:26:59 Basically in a ci loop, you generate your local.conf on the fly Apr 18 18:28:46 But you can also call bitbake with wrapper script that manage build id Apr 18 18:28:51 Yeah but for now I don't have a CI. In a couple of week I will setup a gitlab runner.... Apr 18 18:30:10 nayfe: "bitbake with wrapper script that manage build id" -> Interesting, I've tough doing this last week but I don't know where put/handle the script. Apr 18 18:31:00 Anywhere on build host Apr 18 18:31:22 Brb in 10min Apr 18 18:34:45 I can clone a repository but when I try to do so using yocto it complains: Permission denied (publickey). Apr 18 18:36:20 nayfe: Suppose I create a script that hold a file with the build number in it. Once I trigger the build of an image I could open this file and increment the build number by 1. This is the easy part. What I don't understand is where do I call my script ? Sorry I'm a bit novice with Yocto. Apr 18 18:45:54 RP: Done: https://bugzilla.yoctoproject.org/buglist.cgi?query_format=specific&order=relevance%20desc&bug_status=__open__&content=ptest%20results%20are%20inconsistent%20per%20image&list_id=611830 Apr 18 18:52:03 noway96> can you put your SRC_URI of git repo? Apr 18 18:53:27 erakis> in freescale yocto, they use google repo to manage multiple layers and a script to initialize build folder (https://github.com/Freescale/fsl-community-bsp-base/blob/master/setup-environment) Apr 18 18:54:36 that wraps oe-init-build-env Apr 18 18:56:14 so what I have is a script (embedded in jenkinsfile) that calls ". setup-environment build-xxx && bitbake image-xxx" Apr 18 19:00:24 on build host, you create a script anywhere or in your yocto layer, that will do something like "source oe-init-build-env build-xxx && SW_VERS=`compute_version` bitbake myimage" and in recipe you add SW_VERS to CFLAGS depending on what makefile/cmake/whatever you use Apr 18 19:00:32 erakis Apr 18 19:07:51 nayfe: So you are creating an environment variable before calling bitbake to build the image. From any recipe, you read the environment variable (SW_VERS) and you inject it through CFLAGS so the compiler can replace it in the `version.h` or something similar. Apr 18 19:08:24 exactly :) Apr 18 19:11:56 kergoth: was just reading some archived irc logs. Seems you were working on a method to resize the partition on first boot. Are you able to share what you settled on? Apr 18 19:12:46 nate02: like expanding it to maximum size? :) Apr 18 19:12:52 yes Apr 18 19:14:46 nate02: I know raspbian do it with resize2fs_once Apr 18 19:15:16 https://github.com/RPi-Distro/pi-gen/blob/master/stage2/01-sys-tweaks/files/resize2fs_once Apr 18 19:20:17 nate02: mender uses https://github.com/mendersoftware/mender-convert/tree/master/files for instance :) Apr 18 19:23:03 nate02: 96boards-tools has a systemd service, that's what we'r eusing at mentor. see resize-helper at https://github.com/96boards/96boards-tools Apr 18 19:23:08 so seems you have a few different options Apr 18 19:23:29 https://github.com/96boards/meta-96boards/blob/master/recipes-bsp/96boards-tools/96boards-tools_0.12.bb Apr 18 19:26:35 is this the method you ended up using? Apr 18 19:27:06 The log was 2016, so understandable if you don't recall, haha Apr 18 19:27:09 i just said that. "That's what we're using at mentor". - https://github.com/MentorEmbedded/meta-mentor/tree/master/meta-mel-support/recipes-bsp/96boards-tools Apr 18 19:27:30 though apparently i need to update the recipe. we didn't wnat to pull in all of meta-96boards Apr 18 19:27:35 sorry, missed the targeted msg, my bad Apr 18 19:28:13 thanks! Apr 18 19:31:24 nayfe: Also thanks! Apr 18 19:31:37 np :) Apr 18 19:41:28 otavio_: Hi, do you think it is possible to apply this patch https://www.mail-archive.com/openembedded-devel@lists.openembedded.org/msg63307.html on meta-java to allow warrior builds? warrior is not ready yet so it's only only if you have some time, and if you're still meta-java maintainer? :) Apr 18 20:33:42 JPEW, RP: Just commented on util-linux ptest one. I think is not a bug. https://bugzilla.yoctoproject.org/show_bug.cgi?id=13301 Apr 18 20:33:43 Bug 13301: normal, Undecided, ---, ross.burton, NEW , util-linux ptest results are inconsistent per image Apr 18 20:35:54 justanotherboy: OK, that's good to know. It's good to have that documented somewhere at least Apr 18 20:38:28 JPEW: Where is a good place to document this behavior? Apr 18 20:40:16 justanotherboy: I'm not sure. I was referring to having it documented in the bugzilla.... at least we know its sort of expected behaviour. Whether we want to make it consistent across all the ptest images I couldn't say Apr 18 20:42:15 justanotherboy: Hmm, does that mean if we fix the test getting skipped the numbers will probably match up? Apr 18 20:44:43 JPEW: They should match up if the same numbers of test are run Apr 18 20:45:27 justanotherboy: OK, good. I think we are trying to get the two images to run the same tests. I'm commenting on the bugzilla now Apr 18 20:46:00 justanotherboy: thanks, I've replied. I think that explains the skipped but the passed counts are still a bug Apr 18 20:47:41 JPEW: thanks for filing those that is much appreciated! Apr 18 20:49:14 np. I was able to work on some of the resulttool improvements on the way. Apr 18 20:58:08 RP: I can work on adding the runtime dependencies to the util-linux-ptest package, my only concern is image size because of util-linux is installed even on core-image-minimal. I will check the difference on image size and report it to the bug. Apr 18 21:19:31 justanotherboy: its the dependencies util-linux-ptest has, not any other part of util-linux Apr 18 21:19:42 justanotherboy: util-linux-ptest is not part of core-image-minimal Apr 18 21:22:15 RP: Correct, just add the dependencies to RDEPENDS_${PN}-ptest Apr 18 21:22:37 justanotherboy: yes Apr 18 21:22:58 RP: It's just that I usually have ptest-pkgs in my IMAGE_FEATURES :) Apr 18 21:24:03 RP: But yeah, it shouldn't affect other enviroments Apr 18 21:24:16 justanotherboy: then your images won't be minimal :) Apr 18 22:21:08 Imgur: The magic of the Internet Apr 18 22:21:17 oops wrong one **** ENDING LOGGING AT Fri Apr 19 02:59:57 2019