summaryrefslogtreecommitdiff
path: root/Android.bp
AgeCommit message (Collapse)Author
2018-02-22Remove modification for missing-field-initializers from sources.Hidehiko Abe
Since C++11, we have concrete semantics. Thus, we rely on it. Note that, we still need to keep LAZY_INSTANCE_INITIALIZER because it is a macro used in other project, which may have missing-field-initializers warning enabled. Bug: 73270448 Test: Built locally. Treehugger. Change-Id: Ieb59b25c2936d27c3501d21098b248fac2778f0a
2018-02-21Re-uprev to r462023.Hidehiko Abe
Previous uprevs didn't include several CLs. This re-uprev's to the r462023. cf) Missing CLs I found. https://codereview.chromium.org/2556563002 https://codereview.chromium.org/2754483002 https://codereview.chromium.org/2171833002 https://codereview.chromium.org/2778183003 https://codereview.chromium.org/2500473002 https://codereview.chromium.org/2173523002 https://codereview.chromium.org/2666423002 https://codereview.chromium.org/2723423002 https://codereview.chromium.org/2789463002 https://codereview.chromium.org/2723083004 https://codereview.chromium.org/2637843002 https://codereview.chromium.org/2785943004 https://codereview.chromium.org/2657603004 https://codereview.chromium.org/2774363003 https://codereview.chromium.org/2776853002 https://codereview.chromium.org/2736053003 https://codereview.chromium.org/2779413002 https://codereview.chromium.org/2782503002 https://codereview.chromium.org/2782083003 https://codereview.chromium.org/2399213005 https://codereview.chromium.org/2787383002 https://codereview.chromium.org/2790523004 https://codereview.chromium.org/2787533002 https://codereview.chromium.org/2780983003 https://codereview.chromium.org/2790403003 https://codereview.chromium.org/2747673002 https://codereview.chromium.org/2778173003 https://codereview.chromium.org/2788613004 https://codereview.chromium.org/2781983003 https://codereview.chromium.org/2774223003 Bug: 73270448 Test: Built and ran libchrome_test locally. Run treehugger. Change-Id: I5e76096d4fcf660571275cce5f4a980a8bb574fe
2018-02-19Remove ALLOW_UNUSED_PARAM macro.Hidehiko Abe
Now libchrome is built with -Wunused-parameter, so we no longer need the macro. Bug: 73270448 Test: Built locally. Treehugger. Change-Id: Ie02279df60b26f78019e28d383c50084695fb07a
2018-02-19Deal with -Wunused-parameter in libchrome build rule.Hidehiko Abe
So, now we do not need modification in libchrome to workaround the error. Bug: 73270448 Test: Build locally. Treehugger. Change-Id: I38fe79c1e01fd39a4bdd7121bb58b9b6d9a3da89
2018-02-08Clean up Mac related files.Hidehiko Abe
We droped to support libchrome on Mac host. This CL cleans up Android.bp related to Mac, and removes the files which are no longer used. Bug: 72618679 Test: Build locally, ran Treehugger. Change-Id: I50d0aec5707212be2163286d5c91904196a0be84
2018-02-07Revert "Revert "Disable mac-host build.""Hidehiko Abe
This reverts commit f7ab4b45881660bfeca478ec05f760a25daa51a9. Reason for revert: The fix was landed, https://android-review.googlesource.com/c/platform/external/libbrillo/+/609666, actually before this revert. One build on master has the fix but doesn't this revert, which successfully passed. So, now we can safely reland this. Change-Id: I06654f16397dcd6a65d349bafc3c8e9180f88a9d
2018-02-06Revert "Disable mac-host build."Ian Pedowitz
This reverts commit a5fc101633a53a0f64c0899b97bbbebdc4020aa7. Reason for revert: b/72988664 Bug: 72988664 Bug: 72618679 Change-Id: I11c431c0bf962d9224403f91df1292b8a3012af4
2018-02-05Disable mac-host build.Hidehiko Abe
Now, nobody uses libchrome on Mac as host. This CLs drops the support. Bug: 72618679 Test: Built on Mac locally. Change-Id: I489a20d5820640bf68c3f061c135730f8c9977da
2018-01-10readdir_r is deprecated.Elliott Hughes
This is fixed upstream (https://chromium-review.googlesource.com/c/chromium/src/+/599120) but we haven't made any progress in actually getting that change into Android, so just ignore the warning for now... Bug: http://b/32678321 Test: boots, builds Change-Id: Ic1fd7ebfe63232da67d02fba0f8ae8086e91d6ca
2018-01-06Ignore -Wunused-variable warningYi Kong
Clang 6.0.1 update introduced a number of new warnings, failing werror build. Ignore the -Wunused-variable warning for external/libchrome. Test: m checkbuild Change-Id: Iff40b92cc371c8fa2b66acdd73ee5368b975e15b
2017-12-22Uprev the library to r462023 from Chromium, 3rd attemptJakub Pawlowski
This merge was done against r462023 which corresponds to git commit 32eb7c31af9cab6231f0d3d05206072079177605 from Apr 05, 2017 First attempt, in commit bf8c17f71511c1e90cd8cccfe71f0852c566bd3b was badly squashed, causing automated test failure in system/bt. Next one broke mac build. Test: manually ran all test from system/bt that failed on previous attempt, plus libchrome_unittest Change-Id: I60003263418de3078c7be2da9fb1eeaeb786f3d0
2017-12-21Revert "Uprev the library to r462023 from Chromium"Mathieu Chartier
This reverts commit fe2f52931e8e50253d06329d7bf0a4164c7ba580. Reason for revert: Mac build broken Change-Id: I3abd2ba6874ec5bd283ba17c36ad0b35bcc3d374
2017-12-21Uprev the library to r462023 from ChromiumJakub Pawlowski
This merge was done against r462023 which corresponds to git commit 32eb7c31af9cab6231f0d3d05206072079177605 from Apr 05, 2017 Previous attempt, in commit bf8c17f71511c1e90cd8cccfe71f0852c566bd3b was badly squashed, causing automated test failure in system/bt. Test: manually ran all test from system/bt that failed on previous attempt, plus libchrome_unittest Change-Id: I539a868af1d06baad3e80a89b8c16fb3d86ab77a
2017-12-20Revert "Uprev the library to r462023 from Chromium"Jakub Pawlowski
This reverts commit bf8c17f71511c1e90cd8cccfe71f0852c566bd3b. Reason for revert: https://buganizer.corp.google.com/issues/70858501 Change-Id: Iedb1193d46ea2211f8b6fdace41902ad8df6d754
2017-12-19Uprev the library to r462023 from ChromiumJakub Pawlowski
This merge was done against r462023 which corresponds to git commit 32eb7c31af9cab6231f0d3d05206072079177605 from Apr 05, 2017 Change-Id: I70bf77fcb3215da3e17f997752bfdad7d4e6e1c9
2017-12-13libchrome: Uprev the library to r456626 from ChromiumHidehiko Abe
Pulled the latest and greatest version of libchrome from Chromium. The merge was done against r456626 which corresponds to git commit 08266b3fca707804065a2cfd60331722ade41969 of Mar 14, 2017 Notable changes are: - FOR_EACH_OBSERVER macro removed (replaced by use of C++ 11 range-base for loop) - base::Values no more FundamentalValue - stl_util moved to base namespace - some scoped pointers removed in crypto/ in favor of BoringSSL UniquePtr. - path() accessor renamed to GetPath() in ScopedTempDir (and other classes) - introduction of base::CallbackOnce Test: All unit-tests should still pass. Change-Id: I1e65efb167fa708e35ed7c6492f1cb66a6a46104 Merged-In: I180f9defc7607f462389fae17701fff553c4a2d0
2017-10-16Use target.linux for all linux kernel based targetsDan Willemsen
Now in Android.bp files, target.linux applies to all targets running a linux kernel (android, linux_glibc, linux_bionic). So common flags/sources/etc can be combined instead of copying them to each target. Test: m Change-Id: Ifc6731c84c6db6c2386abc6aa3be080e4dbf2f99
2017-10-02Rename target.linux[_x86[_64]] to target.linux_glibc[_x86[_64]]Dan Willemsen
In the future, target.linux will apply to all targets running a linux kernel (android, linux_glibc, linux_bionic). So move all current users to the specific linux_glibc. There will be another cleanup pass later that will move some instances back to target.linux if the properties should be shared with target.android and target.linux_bionic, but target.linux needs to be removed first. Test: out/soong/build.ninja identical before/after Change-Id: I8ee24e1fc1cdb379b18e5f2d5aaa33ad138e0abd Exempt-From-Owner-Approval: build system cleanup
2017-09-28Remove default librariesDan Willemsen
libdl is part of system_shared_libs now. -ldl -lpthread -lm are now defaults for host_ldlibs on Linux and Darwin. -lrt is a default for host_ldlibs on Linux. Test: m host Change-Id: I10fcb88200e004ad09967532db9a7abc0450054d Exempt-From-Owner-Approval: build system cleanup
2017-07-26Revert "libchrome: Uprev the library to r456626 from Chromium"android-o-mr1-preview-2android-o-mr1-preview-1Luis Hector Chavez
am: e5b2c6fa6f Change-Id: I819960740d65600c933289f480ab6a9e53a88c62
2017-07-26Revert "libchrome: Uprev the library to r456626 from Chromium"android-o-iot-preview-5o-iot-preview-5Luis Hector Chavez
This reverts commit 0601274935e7f632eb0d6ce0fd223b744349d20b. Reason for revert: Broke the mac_sdk Exempt-From-Owner-Approval: Fixing mac_sdk Change-Id: I2cab1818261f3b75dcf7dfc3edf6d6b7bab541a8
2017-07-26libchrome: Uprev the library to r456626 from ChromiumJay Civelli
am: 0601274935 Change-Id: I04c76587e9fb0cdc8f189efe7a12161aee303ec0
2017-07-26libchrome: Uprev the library to r456626 from ChromiumJay Civelli
Pulled the latest and greatest version of libchrome from Chromium. The merge was done against r456626 which corresponds to git commit 08266b3fca707804065a2cfd60331722ade41969 of Mar 14, 2017 Notable changes are: - FOR_EACH_OBSERVER macro removed (replaced by use of C++ 11 range-base for loop) - base::Values no more FundamentalValue - stl_util moved to base namespace - some scoped pointers removed in crypto/ in favor of BoringSSL UniquePtr. - path() accessor renamed to GetPath() in ScopedTempDir (and other classes) - introduction of base::CallbackOnce Test: All unit-tests should still pass. Change-Id: I5c2cb41ea4c037fe69fbb425e711b1399d55d591
2017-06-06Temporarily suppress unused-lambda-capture warning warning am: f320c0cf71 ↵Yi Kong
am: 559de4f511 am: 36b5f97520 Change-Id: I3151fe559d2ccbf74d0ddadb14bb3a0263829613
2017-05-16Temporarily suppress unused-lambda-capture warning warningandroid-o-preview-4Yi Kong
Bug: 38232827 Test: Build Change-Id: I5a6d667a44522514d11af4cd821c1668e52f4777
2017-05-08Make libchrome_test_helpers static buildable for host am: 394b004b77 am: ↵Mark Urbanus
3c4a94e84c am: a8916bf601 Change-Id: I0ddbd54362bb7022426f39f781d83d19e85ebdae
2017-05-08Make libchrome_test_helpers static buildable for hostandroid-o-preview-3android-n-iot-preview-4n-iot-preview-4Mark Urbanus
Bug: 35314006 Test: Validated compilation on linux and mac host.
2017-04-12Mark as vendor_available am: c9027cbc05 am: 7dee603070Dan Willemsen
am: 23d9356cf8 Change-Id: Icf857f12fc17fe21b7ef87ef98d1ae304ca12f75
2017-04-10Mark as vendor_availableandroid-wear-o-preview-4android-wear-o-preview-3android-o-preview-2Dan Willemsen
By setting vendor_available, the following may become true: * a prebuilt library from this release may be used at runtime by in a later releasse (by vendor code compiled against this release). so this library shouldn't depend on runtime state that may change in the future. * this library may be loaded twice into a single process (potentially an old version and a newer version). The symbols will be isolated using linker namespaces, but this may break assumptions about 1 library in 1 process (your singletons will run twice). Background: This means that these modules may be built and installed twice -- once for the system partition and once for the vendor partition. The system version will build just like today, and will be used by the framework components on /system. The vendor version will build against a reduced set of exports and libraries -- similar to, but separate from, the NDK. This means that all your dependencies must also mark vendor_available. At runtime, /system binaries will load libraries from /system/lib*, while /vendor binaries will load libraries from /vendor/lib*. There are some exceptions in both directions -- bionic(libc,etc) and liblog are always loaded from /system. And SP-HALs (OpenGL, etc) may load /vendor code into /system processes, but the dependencies of those libraries will load from /vendor until it reaches a library that's always on /system. In the SP-HAL case, if both framework and vendor libraries depend on a library of the same name, both versions will be loaded, but they will be isolated from each other. It's possible to compile differently -- reducing your source files, exporting different include directories, etc. For details see: https://android-review.googlesource.com/368372 None of this is enabled unless the device opts into the system/vendor split with BOARD_VNDK_VERSION := current. Bug: 36426473 Bug: 36079834 Test: Android-aosp_arm.mk is the same before/after Test: build.ninja is the same before/after Test: build-aosp_arm.ninja is the same before/after Test: attempt to compile with BOARD_VNDK_VERSION := current Change-Id: I6cfc292fb4e2d903d8b2600a61fab74e330f8f54
2017-03-24Revert "Make libchrome_test_helpers static buildable for host" am: ↵Mark Urbanus
262790d4eb am: c240507660 am: 00ed03a325 Change-Id: I5e4d9c86bddb3ab5ad33f912396828a16d1a660a
2017-03-24Revert "Make libchrome_test_helpers static buildable for host"Mark Urbanus
This reverts commit beed40cf417bbfcaf3e884450d50dd38315a3318. Change-Id: I949a70b2243af78da23acfb84e6fa348a6a6d70e
2017-03-23Make libchrome_test_helpers static buildable for host am: beed40cf41 am: ↵Mark Urbanus
0b01841bef am: 950f5a5b52 Change-Id: I7457613acaf12945f8a8a14c92f54fdf4f4f41de
2017-03-21Make libchrome_test_helpers static buildable for hostMark Urbanus
Bug: None Test: Validated compilation Change-Id: I62f2d9397a8e47b6bcc9d093198bde19fc0ca703
2016-12-16Disable experimental allocator shim for AndroidMark Urbanus
Disable the experimental allocator shim on Android builds. At this point we haven't identified a need for it and prevents us from having to update the linker flags for the many projects that have libchrome as a dependency. Bug: 33239390 Test: Validated libchrome dependents (update_engine) can be built properly without adding the -wrap* linker flags Change-Id: I4e7e914883dfbc08b7eab9e0e175c14e59e386eb
2016-12-01Convert Android.mk to Android.bpColin Cross
See build/soong/README.md for more information. libchrome-dbus stays in Android.mk for now due to the use of the BRILLO_USE_DBUS conditional. Test: mma -j Test: out/host/linux-x86/nativetest/libchrome_test/libchrome_test Change-Id: Icaffccd45f5a58f5a0d3f10784ca451048da07a1
generated by cgit v1.2.3 (git 2.25.1) at 2024-07-08 10:01:49 +0000