Michael 'Mickey' Lauer <[EMAIL PROTECTED]> writes: > I recommend the following procedure:
Thanks very much for taking the time to try to explain this to me! > 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? If OpenEmbedded can't build the toolchain, is there a good tutorial somewhere which explains in detail how to do this? Is anything needed other than "cc" and "ld" replacements? > Make it known to OpenEmbedded that you have your own toolchain, i.e.: > > ASSUME_PROVIDED += "virtual/arm-linux-gcc-2.95 binutils-cross > gcc-cross-initial gcc-cross" > ASSUME_PROVIDED += "virtual/arm-linux-libc-for-gcc > virtual/arm-linux-binutils virtual/arm-linux-gcc" > ASSUME_PROVIDED += "virtual/arm-linux-gcc-initial > virtual/arm-linux-gcc-initial > ASSUME_PROVIDED += "virtual/libc linux-libc-headers" Can someone explain the structure of the value of ASSUME_PROVIDED? I apologize in advance if my questions sound stupid, but this all looks like voodoo to me. If I want to become a voodoo practitioner like you folks, I need to ask a few basic questions. :-) What is the difference between the items that are prefixed with "virtual/" and those which are not? What is the difference between "gcc-cross-initial" and "gcc-cross"? What is the difference between "virtual/arm-linux-lib-2.95" and "virtual/arm-linux-gcc"? Etc. > add some more for the libraries like qte which you will take from your > toolchain as well. > > 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? > 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? > I don't know in which way this is different from ipk -- perhaps you > don't need to do anything at all except changing the extension. > > 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. :-( Once again, thanks very much for your help! -- Joe _______________________________________________ Oe mailing list [email protected] https://www.handhelds.org/mailman/listinfo/oe
