This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: [PATCH][ARM] Support arm-android-eabi
> Why -- and how -- is it different? Why can't this just be a -mandroid
> switch to the standard ARM EABI target?
There major differences are
1. non-standard libraries and start-up.
2. Some libraries are not built by default. I can used
--disable-libXXX for most but not libstdc++-v3.
3. -fno-rtti and -fno-exceptions are default.
> We should do
> like every other compiler and support multiple target systems from a single
> compiler build.
I understand that. How does adding --disable-libstdc++-v3 in config
and using -mandroid instead sound?
-Doug