**** BEGIN LOGGING AT Sun Feb 14 02:59:58 2016
Feb 14 06:41:45 <nithinjt> do_populate_sysroot is not copying everything I want. What could be the reason?
Feb 14 06:42:38 <nithinjt> also is do_populate_staging the same as do_populate_sysroot? Both seem to be used interchangeably in the bitbake manual?
Feb 14 06:46:30 <nithinjt> I am guessing this has something to do with WARNING: QA Issue: found library in the wrong location.
Feb 14 06:47:38 <nithinjt> those are the files which are not populated by do_populate_sysroot
Feb 14 06:47:59 <nithinjt> even though the location is correct
Feb 14 06:50:35 <nithinjt> somebody please help, give me a guess even if you don't know why?
Feb 14 10:12:16 <archer121> he
Feb 14 10:12:18 <archer121> hi
Feb 14 10:13:28 <archer121> My do_populate_sysroot is not putting all the all the files into the sysroot (staging area). How do I fix this?
Feb 14 10:14:58 <archer121> somebody please help be with this, I have been stuck with this for a looong time. :-(
Feb 14 10:15:05 <archer121> *me
Feb 14 10:15:58 <archer121> this package is a build dependency of another package, and since it cannot find the files, it is not compiling.
Feb 14 10:21:13 <JaMa> archer121: it populates only the files usually used by other components (stuff like libraries, headers, pkgconfig etc) you can easily extend the list
Feb 14 10:21:39 <archer121> the libraries I want are not populated.
Feb 14 10:21:54 <JaMa> define sysroot_stage_all_append()
Feb 14 10:22:07 <JaMa> are they in usual paths?
Feb 14 10:22:50 <archer121> JaMa: I have started using yocto only since 3 days. the learning curve is pretty steep. SO please bare with me if I talk rubbish
Feb 14 10:23:11 <archer121> They get installed in the correct paths in the final image
Feb 14 10:25:04 <archer121> The path is /usr/local/cuda-6-5{include/bin}
Feb 14 10:27:04 <JaMa> see staging.bbclass /usr/local isn't in paths which are staged in sysroot
Feb 14 10:30:18 <archer121> So I need to copy them manually in sysroot_stage_all_append() by cp -r ${WORKDIR}/output/usr/local ${SYSROOT_DESTDIR}/usr/local
Feb 14 10:32:04 <JaMa> Use sysroot_stage_dir ${D}/usr/local/foo ${SYSROOT_DESTDIR}/usr/local\
Feb 14 10:32:26 <JaMa> but why do you install it in /usr/local in first place?
Feb 14 10:33:24 <archer121> I am trying to install some binaries provided by Nvidia in the for of .deb files.
Feb 14 10:33:53 <archer121> The .deb installs them to /usr/local so I follow the same.
Feb 14 10:36:26 <archer121> JaMa: sysroot_stage_dir ${D}/usr/local/foo ${SYSROOT_DESTDIR}/usr/local\ is like a function call, right?
Feb 14 10:37:08 <archer121> so do I need the inherit the staging class in my recipe?
Feb 14 10:38:25 <archer121> why is there a backward slash in the second argument? is it a typo?
Feb 14 10:40:33 <JaMa> yes typo
Feb 14 10:40:40 <JaMa> and you don't need to inherit anything
Feb 14 10:41:03 <JaMa> it's already inherited
Feb 14 10:41:16 <JaMa> sysroot_stage_all_append only adds it to default function
Feb 14 10:42:10 <archer121> appended to the sysroot_stage_all function. thanks
Feb 14 11:09:31 <archer121> JaMa: This is what i tried to do: https://paste.ubuntu.com/15053144/ but I get this error: https://paste.ubuntu.com/15053158/
Feb 14 11:22:32 <archer121> I fixed it by appending to sysroot_stage_all instead
Feb 14 11:22:49 <archer121> maybe others where python functions
Feb 14 11:27:00 <JaMa> that's what I was saying from the start :)
Feb 14 11:30:07 <archer121> loz, thanks a lot!
Feb 14 14:43:14 <Seekha> What is the difference between using debian or yocto relealted projects for the BeagleBone Black?  Is it space related (on the flash)  ?
Feb 14 14:46:55 <Seekha> lighter?
Feb 14 15:08:35 <fledermaus> Seekha: depends on what you want. debian's got a ton of packages and is a pretty full-fat distro, if that's what you want. A yocto based thing will have whatever the people in charge decided to put in, so more just the bits they want.
Feb 14 15:09:10 <Seekha> Ok, I saw that too
Feb 14 16:46:17 <archer121> can I set a shell environment variable from EXTRA_OECMAKE?
Feb 14 16:50:20 <neverpanic> No
Feb 14 16:50:31 <neverpanic> EXTRA_OECMAKE is passed as argument to the cmake invocation
Feb 14 16:51:20 <archer121> I see, so I can set env variables from do_cmake_configure_append()
Feb 14 16:51:40 <archer121> *prepend
Feb 14 16:51:40 <neverpanic> _append() would probably happen *after* the cmake invocation, so doesn't really help you
Feb 14 16:51:49 <neverpanic> Try do_configure_prepend() { export foo }
Feb 14 16:52:02 <archer121> sry that was a typo.
Feb 14 16:52:28 <archer121> Finally I understand how yocto works.
Feb 14 16:52:38 <archer121> (atleast somewhat)
Feb 14 16:52:42 <archer121> thanks
Feb 14 17:25:49 <archer121> My cmake inside do_configure is trying to execute a binary executable file, and it fails. So what architecture does cmake executed by cmake.bbclass expect? host architecture or target architecture?
Feb 14 17:26:17 <neverpanic> archer121: your host's architecture
Feb 14 17:26:26 <neverpanic> which usually means you need a -native version of the tool
Feb 14 17:28:06 <archer121> the binary file is of target's architecture
Feb 14 17:28:51 <archer121> native = host or target?
Feb 14 17:29:06 <archer121> neverpanic?
Feb 14 17:40:43 <neverpanic> native = host
Feb 14 17:40:52 <neverpanic> if it's a target binary, that won't work
Feb 14 17:51:03 <archer121> neverpanic: So we are making cmake cross compile?
Feb 14 18:08:21 <neverpanic> Yocto does automatically, usually
Feb 15 02:03:56 * nerdboy made a convenience tool for beaglebone  => https://github.com/VCTLabs/vct-beagleboard-bsp-platform
**** ENDING LOGGING AT Mon Feb 15 02:59:59 2016