Jacek M. Holeczek wrote: > Hi, > I'm not that much in the "cross-business", but ... > > > No. Sorry. The whole toolchain is targeted at producing > > Windows CE PE binaries. You'll always need gcc and binutils > > built with --target=mingw32ce/cegcc/pe. And, we have important > > (...) > > You wont be able to use any of those, because they're targetted to > > produce binaries for elf-linux, elf, or to bare bones > > run-on-the-metal-with-no-os binaries, etc, etc. > > ... I don't think you are completely right here. > > First, the "binutils" contain the "objdump" utility, which can "transform" > between "binary-file-formats". Hence, it would be "sufficient" that this > utility knows also the "PE" format, while the compiler could use another > "appropriate" object-file-format (why not "arm elf32"?). >
That only works on some limited cases. If you're interfacing with an OS, and there is an ABI to follow, that won't work. E.g.: the arm-elf32 gcc would be using an ABI that specifies that small structs are returned in registers, while on WinCE they must be passed on the stack. objdump will not be able to convert that. E.g. 2 there are some PE specific things that gcc outputs in the assembly, that is understood by gas and assembled into PE/COFF special sections, that only a PE ld will understand. If you use an elf generic compiler that information will not be there... Anyway, if you want to try that, be my guest. I'll be very happy to try it when you get it working... ------------------------------------------------------------------------- SF.Net email is sponsored by: Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace _______________________________________________ Cegcc-devel mailing list Cegcc-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/cegcc-devel
