**** BEGIN LOGGING AT Thu May 30 03:00:00 2013
May 30 08:27:59 <RagBal> |  * satisfy_dependencies_for: Cannot satisfy the following dependencies for angstrom-packagegroup-gnome:
May 30 08:28:00 <RagBal> |  * 	gconf-sanity *
May 30 08:28:24 <RagBal> When I build cloud9-gnome-image for beaglebone
May 30 08:29:07 <RagBal> The package gconf-sanity is actually building correctly, I tried to clear and rebuild it
May 30 21:21:15 <diddly> russell--: ping
May 30 22:15:00 <russell--> diddly: pong
May 30 22:31:42 <diddly> russell--: hey, so I've built up my MACHINE=beaglebone via the instructions you pointed me at.  Now I'm wondering what to do with the result?  Ie. where can I find my SDK/toolchain in the raft of stuff that it built.  I have a "tmp-angstrom_v2012_12-eglibc" dir in build/ but am not sure what to do next
May 30 22:38:35 <russell--> diddly: build/tmp-angstrom_v2012_12-eglibc/deploy/images/beaglebone
May 30 22:39:28 <russell--> that's where your filesystem tarballs and uboot parts go
May 30 22:39:53 <diddly> right!
May 30 22:40:40 <diddly> and I guess I can just add sysroots/x86_64-linux/usr/bin/armv7a-vfp-neon-angstrom-linux-gnueabi to my PATH to get the cross compiler?
May 30 22:43:46 <russell--> the right way would be to create a recipe for your program and use the build system to cross compile for you
May 30 22:44:33 <diddly> i've written ebuilds before, recipes are similar?
May 30 22:44:51 <russell--> find sources -name \*.bb | less
May 30 22:45:16 <russell--> pick one that looks similar to your program (maybe one exists already) and change to match your needs
May 30 22:45:55 <diddly> what about development, i'll have guys writing software and not yet requiring the rigidness of a .bb
May 30 22:46:10 <diddly> is there a development guide anywhere for angstrom that you know of?
May 30 22:46:52 <russell--> there is a yocto document that talks about quilt and git workflows
May 30 22:47:18 <russell--> http://www.yoctoproject.org/docs/current/mega-manual/mega-manual.html
May 30 22:47:57 <diddly> cool!
May 30 22:47:58 <russell--> i think you'd be ahead of the game to learn and let the openembedded infrastructure work for you
May 30 22:48:40 <russell--> if its your own software, you probably want to create your own layer and use that infrastructure as well
May 30 22:49:18 <diddly> definitely, I've integrated our own stuff into gentoo/ubuntu before and it buys you a lot to use the package manager
May 30 22:49:31 <diddly> have you made a custom kernel in OE/angstrom?
May 30 22:50:11 <russell--> not personally, /me is still a bit of an OE newbie.  i have a lot more experience with the openwrt build system
May 30 22:50:34 <diddly> aye
May 30 22:51:01 <diddly> my problem is I'm leaving a job and trying to teach a new guy/my successor how to use a platform I've never used before :)
May 30 22:51:09 <russell--> lol
May 30 22:51:10 <diddly> and he's not "a linux guy"
May 30 22:51:20 <russell--> well, soon it won't be your problem anymore ;-)
May 30 22:51:29 <russell--> "good luck!"
May 30 22:51:35 <diddly> hehe
May 30 22:54:18 <russell--> maybe they should hire someone who is a linux guy, to work on a linux system
May 30 22:54:31 <diddly> stop using logic
May 30 22:54:35 <russell--> lol
May 30 22:55:11 <russell--> it might work to grind the persons arm off in a cheese grater, too!
May 30 22:56:06 <diddly> lucky for me the guys very quick and picking up what I lay down, but he's got a lot to pick up and its hard for me to teach as I learn, but y'know
May 30 22:57:21 <russell--> google + brain + helpful people on the intarwebs == ultimate success
May 30 22:57:28 <diddly> yup!
May 30 22:57:40 <diddly> and also I'm getting paid to learn something new too :)
May 30 23:03:34 * russell-- wouldn't mind getting paid, but will learn anyway
**** ENDING LOGGING AT Fri May 31 02:59:58 2013