Joe Wells: > > 1.) get your EZX-toolchain up and running with all necessary libraries > > available you want to link against. > > I had been under the impression that the OpenEmbedded framework can > help with building the compiler tools. Is this not true, or is there > some reason why in this particular case OpenEmbedded does not help?
That's right. Usually, OpenEmbedded builds the toolchain and this is not necessary. However in your particular case there are two problems: 1.) You need to build a 100% compatible toolchain to build binaries that link and work against your runtime libraries on the phone. It's painful to recreate all what's necessary -- that's the reason why I use a prebuilt toolchain. 2.) The EZX-toolchain as distributed by several sources is of questionable legalty -- we are not going to allow these things to be a direct part of OE. > If OpenEmbedded can't build the toolchain, is there a good tutorial > somewhere which explains in detail how to do this? Read a bit about EZX crosstool on a forum, it's explained there. I don't want to link from here, sorry. > Can someone explain the structure of the value of ASSUME_PROVIDED? That stuff tells OE to ASSUME that some dependencies are PROVIDED by you and that OE doesn't need to build them. Please see the OE manual and the BitBake manual for those "basics" :) > What is the difference between the items that are prefixed with > "virtual/" and those which are not? virtual/foo is something that fulfills a dependency, i.e. you can have glibc and uclibc provide virtual/libc. This is to ease dependencies where it doesn't matter which package exactly fulfills the dependency, just the "feature" is present. > What is the difference between "gcc-cross-initial" and "gcc-cross"? Part of the toolchain creation. You can't build gcc in one run. See "building gcc" on gcc.gnu.org for a (exhaustive) explanation... > > 2.) add a fake toolchain package like ezx-toolchain which makes the > > toolchain paths available, see sharprom-toolchain for an example. > > Do I have to put this in the org.openembedded.dev/packages directory > for it to work? It doesn't matter where you put the .bb files to as long as OE can find them, i.e. they are included in BBFILES (see local.conf.sample). > > > 3.) integrate MPK as an additional package format. > > What is MPK? I haven't heard of this before. Do you mean the files > with ".mpkg" extension? Yes. Apparantly those are just old-style ipks without a CONTROL file, so not much to do for you in this direction :) > > 4.) you may need to develop patches to make Opie link against your > > toolchain. Submit them to [EMAIL PROTECTED] > > Yes, I predict a lot of work on this item. :-( Yeah. Then again, that's the most interesting part as well... -- Regards, Michael 'Mickey' Lauer | FreeLancer | http://www.Vanille-Media.de _______________________________________________ Oe mailing list [email protected] https://www.handhelds.org/mailman/listinfo/oe
