| 5bdf305bbe529a85735200353478057b65bb462e |
|
20-Sep-2012 |
Ying Wang <wangying@google.com> |
Move AndroidConfig.h from system/core to the build project.
So unbundled branches don't need to include the system/core project.
Change-Id: Ic4ef62ee6df069b9b2dd123aed95a3e7fcdfc146
|
| 31ef1037bf7b66e949ecf52a1a29672d43ebfef8 |
|
21-Aug-2012 |
Andrew Hsieh <andrewhsieh@google.com> |
Added BUILD_HOST_static to build statically linked executable/shared-lib
Statically linked executable/shared-lib (eg. SDK tools) are useful
in sandboxed environment.
In BUILD_HOST_static zipalign needs -lpthread indirectly:
zipalign->libutils.a->liblog.a->logd_write.c->pthread
Change-Id: I615f574e918c83ed1ab82db2453b69d0420cb59c
|
| da4bf4251451d2da8883d636849b65fcc368a575 |
|
17-Aug-2012 |
Ying Wang <wangying@google.com> |
Don't include system/core/include/arch/<arch>/Android.mk for apps-only build.
Bug: 6994483
Change-Id: I76c4d96264cf94a79d59fdeb52bb37c07a9458dd
|
| f9613a4f730b8a385971f95150582b9a543302ae |
|
27-Apr-2012 |
Andrew Hsieh <andrewhsieh@google.com> |
Added BUILD_HOST_static to build statically linked executable/shared-lib
Statically linked executable/shared-lib (eg. SDK tools) are useful
in sandboxed environment.
In BUILD_HOST_static zipalign needs -lpthread indirectly:
zipalign->libutils.a->liblog.a->logd_write.c->pthread
Change-Id: I8fa91a937b728ccdf942c4ba199efb1e2e49da3d
|
| 4e82d1fa7f3fb1ecfa6cbd8b8ddcb6c0c0e17d1d |
|
21-Apr-2012 |
Jean-Baptiste Queru <jbq@google.com> |
On linux, always use the prebuilt host toolchain
Change-Id: I8077c4780e1e3540e5e2133cf0ffa61d474d3acc
|
| 2245d17dc847ecb5371807466788552ca0198152 |
|
13-Mar-2012 |
Andrew Hsieh <andrewhsieh@google.com> |
Point to new linux prebuilt toolchain for SDK build
Change-Id: I21849119b0f3f45f950e9e6d1da0833aff381fb7
|
| 0e63fd37ddc539912a1b89875a925c75e4a281b2 |
|
13-Mar-2012 |
Andrew Hsieh <andrewhsieh@google.com> |
Point to new linux prebuilt toolchain for SDK build
Change-Id: I21849119b0f3f45f950e9e6d1da0833aff381fb7
|
| ed6b8155056c52ac6d6a38151a97fc948b4614c3 |
|
28-Feb-2012 |
Andrew Hsieh <andrewhsieh@google.com> |
BUILD_HOST_64bit=1 to build host tools in 64-bit
By default we build tool in 32-bit. This flag allow individual tool and its
dependencies to be built in 64-bit (eg. Emulator). Fixes to resolve 64-bit
porting issues (in other git) will be submitted seperately.
Change-Id: I486cf7ddac727d3c374ed890857d497c3a69e598
|
| d75dbec617307ecb7c728201a4da82f1177ff742 |
|
11-Jan-2012 |
Jean-Baptiste Queru <jbq@google.com> |
Revert "Reference new location of SDK toolchain"
This reverts commit 1b834c6660c80d376151e977466e1622b67a2af0.
|
| 1b834c6660c80d376151e977466e1622b67a2af0 |
|
10-Jan-2012 |
Jean-Baptiste Queru <jbq@google.com> |
Reference new location of SDK toolchain
Change-Id: If470d742a92061006d94b72f21df5c642348e179
|
| cb48497ff2f84e8f7def981246ddc028ea126879 |
|
06-Sep-2011 |
Jim Huang <jserv@0xlab.org> |
HOST_linux-x86: Avoid doubly define macro _FORTIFY_SOURCE
While building Android with latest host gcc, it causes the following
build error:
Install: out/host/linux-x86/bin/mkbootimg
host C++: obbtool <= frameworks/base/tools/obbtool/Main.cpp
<command-line>:0:0: error: "_FORTIFY_SOURCE" redefined [-Werror]
<built-in>:0:0: note: this is the location of the previous definition
cc1plus: all warnings being treated as errors
In order to make build system happy, this patch does unset macro
_FORTIFY_SOURCE and then define it in host cflags.
Change-Id: Ic37a90f05081a2c3650b3335bc87e9e895900fb2
|
| fddf23f19e7604e6c5b3c5377e7ff6293539a1da |
|
06-Sep-2011 |
Jim Huang <jserv@0xlab.org> |
HOST_linux-x86: Avoid doubly define macro _FORTIFY_SOURCE
While building Android with latest host gcc, it causes the following
build error:
Install: out/host/linux-x86/bin/mkbootimg
host C++: obbtool <= frameworks/base/tools/obbtool/Main.cpp
<command-line>:0:0: error: "_FORTIFY_SOURCE" redefined [-Werror]
<built-in>:0:0: note: this is the location of the previous definition
cc1plus: all warnings being treated as errors
In order to make build system happy, this patch does unset macro
_FORTIFY_SOURCE and then define it in host cflags.
Change-Id: Ic37a90f05081a2c3650b3335bc87e9e895900fb2
|
| 59d296623b0820fa0689b70c20af1db6b4435ab2 |
|
06-Sep-2011 |
Jim Huang <jserv@0xlab.org> |
HOST_linux-x86: Avoid doubly define macro _FORTIFY_SOURCE
While building Android with latest host gcc, it causes the following
build error:
Install: out/host/linux-x86/bin/mkbootimg
host C++: obbtool <= frameworks/base/tools/obbtool/Main.cpp
<command-line>:0:0: error: "_FORTIFY_SOURCE" redefined [-Werror]
<built-in>:0:0: note: this is the location of the previous definition
cc1plus: all warnings being treated as errors
In order to make build system happy, this patch does unset macro
_FORTIFY_SOURCE and then define it in host cflags.
Change-Id: Ic37a90f05081a2c3650b3335bc87e9e895900fb2
|
| e33ba4c49ed461d608c65eb4e09d31ca81d167ff |
|
12-Jul-2011 |
Jeff Brown <jeffbrown@google.com> |
Remove the simulator target from all makefiles.
Bug: 5010576
Change-Id: Ie814f4c8d3aa1e7cc7f5735822ab25542f36cf62
|
| 60a1e8805290267d6c8f32051f25e6f21fae909a |
|
12-Jan-2011 |
David 'Digit' Turner <digit@android.com> |
Add support for custom Linux host toolchains when building the SDK.
This is needed in order to build Linux SDK binaries that can run
properly on Ubuntu 8.04 (Hardy). By default, the host toolchain
on 10.04 (Lucid) generates machine code that won't run on Hardy
due to GLibc ABI mistmatches.
Note that nothing happens if the new toolchain is not in the
prebuilt tree.
Change-Id: I914f5a303f16b6871759ce5a7178585ed3060870
|
| 0960ca748804b772453ebe50d212a691c1a6c066 |
|
10-Dec-2010 |
David 'Digit' Turner <digit@google.com> |
Add support for custom Linux host toolchains when building the SDK.
This is needed in order to build Linux SDK binaries that can run
properly on Ubuntu 8.04 (Hardy). By default, the host toolchain
on 10.04 (Lucid) generates machine code that won't run on Hardy
due to GLibc ABI mistmatches.
Note that nothing happens if the new toolchain is not in the
prebuilt tree.
Change-Id: I45c1f68e37e15a0032f885df1c5c0f297b3d8642
|
| 163fa35fe3d49f0178b0173d662cf899989b7bcb |
|
02-Sep-2010 |
Ying Wang <wangying@android.com> |
Disable new longjmp in glibc 2.11 and later.
Bug: 2967937
Change-Id: I7a5ef082502192f41c26a48632edfe775dea7648
|
| fb644881b6083aa0d9d15e7aad8bfa5a429b1c37 |
|
02-Sep-2010 |
Ying Wang <wangying@google.com> |
Disable new longjmp in glibc 2.11 and later.
Bug: 2967937
Change-Id: I4e2a5f806ad45a01ca7f8c4d032cd29fce1d794d
|
| 16e95bb99df4515ad37d73562bffb1a9fd21c162 |
|
24-Feb-2010 |
Andy McFadden <fadden@android.com> |
Build the target side of the simulator as 32-bit.
This detail got lost in my previous cleanup change 9b4a812.
Also add a comment explaining why the host side of the
simulator needs to be built in 64-bit (wxWidgets).
Change-Id: I2a867f7f80b43d53e73348b19f6ae834600295f9
|
| 9b4a81237be29b0aae50d1e370b63a07ea2b88b9 |
|
23-Feb-2010 |
Jean-Baptiste Queru <jbq@google.com> |
Get rid of $(combo_target)
The only OS-ARCH combo that would have benefited from it
is linux-x86, but it explicitly used separate configurations
for the HOST_ and TARGET_ side of things.
This makes is clear which files are related to the HOST_
configuration and which ones are related to the TARGET_
configuration, and expands $(combo_target) to the only
possible/reasonable value that it could have had in every
file.
This also cleans up the simulator, by moving it in a single
place in TARGET_linux_x86 (since the only part that's special
is to use HOST_ settings even when building TARGET_ modules).
Change-Id: I2420eeb8cfe539f5807ec99cb3177ffb9f2476d5
|