The GCC-E compiler is stricter than RVCT, so you may have to update some of your sources to be more ISO C++ compliant to use GCC-E.Building ROMs with GCC-E binaries
Binaries created by GCC-E can be included in a ROM image by passing the –D_GCCE option to the buildrom command. This will automatically look for GCC-E binaries before RVCT binaries, and it will include an ARMv5 binary if it cannot find a GCC-E binary.
Limitations
GCC-E cannot handle files containing inline assembler and some target types for the kernel. So it cannot be used for compiling some base files. The current list of target types not supported is KDLL, KEXT, PDD, VAR and LDD.
Will the GCC-E compiler be free in licensee SDKs?
The compiler is publicly available (free) from http://www.codesourcery.com/gnu_toolchains/arm/, but you also need the correct build system toolchain (i.e. bldmake etc.) to be able to compile with GCC-E.
The plan of record at time of writing is that:
- Series60 3.0 and UIQ 3.0 SDKs will include the compiler and the buildsystem.
- CW3.1 will support building using GCC-E (but will require the SDK to have the buildsystem).
- Eclipse tools (in development) will support building GCC-E and will include the buildsystem