On Tue, 2010-02-23 at 16:53 -0800, Philip Balister wrote: > > On 02/23/2010 03:09 PM, Khem Raj wrote: > > On Tue, Feb 23, 2010 at 2:37 PM, Philip Balister<[email protected]> > > wrote: > >> On 02/23/2010 05:51 AM, Jay Snyder wrote: > >>> > >>> I was able to build gcc for installation directly onto the OE target > >>> with "bitbake gcc". "bitbake g++" gives me "nothing provides g++". > >>> > >>> What is the magic bitbake command to provide this? > >> > >> bitbake task-sdk-native, and install task-native-sdk. Anyone know why the > >> task creates a package with different name? > > > > may be because > > > > task-sdk-native.bb:RPROVIDES_${PN} = "task-native-sdk" > > I know that :) I am curious why the renaming.
And if perhaps we couldn't get a different name altogether? 'native' has a meaning normally that's not what it means here. task-on-device-sdk is a bit wordy, but avoids 'native'. Of course, 'native development' also has a meaning too.. RPROVIDES perhaps? Or is that just the worst of both worlds.. -- Tom Rini <[email protected]> Mentor Graphics Corporation _______________________________________________ Openembedded-devel mailing list [email protected] http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
