Joe Wells writes: > > 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. > > I'm expecting to have to make the headers for the libraries myself. > I'm hoping that merely fetching the correct old versions of glibc and > Qt/Embedded will go a long way towards solving that problem.
glibc should be easy, I think Qt/Embedded would be a huge undertaking, since MOTO deeply modified it. Worth a try though, though if I would do it, I'd add a fake qte bbfile, that just takes the binary libs as taken from a phone and your EZX header files and copies them into the staging area. Build-Time-Linking against the open source Qt/E version will probably generate lots of missing/false references when trying to resolve the symbols with the MOTO-adjusted Qt/E. > I can > use the libraries on the A780 to make dummy versions with the code > portion zeroed out that will be good enough for linking. The above > steps involve no risk of copyright violation. I can hopefully figure > out the interface to any remaining symbols I need to use by reverse > engineering (e.g., using strace, ltrace, etc.). > > Are these the kind of issues you mean or are there other completely > different issues? No, that's more or less it. Especially the leaked SDK I've heard about is the stuff that I would like us to stay away from. > > Part of the toolchain creation. You can't build gcc in one run. See > > "building gcc" on gcc.gnu.org for a (exhaustive) explanation... > > Why am I supposed to claim to have provided both of them? If I > understand correctly, I will only provide the substitute for > gcc-cross. Am I wrong? gcc-cross, binutils, (and perhaps libc -- depending on if you can recreate the exact version). I guess I put more stuff into ASSUME_PROVIDED than necessary :) > >> > 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 :) > > Where do I need to make changes to integrate support for them? Add the chose-old-ipkg-format parameters from sharprom.conf. Additionally, you may or may not need to tweak ipkg (or alternatively post process packages in a special bbclass if you want) to remove the CONTROL files -- I don't know whether the MOTO installer would ignore them or not. -- Regards, Michael 'Mickey' Lauer | FreeLancer | http://www.Vanille-Media.de _______________________________________________ Oe mailing list [email protected] https://www.handhelds.org/mailman/listinfo/oe
