**** BEGIN LOGGING AT Sun Apr 26 02:59:59 2015
Apr 26 21:01:14 <sayguh> Very sorry, simple question. Been trying to parse through the manual for this but am not having any luck.  My recipe builds fine and installs when I include it in an image but it is not populating the sysroot for other down stream recipes to build off of.  What class do I inherit from or magic one liner do I need here to populate sysroot with my built library?
Apr 26 22:03:51 <kergoth> sayguh: If you install files into proper locations in do_install, those files will be both in the sysroot and its binary package. If not, then not.
Apr 26 22:04:05 <kergoth> sayguh: e.g. headers into ${D}${includedir}, libs into ${D}${libdir}, ..
Apr 26 22:06:57 <sayguh> Yeah I was just reading through some other examples.  I'm not sure why my stuff isn't getting automatically installed.  I do not override any of the do_install methods, instead I'm inheriting from autotools-brokensep pkgconfig and pythonnative.  It must be one of my EXTRA_OECONF or CACHED_CONFIGUREVARS that is causing things to install impropertly
Apr 26 22:09:33 <kergoth> highly unlikely
Apr 26 22:09:49 <kergoth> examine the ${D} directory (${WORKDIR}/image) and see what got installed and where.
Apr 26 22:18:29 <xulfer> Is there a way to ignore errors within a certain package?
Apr 26 22:23:26 <kergoth> assuming you mean recipe, not binary package, ignore in what way? bitbake -k will continue to run other tasks it's possible to run, but anything depending on the recipe which failed obviously cannot be built, which includes any images which include i
Apr 26 22:23:27 <kergoth> t
Apr 26 22:24:35 <xulfer> Ah.  Well I'm hoping I can do something in the recipe.  I tend to want failures to stop the build.  But in this case it makes more sense to me to just allow the failure.  (It still works for what I need it to).
Apr 26 22:25:11 <kergoth> what's the failure?
Apr 26 22:26:10 <xulfer> Building a project that is contained within the chromium source.  Even though I'm not pulling in all of chromium it will fail (after checkout) because I don't have all of the deps needed for chromium itself.
Apr 26 22:26:18 <xulfer> So it appears as a fetch failure.
Apr 26 22:27:20 <sayguh> What does it mean if there is no image directory in my workdir?
Apr 26 22:27:23 <xulfer> So I'm left with somehow allowing this failure and using the source (which does get pulled down, merged, etc, etc).  Or from scratch reimplementing whatever black magic their tools use.
Apr 26 22:27:39 <kergoth> sayguh: your do_install didn't install anything.
Apr 26 22:28:27 <kergoth> xulfer: sounds like you need to customize the fetch process in some way. there's no way to tell bitbake it's okay to have a task fail. as far as it's concerned, no tasks which depend on a failed task can run, since they require what that task did
Apr 26 22:28:52 <xulfer> Yeah it's an understandable feature.  I just didn't know if there was a workaround.
Apr 26 22:50:12 <xulfer> Hm.  I think I'm going to try an || : on the command and see if that works.
Apr 26 22:54:44 <kergoth> seems reasonable
**** ENDING LOGGING AT Mon Apr 27 02:59:59 2015