**** BEGIN LOGGING AT Mon Oct 17 02:59:56 2011 Oct 17 09:15:51 angstrom: 03testlab  07yocto * r474cffeb5d 10testlab/usrp_e1xx/eglibc/systemd-image/ (5 files): usrp-e1xx: systemd-image configured for angstrom v2011.10-core using branch angstrom-staging and revision 0fe6d2b7c06b7585dc4906c6f8465b6f023c1a1c Oct 17 12:01:49 Hi there. I've been playing around with Angstrom on a BeagleBoard-xM recently, using the OE-classic setup (accidentally). Now I was pointed at OE-core and tried Angstrom with the setup-scripts, that all works. Oct 17 12:03:07 However, everywhere I've been looking for oe-core and documentation about it, I'm pointed at Yocto and Poky. Is there any reason why Angstrom is based directly upon oe-core instead of poky? Oct 17 12:04:12 jonathan__: different ways of working really Oct 17 12:04:42 jonathan__: FYI, poky is basically oe-core + bitbake (+ some patches) + meta-yocto (some configuration) + docs Oct 17 12:05:10 so we are collaborating around the same core of recipes Oct 17 12:05:19 ok, thanks. That's clear. Oct 17 12:06:12 (I kind of sit in both camps, although my work on the Yocto project means I spend most of my time with Poky) Oct 17 12:06:59 So basically it just wouldn't make sense to do it. But I guess the Yocto/Poky documentation is the right place to find out about oe-core? Oct 17 12:07:45 of course it mentions yocto everywhere, but yes 99% of it is applicable Oct 17 12:14:31 Thanks for the info! Maybe you could help me on the following question as well..I posted it on #oe which is rather quiet today...In oe-classic I was creating a distribution of my own, based on a overlay setup using the already existing Angstrom configs. This was all working fine, until I found out I was working on an outdated branch of oe, pretty stupid. However, now I'd like to `port' my work to the oe-core way but I can't reall Oct 17 12:14:58 I guess I'm off best by starting to look at the setup-scripts of Angstrom? Oct 17 12:16:15 The documentation on Poky is very nice btw. Oct 17 12:16:54 angstrom: 03testlab  07yocto * r4e2f58bb64 10testlab/beaglebone/eglibc/systemd-image/ (3 files): beaglebone: systemd-image configured for angstrom v2011.10-core using branch angstrom-staging and revision 0fe6d2b7c06b7585dc4906c6f8465b6f023c1a1c Oct 17 12:17:45 jonathan__: so, what you did before is still perfectly feasible Oct 17 12:18:09 jonathan__: I'd recommend you create a new layer to hold your customisations on top of angstrom Oct 17 12:19:08 all you need is a new directory with conf/layer.conf in it, then add that to your bblayers.conf and then you're set, just add whatever additional/overridden conf/distro/* files you need to your layer Oct 17 12:19:23 have a look at meta-angstrom itself for an example Oct 17 12:24:32 Ok thanks a bunch for the information! I appreciate it. Oct 17 12:25:37 no worries Oct 17 12:37:09 angstrom: 03testlab  07yocto * rd8329be280 10testlab/beaglebone/eglibc/Cloud9-IDE/ (4 files): beaglebone: Cloud9-IDE configured for angstrom v2011.10-core using branch angstrom-staging and revision 0fe6d2b7c06b7585dc4906c6f8465b6f023c1a1c Oct 17 15:39:01 angstrom: 03testlab  07yocto * r9f1cf2c4b3 10testlab/beaglebone/eglibc/systemd-image/ (5 files): beaglebone: systemd-image configured for angstrom v2011.10-core using branch angstrom-staging and revision f2f46bce99fef2085beb86de924855b4e771bc3a Oct 17 15:59:13 angstrom: 03testlab  07yocto * r8504ee63d7 10testlab/beaglebone/eglibc/hw-bringup/ (5 files): beaglebone: hw-bringup configured for angstrom v2011.10-core using branch angstrom-staging and revision f2f46bce99fef2085beb86de924855b4e771bc3a Oct 17 16:28:58 angstrom: 03testlab  07yocto * re32ed711e3 10testlab/beaglebone/eglibc/Cloud9-IDE/ (5 files): beaglebone: Cloud9-IDE configured for angstrom v2011.10-core using branch angstrom-staging and revision f2f46bce99fef2085beb86de924855b4e771bc3a Oct 17 17:29:34 angstrom: 03testlab  07yocto * r0f46bef98a 10testlab/beaglebone/eglibc/TI-hw-bringup/ (5 files): beaglebone: TI-hw-bringup configured for angstrom v2011.10-core using branch angstrom-staging and revision f2f46bce99fef2085beb86de924855b4e771bc3a Oct 17 18:09:57 angstrom: 03testlab  07yocto * rb0d2513a7c 10testlab/beaglebone/eglibc/Cloud9-IDE/ (3 files): beaglebone: Cloud9-IDE configured for angstrom v2011.10-core using branch angstrom-staging and revision f2f46bce99fef2085beb86de924855b4e771bc3a Oct 17 19:10:32 anyone awake ? **** ENDING LOGGING AT Tue Oct 18 02:59:57 2011