[PATCH][ARM] Support arm-android-eabi

Doug Kwan (關振德) dougkwan@google.com
Sun Jun 29 19:36:00 GMT 2008


Hi,

2008/6/29 Mark Mitchell <mark@codesourcery.com>:

> I think adding a configure option to disable libstdc++-v3 would be better
> than hard-coding it into the configuration.  I'd assume that in the future
> someone might get libstdc++ working on Android; presumably it's not an
> inherent limitation of the platform that there not be a C++ runtime library.
>  And, it could be useful on other systems too.

Yes, I am talking about adding a --disable-libstdc++-v3, just like
other libraries.  There are platforms that have their own C and C++
libraries and do not use the ones from FSF :)

>> I understand that.  How does adding --disable-libstdc++-v3 in config
>> and using -mandroid instead sound?
>
> That sounds much better to me.
>
> In my ideal world, you'd be able to pass in *all* the things you need for
> -mandroid as configuration options and be able to pass them on the
> command-line as well.

Currently, all things that -mandroid will pass are passed in command
line now and that places too much burden on the user to know all the
options and implementation details like name of the start-up files,
name of the dynamic-linker and etc.

In my ideal world, I expect the tool "just works". In other words,

arm-android-eabi-gcc hello.c

should produce a ready-to-run ARM executable a.out on a host just like
running "gcc hello.c" on the host.

That said, I am still happy to use -mandroid. One single switch still
beats a long list of options. And "-mandroid" is easier for users to
remember as well.  Using "-mandroid" is less error-prone than the
current practice.

> In other words, I'd like to get to a situation where
> "arm-android-gcc" (whether provided with GCC or otherwise)  was just a
> wrapper program around "arm-eabi-gcc", that passed along the right options
> (like "-fno-rtti").  Right now, we're baking configurations into the
> compiler because we don't have enough flexibility to put them elsewhere, and
> that's unfortunate.

A gcc configuration file selectable at command line would be nice.

-Doug



More information about the Gcc-patches mailing list