On 12/19/2012 02:06 AM, Bjørn Forsman wrote: > On 19 December 2012 05:09, Peter Kurrasch <gtin...@hotmail.com> wrote: >> Previously... >> >>>> 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+). >> >> ...snip... >>> >>> 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 >> >> >> Point of information: the above procedure should give you >> "angstrom-v2012.05-yocto1.2" whereas Bjorn is trying to use >> "angstrom-v2012.12-yocto1.3". I don't think this later version is formally >> released yet? (BTW--I found this in my sources/layers.txt file.) >> >> Regarding the 2012.12 release, I saw on one of the myriad sites/pages/wikis >> I've reviewed recently that a "meta-beagleboard" will (or probably will) be >> introduced. The page mentioned this in conjunction with audio drivers and >> there's something about it not being ready yet, blah blah blah. The point >> is that I wonder if the release is ready for prime time yet and if something >> fancy like populate_sdk is sufficiently fleshed out? > > Ok. But as far as the populate_sdk task goes, it seemed to work in the > angstrom-v2012.12-yocto1.3 branch. Except for the openssh/dropbear > conflict with the systemd-image, which is the reason for this thread. > "bitbake core-image-minimal -c populate_sdk" works.
I am pretty sure populate_sdk is new to 1.3. Philip > >> As for dealing with SDK's, this is something I've been trying to wrap my >> head around for a while. I've come across the Arago project (also as >> meta-arago) and the Sitara SDK--actually, any number of different TI SDKs. >> I've been wondering how the meta-arago is supposed to tie-in with >> meta-angstrom but haven't seen anyone who says it can be done. I also don't >> understand how the Sitara SDK is supposed to work here since it provides its >> own toolchain and doesn't seem to have a particular association with a Linux >> release/distribution. > > Yeah, TI has their own SDK(s) and I have no idea how that maps into > openembedded. I think TI often use the CodeSourcery (now Mentor) > toolchain for their SDKs. > >> I assume, Bjorn, that all you want to do is build new code using the same >> headers, compilers, etc. as was used to build Angstrom...is that right? >> This is what I'd like to do, myself, but so far I haven't quite figured that >> out. I did do a sample program using the Sitara SDK but haven't tried >> anything too ambitious yet. > > Yes, I'd like to get the toolchain, headers and libraries that was > used to build the systemd-image. > > I got "meta-toolchain" and "meta-toolchain-sdk" working. The first is > (AFAIK) just the toolchain with libc (no extra libraries). And the > latter is an alias for "meta-toolchain-gmae" which is a toolchain > suitable for the "Gnome Mobile Application Environment". It has a > bunch of additinal libraries and headers. But to use this SDK thing I > need to be able to control what goes into it. > > I'm now thinking about just using the toolchain and sysroot from the > build dir... > >> Just trying to make sense of all this stuff.... > > Me too :-) > > Best regards, > Bjørn Forsman > > _______________________________________________ > Angstrom-distro-devel mailing list > Angstrom-distro-devel@linuxtogo.org > http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel > _______________________________________________ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
