This is the mail archive of the
mailing list for the GCC project.
Re: Add Android related compilation options and multilib options
- From: Ian Lance Taylor <iant at google dot com>
- To: Richard Guenther <richard dot guenther at gmail dot com>
- Cc: Jing Yu <jingyu at google dot com>, gcc-patches at gcc dot gnu dot org, Doug Kwan (éæï) <dougkwan at google dot com>, nickc at redhat dot com, richard dot earnshaw at arm dot com, paul at codesourcery dot com, mark at codesourcery dot com
- Date: Tue, 16 Jun 2009 13:53:01 -0700
- Subject: Re: Add Android related compilation options and multilib options
- References: <firstname.lastname@example.org> <email@example.com>
Richard Guenther <firstname.lastname@example.org> writes:
> On Tue, Jun 16, 2009 at 2:50 AM, Jing Yu<email@example.com> wrote:
>> This patch does three things:
>> 1. Add -mandroid option to the compiler.
>> Â (This part was originally written by Doug Kwan firstname.lastname@example.org
>> for gcc-4.3.1)
>> Â ÂWith this option, users can easily compile programs for android.
>> Â ÂSuppose arm-eabi-gcc is built with android sysroot. Then we can use a simple
>> Â Â Âcommand to compile a program:
>> Â Âeg. Âarm-eabi-gcc -mandroid hello.c -o hello
> Why don't you add android as a os variant and configure
> for a arm-eabi-android target instead?
That is what Doug Kwan proposed originally, and Mark Mitchell said this:
I try to avoid approving Google patches, but now different maintainers
are just jerking around the Android folks. That is unfair.
What do we want to do here?