**** BEGIN LOGGING AT Tue Sep 01 02:59:58 2015 Sep 01 07:38:48 morning all Sep 01 07:39:27 morning bluelightning Sep 01 07:40:05 hi nrossi Sep 01 12:09:04 gm Sep 01 12:09:52 morning Crofton Sep 01 12:35:15 hi Crofton|work Sep 01 12:35:55 How are things going? Sep 01 12:36:19 you know abut buildhistoy, right? SHould I expect anythig useful for -native and nativesdk- builds? Sep 01 12:36:31 Crofton|work: great thanks Sep 01 12:37:04 Crofton|work: yes... for native IIRC you may only get srcrevs recorded, let me just check that Sep 01 12:37:13 that is what I see Sep 01 12:37:37 working on a recipe for thrift and I need -native and nativesdk Sep 01 12:37:42 madness Sep 01 12:37:59 nativesdk needs a binary that runs in the sdk and likely libs to link with :) Sep 01 12:38:09 right... native doesn't package anything hence the lack of info Sep 01 12:38:20 yeah, that is kind of what I worked out Sep 01 12:38:31 nativesdk does though so you should see info for that Sep 01 12:38:42 playing with build config to only build the thrift compiler and wanted to check output Sep 01 12:38:58 will we see you at all during elce? Sep 01 12:39:53 still waiting to find out if I can go Sep 01 12:40:37 well, surely they pay for travel to important meetings :) Sep 01 12:41:12 you would hope so yes Sep 01 13:48:00 bluelightning, I sure hope I set up my git config to correectly send patches for oe-core :) Sep 01 13:55:05 Crofton|work: this can't be your first OE-Core patch though surely? Sep 01 13:55:30 no, but I forget the incantion Sep 01 13:55:44 I always cut and paste from the readme for other layers :) Sep 01 13:57:31 Crofton|work: use the git config lines I added to the "how to submit a patch" page and you never have to remember any of the options again (well, you will need subject-prefix for meta-oe, but still) Sep 01 13:57:32 for this layer email seeting are in git config and I ahve to trust memory Sep 01 15:31:12 is there a way to set the hostname in local.conf when building yocto? Sep 01 15:57:17 bluelightning, my email is missing the [ prefixoe-core] Sep 01 15:57:24 hopefully it gets picked up anyway Sep 01 15:59:09 unlike meta-oe, there's no prefix beyond what the list does Sep 01 15:59:18 Crofton|work: the list [OE-core] prefix gets added automatically. you don't do it. if you don't see it in your email, it's because your email provider deleted the inbound duplicate of your message coming from teh hlist and kept the one from your sent mail, so it doesn't exist there, but does on the one that hit the list Sep 01 15:59:29 hmm Sep 01 15:59:54 afaik, anyway. at any rate, you can always examine gmane to see what your email on the list looks like, in general Sep 01 16:00:05 also useful to see if your email hit the list at all, if you have concerns about your email provider Sep 01 16:00:09 thanks Sep 01 16:00:10 http://news.gmane.org/gmane.comp.handhelds.openembedded.core Sep 01 16:00:17 archive look sfine Sep 01 16:00:41 hmm Sep 01 16:38:37 realBigfoot: this is what you are after right -> https://github.com/openembedded/openembedded-core/blob/master/meta/recipes-core/base-files/base-files_3.0.14.bb#L66 Sep 01 16:39:36 nrossi, perfect! Thank you very much Sep 01 16:39:46 i was looking after this info indeed Sep 01 16:40:07 yer, interestingly its not in the ref-manual glossary **** ENDING LOGGING AT Wed Sep 02 02:59:58 2015