On Tue, 18 Dec 2012, Bjørn Forsman wrote:
I only switched the branch of setup-scripts to angstrom-v2012.12-yocto1.3. Because in master "bitbake systemd-image -c populate_sdk" doesn't work at all (as the populate_sdk thingy came in yocto 1.2+).
Patient: Doctor, when I bang my head against the wall it hurts. Doctor: Don't bang your head against the wall.
So, how do angstrom people create SDK's for their images?
I wasn't trying to be sarcastic, but don't understand what you have done, and was only trying to find out so I might be able to offer some useful advice.
I pull the setup-scripts from github and execute the following: ----- $ git clone git://github.com/Angstrom-distribution/setup-scripts.git $ cd setup-scripts $ MACHINE=beaglebone ./oebb.sh config beaglebone $ MACHINE=beaglebone ./oebb.sh bitbake systemd-image -----That builds the entire toolchain to cross compile to arm, and all the packages are retreived and built for the systemd-image.
Doesn't that work for you? -- Regards, Alan
_______________________________________________ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
