summaryrefslogtreecommitdiffstats
path: root/android_webview/java/generated_src
Commit message (Collapse)AuthorAgeFilesLines
* Add switch for turning on library in zip file support.anton@chromium.org2014-07-011-0/+4
| | | | | | | | | | Note this patch doesn't enable the support (that is done in GYP). BUG= Review URL: https://codereview.chromium.org/359323002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@280812 0039d316-1c4b-4281-b951-d872f2087c98
* Move the android library loader from content to baseaberent@chromium.org2014-02-101-4/+7
| | | | | | | | | | | | | The android library loader has no logical connection with content. Mojo shell, which doesn't depend on content, wants to use it. This CL moves it from content to base. BUG=225101 NOTRY=true Review URL: https://codereview.chromium.org/141223002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@250113 0039d316-1c4b-4281-b951-d872f2087c98
* Check library version and handle library load errorsaberent@chromium.org2013-11-281-1/+6
| | | | | | | | | | | | | | | This CL modifies the build to incorporate the expected C++ library version in the Java code. This is then checked when the library is loaded, to make sure that the C++ and Java builds match. This CL also implements error handling when library loads fail or the loaded version doesn't match the expected version. BUG=311644 Review URL: https://codereview.chromium.org/59533009 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@237779 0039d316-1c4b-4281-b951-d872f2087c98
* Android: Add chrome-specific dynamic linker.digit@chromium.org2013-10-211-0/+8
| | | | | | | | | | | | | | | | | | | | | | This patch adds a new Chrome-specific dynamic linker for Android, that implements RELRO section sharing in order to save about 1.3 MB of RAM per renderer process in content-based programs (ContentShell, ChromiumTestShell, Chrome, etc...) The linker is disabled by default. For more details, see the corresponding bug entry. This introduces a new test package (content_linker_test_apk) as well as a new test category. To build and test this feature, do the following: ninja -C out/Debug content_linker_test_apk build/android/test_runner.py linker BUG=287739 R=qsr@chromium.org Review URL: https://codereview.chromium.org/23717023 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@229921 0039d316-1c4b-4281-b951-d872f2087c98
* Android: nits following library loader changes.bulach@chromium.org2013-04-021-1/+0
| | | | | | | | | | | | Truly small follow-up from r191695. No functional changes. BUG= Review URL: https://chromiumcodereview.appspot.com/13469003 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@191930 0039d316-1c4b-4281-b951-d872f2087c98
* Make the build control what library(/ies) to loadcjhopman@chromium.org2013-04-011-0/+13
At build time, we know what native libraries an apk needs to load. Instead of requiring those .apks to specify this again in code, instead generate a .java file containing a list of the libraries to load. This is done using a pattern similar to resources, content_java is built with a placeholder NativeLibraries.java (i.e. without an actual value for its libraries list). The corresponding .class file is not included in content_java.jar. Then, when building an apk we generate the "real" NativeLibraries.java (with the real String[]) and include that in the .apk. This is designed to also support the component build, where, we will have to calculate the list of libraries at build time, and sort them in dependency order (because Android's linker, for some reason, doesn't do that itself). BUG=158821 TBR=brettw@chromium.org Review URL: https://chromiumcodereview.appspot.com/12939021 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@191695 0039d316-1c4b-4281-b951-d872f2087c98