On Wed, 19 Dec 2012, Bjørn Forsman wrote:
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 think Angstrom uses it indirectly, IOW, I think it is the one
incorporated into the build tree.
The TI scripts are more refined. I was working with a Blaze reference
earlier in the year (OMAP4) with Ice Creame Sandwich and like the TI stuff
a lot.
I was going to move my BeagleBone over to the Sitara (Arago) tree, but my
boss wanted me to stick with the Angstrom.
The main reason were some of the scripts they included and TI folks. In
the past when I needed an answer, I sent emails to the addresses that did
the putbacks to their git repo, and they did respond.
--
Regards,
Alan
_______________________________________________
Angstrom-distro-devel mailing list
Angstrom-distro-devel@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
