**** BEGIN LOGGING AT Thu Jul 18 02:59:58 2013 Jul 18 07:14:47 If anyone is awake and nearby I'd like some help with finding out WHY I can't get theese instructions working on my TV. Jul 18 07:15:41 http://factory-reset.com/wiki/LG_Service_Menu Jul 18 07:57:55 morning all Jul 18 08:48:23 i knew it... Jul 18 08:49:10 gstreamer_0.10.36 in meta/recipes-multimedia Jul 18 08:53:18 nerdboy: ? Jul 18 09:24:30 morning all Jul 18 10:10:08 hi all Jul 18 10:24:22 Hi. I am writing a recipe for a software where the same source code compiles as kernel module, and as a user-space library. The resulting module is of course machine (kernel) specific, but the user-space library is not. If I 'inherit module' in my .bb file, all resulting packages (including user-space library) are machine specific, which I don't want. Is there a way to get round that without creating two recipes? Jul 18 10:25:58 hi pb_ Jul 18 10:26:51 andre_d: In any case I would say two recipes are cleaner. You are having to components after all Jul 18 10:27:10 andre_d: right, I'd agree with stefan_schmidt_w Jul 18 10:31:55 OK. Thanks. My thinking was that it'd be nice to have all related build instructions in one place, and bitbake wouldn't have multiple work directories. Jul 18 10:35:18 andre_d: if you have many things that are shared between the two components you could have an include file which abstracts these details out Jul 18 10:36:00 i'm doing that now indeed Jul 18 10:36:03 thanks Jul 18 10:36:20 cool Jul 18 16:32:50 moin Jul 18 16:45:01 shouldn't the preferred_provider_jpeg = libjpeg-turbo work in oe-classic? Jul 18 16:46:10 at least if libjpeg-turbo is already built, why would a package with "jpeg" in depends pull in jpeg-8b ? Jul 18 16:52:25 damn, i just noticed it only has an RPROVIDES_${PN} = "jpeg" Jul 18 16:53:09 jpeghell :) Jul 18 16:57:57 * mr_science adds some sprinkles Jul 18 17:47:53 maybe i should just add a virtual/jpeg ... Jul 18 18:12:13 time to get the red pen and review some docs old-school style... Jul 18 18:49:33 3 down, one to go Jul 18 22:30:14 Hello; I am looking why, when building for hardfp, gcc is not getting __ARM_PCS_VFP set. Any clue? Jul 18 23:03:02 otavio: not without more info... Jul 18 23:03:34 what does your build config say when you start a build? Jul 18 23:04:18 specifically, TARGET_FPU and DISTRO FEATURES Jul 18 23:13:22 if you have the right stuff in the latter, it should build hardfp as aexpected Jul 19 00:03:54 otavio: if you ping me later i can look at the hardfp config i just setup a couple of weeks ago Jul 19 00:04:13 er, ping nerdboy ... Jul 19 00:07:29 mhnoyes: I found it Jul 19 00:07:37 Oh Jul 19 00:07:40 :) Jul 19 02:31:07 otavio: did you get it sorted out? **** ENDING LOGGING AT Fri Jul 19 02:59:58 2013