Fantastic, thanks for this, I'm in the process of running my first build.
However, it occurs to me that perhaps I don't need to copy the
beagleboard.org_image.sh script ... it seems to write all of the things I
want to change to the .project file ... If I drop in my own version of this,
will the "stock" beagleboard.org_image.sh pick those up?
Hey someone noticed the heart of the script.
Correct, just setup ".project" and run
/bin/sh ./RootStock-NG.sh
Couple of other questions:
1) I'm working out of master, should I be using the 01.10.2014 branch? I'm
happy to work on the bleeding edge, as long as I can load my capes .dts via
EEPROM
Master is fine.. I only tag releases for ease of looking back...
2) I need to load some "unstable" packages from sid, is there any way in the
script to do this? -- specifically, golang-go (2:1.2-2) for Go 1.2
I haven't setup any apt-pinning yet, so in the script it's dangerous..
When i need something from sid, i just try to back port it first..
Follow:
https://wiki.debian.org/sbuild
(sid -> wheezy, amd64 -> armhf)
Make sure to set:
$build_arch_all = 1;
$build_source = 1;
Then just:
sbuild http://ftp.us.debian.org/debian/pool/main/g/golang/golang_1.2-2.dsc
hopefully you have enough memory/cpu for it to build.. (and wheezy has
the dependices, if it doesn't well it gets funner...)
3) I'm curious as to what is QEMU used for? I actually need it to cross
compile Erlang for the BBB, so I'd like to see how it's getting used.
So the script can run on an x86 machine.. Back when all the script did
was: debootstrap/dpkg/apt-get qemu worked well, howver anything like
"git clone xyz" qemu can fail.. So run it native, but in some cases
on x86 is fine..
Regards,